Right to be forgotten requests remain concentrated on search engine delisting rather than full source removal. Google has processed millions of these requests since 2014, and most come from private individuals. This page covers the right to be forgotten under GDPR Article 17 before you pay for removal tools.
The headline numbers matter because people often confuse delisting with deletion. A search engine may remove a link, but the source page remains live. GDPR Article 17 creates an erasure right, yet search engines only control their own indexes. If you want source-level removal, compare data removal services or contact each site directly.
US readers should not assume the EU right applies at home. California’s CCPA deletion rules create some obligations, but exemptions remain. Start with our guide to opting out of data brokers if you want to reduce exposure in people search databases.
Key Right to Be Forgotten Statistics 2026
| Stat | Detail | Source |
|---|---|---|
| Millions | Google has processed right-to-be-forgotten deletion requests since 2014. | Google Transparency Report, 2024 |
| Majority | Most RTBF requests come from private individuals seeking removal of personal data. | Google Transparency Report, 2024 |
| Broad right | GDPR Article 17 grants broad erasure rights across the EU. | GDPR, 2018 |
| Delisting only | Search engine delisting does not remove the underlying content from the source site. | Google Transparency Report |
What Google’s Request Data Shows
| Stat | Detail | Source |
|---|---|---|
| Request volume | Millions of deletion requests have been processed since 2014. | Google Transparency Report, 2024 |
| Who files | The majority are private individuals, not businesses or public figures. | Google Transparency Report, 2024 |
| Legal basis | GDPR Article 17 provides the core erasure right for EU residents. | GDPR, 2018 |
| Technical result | Google delists URLs from its search results. The original page stays online. | Google Transparency Report |
What Delisting Does Not Do
| Stat | Detail | Source |
|---|---|---|
| Source page | Search engine delisting does not remove the underlying content from the source site. | Google Transparency Report |
| Request type | Most RTBF requests come from private individuals seeking removal of personal data. | Google Transparency Report, 2024 |
| Legal limit | GDPR Article 17 grants broad erasure rights across the EU, but delisting is not full source deletion. | GDPR, 2018 |
Frequently Asked Questions
What is the right to be forgotten?
The right to be forgotten is an EU privacy right under GDPR Article 17. It lets individuals ask for erasure of personal data in certain situations. For search engines, this usually means delisting links rather than deleting source content.
Does Google delete the original content?
No. Google delists search results but does not remove the underlying page from the source website. To remove content at the source, you must contact the website owner or use a data removal service.
Who files the most right to be forgotten requests?
The majority of requests come from private individuals. These people ask Google to remove search links to personal data such as home addresses, names, or sensitive private details.
Is the right to be forgotten available in the United States?
There is no direct US federal equivalent to GDPR Article 17. California’s CCPA provides limited deletion rights, but many exceptions apply. US consumers often use data removal services to reduce exposure in broker databases.
How long does a Google delisting request take?
Google does not publish a fixed processing time for all RTBF cases. Each request is reviewed against GDPR criteria, privacy interests, and public interest. The volume is millions, so complex requests may require additional review.
