Snap Inc. Transparency Reports are released twice a year. These reports provide important insight into the volume and nature of governmental requests for Snapchatters’ account information.
Providing our users very specific and clear information about how governments solicit their data—and how we respond—is an important way for users to hold their government—and us—accountable. An open society, after all, depends on openness. Without key data, our users can’t meaningfully understand how we harmonize our unwavering commitment to their privacy with the legitimate needs of law enforcement. And as government surveillance becomes an increasing matter of public concern, publishing semi-annual Transparency Reports is one way we can help.
Of course, there are limits even to what we may know about government surveillance. Section 702 of the Foreign Intelligence Surveillance Act—better known as FISA—lets the U.S. government covertly intercept electronic communications. When the government conducts surveillance without our knowledge or involvement, we obviously can’t provide visibility into these actions.
That is one reason why we believe that Congress should not reauthorize Section 702 absent substantive reforms to address key privacy and due-process issues.
And to be perfectly clear: We do not voluntarily provide any government with access to user data for surveillance purposes, whether directly or through third parties.
We also do our best to inform users when the government seeks their data. Since November 15, 2015, our policy has been to notify Snapchatters when we receive legal process that asks for their account information. There are only two exceptions to this policy: when we are legally prohibited from informing our users of the request (such as a gag order issued by a court) or when we believe that there are exceptional circumstances (like child exploitation or an imminent risk of death or bodily injury).
For more information about how we handle law enforcement data requests, please take a look at our Law Enforcement Guide, Privacy Policy, and Terms of Service.
Reporting Period
Requests
Account Identifiers
Percentage of requests where some data was produced
July 1, 2016—December 31, 2016
2,008
3,203
81%
Subpoena
744
1,278
76%
Pen Register Order
10
11
70%
Court Order
108
169
81%
Search Warrant
1,048
1,620
86%
Emergency
96
120
69%
Wiretap Order
2
5
50%
National Security
Requests
Account Identifiers*
July 1, 2016—December 31, 2016
NSLs and FISA Orders/Directives
O-249
0-249
Reporting Period
Emergency Requests
Account Identifiers for Emergency Requests
Identifiers for Emergency Requests Percentage of emergency requests where some data was produced
Other Information Requests
Account Identifiers for Other Requests
Percentage of other information request where some data was produced
July 1, 2016—December 31, 2016
64
95
73%
137
175
0%
Australia
4
6
50%
5
8
0%
Brazil
0
0
N/A
1
1
0%
Canada
11
11
100%
2
2
0%
Czech Republic
0
N/A
N/A
1
4
0%
Denmark
0
N/A
N/A
3
4
0%
Dominican Republic
0
N/A
N/A
1
1
0%
Estonia
0
N/A
N/A
1
1
0%
France
4
20
100%
19
28
0%
Germany
0
N/A
N/A
10
13
0%
Greece
0
N/A
N/A
1
1
0%
Hungary
0
N/A
N/A
1
4
0%
Iceland
0
N/A
N/A
1
1
0%
India
0
N/A
N/A
3
3
0%
Ireland
1
1
100%
1
3
0%
Israel
1
1
0%
0
N/A
N/A
Malta
0
N/A
N/A
1
1
0%
Mexico
0
N/A
N/A
1
1
0%
New Zealand
0
N/A
N/A
1
1
0%
Norway
0
N/A
N/A
1
1
0%
Singapore
0
N/A
N/A
2
2
0%
Spain
0
N/A
N/A
2
3
0%
Sweden
0
N/A
N/A
11
15
0%
Switzerland
1
3
0%
2
3
0%
United Kingdom
42
53
69%
64
73
0%
Reporting Period
Removal Requests
Percentage of requests where some content was removed
July 1, 2016—December 31, 2016
0
N/A
Reporting Period
DMCA Takedown Notices
Percentage of requests where some content was removed
July 1, 2016—December 31, 2016
18
67%
Reporting Period
DMCA Counter-Notices
Percentage of requests where some content was reinstated
July 1, 2016—December 31, 2016
0
N/A
* “Account Identifiers” reflects the number of identifiers (e.g. username, email address, phone number, etc.) specified by law enforcement in legal process when requesting user information. Some legal process may include more than one identifier. In some instances, multiple identifiers may identify a single account. In instances where a single identifier is specified in multiple requests, each instance is included.