Skip to content

Transparency report

This page explains the principles used when a government or law-enforcement body asks for customer data, defines the main request types, and presents the disclosed request counts for the stated reporting period. It is written for customers, prospective customers, and legal or compliance reviewers who need to understand the request-handling approach and read the table correctly.

Guiding principles for handling requests

A transparency report is only useful if it tells readers how a data request will be handled before any specific request arrives. The framework below sets out the commitments that guide that handling, so customers and reviewers can judge individual decisions against a stated standard rather than an ad hoc response. It also records the wider position on privacy, user-data protection, constitutional guardrails, and judicial oversight of government data collection and surveillance, which informs how the commitments are applied in practice. The four commitments are: customer privacy and confidentiality are maintained; every legal process is reviewed, and requests lacking a legal basis or that are unclear, overbroad, or otherwise inappropriate are rejected or challenged; legal process is construed as narrowly as possible; and, where possible, customers and third parties are encouraged to obtain relevant data without the provider's intervention. Read together, these commitments describe a review posture rather than a set of outcomes: they explain what a request must satisfy, how far a response will reach, and when a requester will be pointed toward a route that does not involve the provider at all.

Requests for information through the legal process

The legal directory table below reports request counts by reporting period, request type, and disclosure category. Read it as a historical record for the stated period, not as a statement about current volumes. The table is reproduced with every original row and numeric cell.

How to read the request table

Use the following checklist when reviewing the table:

  1. Identify the reporting period and jurisdiction row before comparing counts.
  2. Match the request type to its definition in the next section; a search warrant, court order, subpoena, national security request, and MLAT request are not interchangeable.
  3. Read the two disclosure columns separately: one counts requests where both content and non-content data were disclosed, the other counts requests where only non-content data was disclosed.
  4. Treat a zero as a reported count for that row and period, not as a guarantee about future requests.

Worked example using the captured 2020 United States rows: for search warrants, court orders, subpoenas, national security requests, and civil subpoenas, the reported number of requests is 0, the reported content-and-non-content disclosure count is 0, and the reported only-non-content disclosure count is 0. The same zero pattern appears for foreign requests pursuant to an MLAT. This shows how the columns combine; it does not establish what any later period contains.

Definitions of request and data types

The following definitions explain the terms used in the table and in the principles above.

  • Civil Subpoena — A demand for information made in connection with civil litigation. The report states that content cannot be provided in response to a civil request without a valid, lawful exception, such as consent.
  • Content data — Data sent to the service, such as events, errors, stack traces, and any information the user includes in or attaches to those items.
  • MLAT — A Mutual Legal Assistance Treaty. A foreign government is expected to use appropriate international law processes, such as an MLAT, to obtain user data stored in the U.S.
  • National security requests — A National Security Letter issued under 18 U.S.C. § 2709, a court order issued under the Foreign Intelligence Surveillance Act, or any other classified request for user information issued in the U.S.
  • Non-content data — Basic account information such as name and email address, registration information, login history, and billing information.
  • Search warrant — An order issued by a judge or magistrate on a finding of probable cause. A search warrant is required to obtain the content of communications.
  • Law Enforcement Subpoena — A compulsory demand issued by a governmental entity for the production of documents or testimony in a criminal case, such as a grand jury subpoena or an administrative subpoena.
Legal directory table: requests for information through the legal process
Reporting periodType of requestNumber of requestsContent data and non-content data disclosedOnly non-content data disclosed
United States
1st January – 31st December 2020Search warrants000
1st January – 31st December 2020Court orders000
1st January – 31st December 2020Subpoenas000
1st January – 31st December 2020National security requests000
Civil Subpoenas000
Non-US Entities
Foreign requests pursuant to an MLAT000

Historical reference for the stated reporting period only; check current conditions and any later published report.

Frequently asked questions

What is the difference between content data and non-content data?

Content data is data sent to the service, such as events, errors, stack traces, and information the user includes in or attaches to those items. Non-content data is basic account information such as name and email address, registration information, login history, and billing information. The table reports disclosures in these two categories separately.

Is a search warrant the same as a law-enforcement subpoena?

No. A search warrant is an order issued by a judge or magistrate on a finding of probable cause, and it is required to obtain the content of communications. A law-enforcement subpoena is a compulsory demand issued by a governmental entity for documents or testimony in a criminal case, such as a grand jury or administrative subpoena.

What does MLAT mean in this report?

MLAT stands for Mutual Legal Assistance Treaty. A foreign government is expected to use appropriate international law processes, such as an MLAT, to obtain user data stored in the U.S.

What period does the report cover?

The first report covers requests from January 1, 2019 through June 30, 2021. The report states that updates are planned annually. The table itself shows a 2020 reporting period for the United States and a non-US entity row.

Reporting periodType of requestNumber of requestsContent data and non-content data disclosedOnly non-content data disclosed
United States
1st January – 31st December 2020Search warrants000
Court orders000
Subpoenas000
National security requests000
Civil Subpoenas000
Non-US Entities
Foreign requests pursuant to an MLAT000