1. Transparency Report
  2. Government Data Requests

United Kingdom

The numbers reported below represent requests from government agencies for user data received by Yahoo! UK Limited during the specified reporting period. Each Government Data Request was processed in a manner consistent with local law and the applicable Terms of Service and Privacy Policy.

Government Data Requests

United Kingdom chart

No Data Found Rejected Only NCD Disclosed Content Disclosed Total Government Data Requests Total Government Specified Accounts
156 435 679 417 1,687 2,488

Glossary

Government Specified Accounts

The number of Yahoo accounts, users, or other unique identifiers listed in a Government Data Request. This number is typically larger than the number of users and accounts actually involved because: 1) a single account may be included in more than one Government Data Request; 2) an individual user may have multiple accounts that were specified in one or more Government Data Requests; and 3) if a Government Data Request specified an account that does not exist, that nonexistent account would nevertheless be included in our count of Government Specified Accounts.

Government Data Request

Legal process to a Yahoo entity from a government agency seeking information about Yahoo accounts and/or the activity of Yahoo users within Yahoo products. The Government Data Requests reflected in this report are generally made in connection with criminal investigations.

Content

Data that our users create, communicate, and store on or through our services. This could include words in a communication (e.g., Mail or Messenger), photos on Flickr, files uploaded, Yahoo Address Book entries, Yahoo Calendar event details, thoughts recorded in Yahoo Notepad or comments or posts on Yahoo Answers or any other Yahoo property.

NCD

Non-content data such as basic subscriber information including the information captured at the time of registration such as an alternate e-mail address, name, location, and IP address, login details, billing information, and other transactional information (e.g., “to,” “from,” and “date” fields from email headers).

No Data Found

Yahoo produced no data in response to the Government Data Request because no responsive data could be found (i.e., the account didn’t exist or there was no data for the date range specified by the request).

Rejected

Yahoo may have possessed data responsive to the Government Data Request, but none was produced because of a defect or other problem with the Government Data Request (e.g., the government agency sought information outside its jurisdiction or the request only sought data that could not be lawfully obtained with the legal process provided). This category also includes Government Data Requests that were withdrawn after being received by Yahoo. We carefully review Government Data Requests for legal sufficiency and interpret them narrowly in an effort to produce the least amount of data necessary to comply with the request.

 

  • Government Data Requests

    United Kingdom chart

    No Data Found Rejected Only NCD Disclosed Content Disclosed Total Government Data Requests Total Government Specified Accounts
    156 435 679 417 1,687 2,488

    Glossary

    Government Specified Accounts

    The number of Yahoo accounts, users, or other unique identifiers listed in a Government Data Request. This number is typically larger than the number of users and accounts actually involved because: 1) a single account may be included in more than one Government Data Request; 2) an individual user may have multiple accounts that were specified in one or more Government Data Requests; and 3) if a Government Data Request specified an account that does not exist, that nonexistent account would nevertheless be included in our count of Government Specified Accounts.

    Government Data Request

    Legal process to a Yahoo entity from a government agency seeking information about Yahoo accounts and/or the activity of Yahoo users within Yahoo products. The Government Data Requests reflected in this report are generally made in connection with criminal investigations.

    Content

    Data that our users create, communicate, and store on or through our services. This could include words in a communication (e.g., Mail or Messenger), photos on Flickr, files uploaded, Yahoo Address Book entries, Yahoo Calendar event details, thoughts recorded in Yahoo Notepad or comments or posts on Yahoo Answers or any other Yahoo property.

    NCD

    Non-content data such as basic subscriber information including the information captured at the time of registration such as an alternate e-mail address, name, location, and IP address, login details, billing information, and other transactional information (e.g., “to,” “from,” and “date” fields from email headers).

    No Data Found

    Yahoo produced no data in response to the Government Data Request because no responsive data could be found (i.e., the account didn’t exist or there was no data for the date range specified by the request).

    Rejected

    Yahoo may have possessed data responsive to the Government Data Request, but none was produced because of a defect or other problem with the Government Data Request (e.g., the government agency sought information outside its jurisdiction or the request only sought data that could not be lawfully obtained with the legal process provided). This category also includes Government Data Requests that were withdrawn after being received by Yahoo. We carefully review Government Data Requests for legal sufficiency and interpret them narrowly in an effort to produce the least amount of data necessary to comply with the request.