The table below summarizes the National Security Requests we received during the six month periods between July 1, 2013 – June 30, 2016 . “National Security Requests” include National Security Letters and FISA court orders.
|National Security Requests Received||User Accounts Affected|
|2016: Jan 1 – Jun 30||None.||None.|
|2015: Jul 1 – Dec 31||None.||None.|
|2015: Jan 1 – Jun 30||None.||None.|
|2014: Jul 1 – Dec 31||None.||None.|
|2014: Jan 1 – Jun 30||None.||None.|
|2013: Jul 1 – Dec 31||0-249||0-249|
We are pleased to report that we received no National Security Requests during 2014, 2015, and so far in 2016.
For other periods, we don’t think the disclosures allowed by current Justice Department rules allow us to paint a truthful picture. Reporting National Security Requests in bands of 250 obfuscates rather than clarifies the volume of National Security Requests we and other small tech companies receive. While the disclosure regime may work well for larger companies with a high volume of requests, like the ones that worked with the Justice Department to craft these rules, they do not work well for smaller companies like Automattic.
Twitter is currently suing the Justice Department to disclose full, truthful information about the number of National Security Requests they receive. We fully agree with Twitter’s position in this lawsuit and joined with other companies to file this amicus brief to support their case.
By preventing us from sharing a more precise number of requests, the current disclosure rules diminish the trust that our users place in us and our services. For now, we are disclosing the maximum amount of information allowed by law.