An essential part of earning the trust of our customers is being transparent about the requests we receive from law enforcement and other governmental entities. To this end, Cloudflare publishes this semi-annual Transparency Report on the governmental requests we have received to disclose information about our customers. The data is complete as of December 31, 2017, including requests related to Cloudflare and StopTheHacker. This Report supplants our previous Transparency Reports, which are archived in their entirety here.
Cloudflare operates a robust global network that transmits as much as 10% of all global internet requests and is extremely mindful of the responsibility that comes with that privileged position. It is Cloudflare's overriding privacy principle that any personal information you provide to us is just that: personal and private. We will not sell, rent, or give away any of your personal information without your consent. Our respect for our customers' privacy applies with equal force to commercial requests and to government or law enforcement requests.
Cloudflare's approach to law enforcement requests is that we are supportive of their work; however, any request we receive must strictly adhere to the due process of law and be subject to judicial oversight. It is not Cloudflare's intent to make law enforcement's job any harder, or easier. We respect the work they do and appreciate their assistance in protecting the rights of our customers. We have a healthy and open relationship with law enforcement officials so they understand these standards and our processes.
It is our policy to notify our customers of a subpoena or other legal process requesting their customer or billing information before disclosure of information. Cloudflare is not subject to foreign legal jurisdictions and only accepts requests in English from foreign law enforcement agencies that are issued via a U.S. court either by way of a mutual legal assistance treaty (MLAT) or a letter rogatory. We received 6 MLAT requests through the U.S. court system in the second half of 2017. We received 2 SEC subpoena.
If Cloudflare were asked to do any of the above, we would exhaust all legal remedies, in order to protect our customers from what we believe are illegal or unconstitutional requests.
The data presented below covers the period from July 1, 2017 to December 31, 2017. A request received in December 2017, but not processed until January 2018 will show as both "Requests received" and "Requests in process." Also, requests for which we are waiting for a response from law enforcement before moving forward may also be reflected in "Requests in process." The Total # of domains affected and the Total number of accounts affected refer only to requests which have been answered.
This category includes any legal process which does not have ex ante judicial review, including but not limited to grand jury subpoenas, U.S. government attorney issued subpoenas, and case agent issued summonses.
Requests in process
Total # of domains affected
Total # of accounts affected
1 The one subpoena in process in 2013 was rescinded in 2014.
2 A small number of subpoenas received accounted for 2/3 of domains affected.
3 A small number of subpoenas received accounted for 2/3 of accounts affected.
In 2017 Cloudflare pushed back on 20 subpoenas, and they were rescinded.
This category includes any order issued by a judge or magistrate, including but not limited to 18 U.S.C. § 2703(d), 18 U.S.C. § 2705(b), and MLAT orders. Orders which may fall under a more specific category such as search warrants or pen register / trap and trace orders will be reported under the more specific category and not counted here.
1 For one of the court orders in 2013, Cloudflare was not able to provide any information. Counts have been updated to reflect the requests in process in 2013 that were answered in 2014.
2 A small number of court orders received accounted for almost 2/3 of domains affected.
3 A small number of court orders received accounted for almost 2/3 of accounts affected.
In 2017 Cloudflare pushed back or was unable to provide any information on 29 court orders, and they were rescinded.
This category includes only search warrants which require judicial review, probable cause, and inclusion of a location to be searched and a detail of items requested.
1 One search warrant in 2013 was rescinded. Counts have been updated to reflect the requests in process in 2013 that were answered in 2014.
2 A small number of court orders received accounted for almost 2/3 of domains affected
3 A small number of court orders received accounted for almost 2/3 of accounts affected
In 2017 one search warrant was rescinded, as Cloudflare was not able to provide any information.
Cloudflare follows the principles laid out in U.S. v. Warshak and requires a valid search warrant before disclosing any customer content sought by law enforcement. Cloudflare is not a hosting provider or an email service provider and does not have customer content in the traditional sense. In the rare instances where law enforcement has sought content such as abuse complaints or support communications, Cloudflare has insisted on a warrant for those electronic communications. To date, we have received no such warrants.
This category includes only pen register/trap and trace orders issued by the court for real-time disclosure of non-content information, including IP address information.
This category includes only wiretap orders that were issued by a court.
What we can say in regard to national security orders is highly regulated. In January 2014, the Department of Justice and the Director of National Intelligence announced a change in the rules governing the disclosure of national security orders, including National Security Letters (NSLs) received by a company from the FBI. While an improvement, we still consider the 2014 guidance to be an undue prior restraint on the freedom of speech. These guidelines, now codified as part of the USA FREEDOM Act, allow companies to disclose the number of NSLs and FISA orders as a single number in bands of 250, starting with 0-249.
National security orders received
Total accounts affected
FN1 In February 2013, the FBI served national security letter NSL-12-358696 on Cloudflare, requesting certain customer information. This NSL contained an administratively-imposed gag which prohibited Cloudflare from disclosing information about this NSL to anyone other than our attorneys and a limited number of our staff, under threat of criminal liability. In 2013, Cloudflare objected to the NSL and threatened to sue the U.S. Government to protect its customers’ rights. The FBI soon rescinded the NSL and withdrew the request for information. Cloudflare provided no customer information subject to NSL-12-358696; but nonetheless, the NSL's nondisclosure provisions remained in effect for nearly four years. The FBI delivered to Cloudflare a letter dissolving the 2013 gag order in December 2016. Now that the administrative gag order is no longer in effect, Cloudflare is disclosing receipt of the NSL in our second half 2016 report, along with a redacted copy of the NSL.
FN2 Since no information was provided in response to NSL-12-358696, the Total accounts affected figure remains unchanged.
Given the vast amount of information transiting of our global network, Cloudflare is mindful of the special and sensitive position we occupy with regard to our customers. Cloudflare is extremely mindful of the position and the responsibilities our customers have placed on us through their trust. While there has been a steady increase in the number of law enforcement requests since our first transparency report in 2013, this is due in part to the five-fold increase in the number of Cloudflare customer domains during that time period.
We will continue to publish this report on a semiannual basis. Please be advised that we may restate data as we go forward as more complete information becomes available or if we change our classifications. This page will always contain the most recent version of our Transparency Report. Archival reports will be available from this page.