The right to be forgotten is one of the most discussed privacy tools in the world and one of the most misunderstood. It does not erase articles. It does not apply in the United States. It fails far more often than it succeeds for news content. This guide covers exactly what it is, where it applies, how to use it, and what to do when it does not work for you.
The right to be forgotten de-indexes URLs from Google search results -- it does not force publishers to remove articles. The source article remains live on the web; only its visibility in EU/UK Google search is affected.
It applies only to EU and UK residents. US residents have no equivalent federal right. California's CCPA offers a narrower right to delete, not a right to de-index news articles. See the US guide.
Most requests for news articles fail because of the public interest exemption. GDPR Article 17(3)(a) carves out freedom of expression and journalism. Google applies this broadly for any content touching matters of public concern.
Even a successful RTBF request only covers EU/UK versions of Google -- not google.com. And it does nothing to stop AI tools such as ChatGPT from surfacing the information. See the AI guide.
For most people -- EU, UK, or US -- source removal through direct engagement with the publisher is the most effective and durable path. De-indexing alone leaves the article reachable and AI-accessible.
The right to be forgotten is a data privacy right that allows individuals to request that search engines remove specific URLs from their search results. The underlying content is not deleted from the internet -- the publisher's article stays on their website. What changes is that the URL becomes invisible in Google search results when someone in the EU or UK searches for the individual's name.
The right has a precise legal origin. On May 13, 2014, the European Court of Justice issued its ruling in Google Spain SL v. Agencia Espanola de Proteccion de Datos (AEPD). The case involved a Spanish citizen named Mario Costeja Gonzalez who objected to Google returning links to a 1998 newspaper notice about his property being auctioned to pay social security debts. The ECJ held that search engines are data controllers under EU law and that individuals can request de-indexing of links that are "inadequate, irrelevant or no longer relevant, or excessive in relation to the purposes for which they were processed."
That 2014 ruling was significant but had no binding legislative text behind it. The right was formally codified in law when the General Data Protection Regulation (GDPR) took effect on May 25, 2018. GDPR Article 17 is titled "Right to erasure ('right to be forgotten')" and gives EU residents a statutory right to request deletion of personal data under specific conditions. Article 17 is the legal foundation that all RTBF requests now rest on for EU residents.
After the United Kingdom left the European Union, it retained GDPR in its domestic law as UK GDPR. The right to be forgotten under UK GDPR mirrors Article 17 closely. UK residents submit requests through the same Google form and appeal to the Information Commissioner's Office (ICO) if requests are rejected. See our detailed guide to the UK ICO process for specifics.
The phrase "right to be forgotten" does not appear verbatim in GDPR. The regulation uses "right to erasure." In practice, "right to be forgotten" has become the universal shorthand for RTBF requests submitted to Google and other search engines seeking de-indexing. It is also used loosely to describe source removal requests, but those are a separate process governed by editorial and legal standards rather than GDPR.
Understanding the precise scope of what an RTBF request achieves is essential before investing time in the process. The gap between what people expect and what actually happens is significant.
What it does: A successful RTBF request causes Google to de-index specific URLs from search results when a user performs a name-based search from an EU or UK IP address. If someone in France searches your name, the de-indexed article will not appear. The same applies to google.co.uk searches for UK residents. This can meaningfully reduce visibility for a specific, named individual in jurisdictions where RTBF applies.
What it does not do: The article remains fully live on the publisher's website. Anyone who navigates directly to the URL, shares the link directly, or accesses the article through any channel other than a European Google name search can still read it. Furthermore, the de-indexing applies only to European versions of Google -- google.fr, google.de, google.co.uk, and so on. It does not affect google.com, which is the version most US users, and many globally, default to.
For a request targeting a news article, the publisher is typically not notified of a successful de-indexing. The article stays on their server exactly as it was. What changes is only Google's index entry for that URL under name-based searches in covered jurisdictions.
A successful RTBF de-indexing in the EU does not remove the article from google.com. US-based searchers, global travelers using VPNs set to US servers, and anyone accessing the non-European version of Google will continue to see the article in full. For most public-facing individuals with an international reputation, source removal remains the only approach that addresses all search contexts simultaneously.
Eligibility for the RTBF is determined by two factors: your geographic location and the legal basis on which you invoke it.
If you are a resident of an EU member state, you have full RTBF rights under GDPR Article 17. Your national data protection authority (DPA) is the regulatory body that oversees your rights. If Google rejects your request, you can escalate to your country's DPA -- the CNIL in France, the BfDI in Germany, the Garante in Italy, the AEPD in Spain, and so on. See our full guide to which countries have this right.
Post-Brexit, UK residents retain the right to be forgotten under UK GDPR. The process is nearly identical to the EU process. The regulator for appeals is the Information Commissioner's Office (ICO). Our guide to the UK ICO process walks through the specific steps.
This is the most important clarification in this guide. The right to be forgotten, as defined in GDPR Article 17, does not apply to US residents. There is no equivalent federal US law that gives individuals the right to compel Google to de-index news articles. If you are a US resident whose name appears in an online article, submitting a GDPR RTBF form to Google will fail -- Google will reject it on jurisdictional grounds.
California residents have additional rights under the California Consumer Privacy Act (CCPA), but those rights are narrower in scope and do not create a right to de-index news articles from Google. Our guide to California and CCPA explains what those rights actually cover and why they do not function as an RTBF equivalent. For US residents, the primary tool for addressing harmful online news content is direct engagement with publishers through the editorial removal process -- which is what RemoveNews.ai specializes in. See our full guide to what does the right to be forgotten apply in the US.
If you are based in the United States and an article is damaging your reputation, the RTBF form will not help you. Your primary options are: (1) requesting editorial removal or correction directly from the publication, (2) pursuing Google de-indexing for limited technical grounds such as outdated content policies or violations of Google's own content policies, and (3) implementing a search suppression strategy that builds positive, authoritative content to push the article down in rankings. Our team at RemoveNews.ai handles all three approaches.
GDPR Article 17 does not create a blanket right to erase any personal information you dislike. It specifies six grounds on which a request can be based, and it includes exceptions that frequently defeat requests about news articles.
Even when one of the six grounds above is met, GDPR Article 17(3) lists exceptions that can override the erasure right. The most consequential for news articles is Article 17(3)(a): the right to be forgotten does not apply where processing is necessary for exercising the right to freedom of expression and information.
Google applies this exception through a proportionality test that weighs the subject's privacy interest against the public's interest in access to the information. The key factors Google considers include: whether the person is a public figure, whether the content concerns their public role or their private life, whether the information is outdated or stale, whether the underlying events remain matters of ongoing public concern, and whether the person has a criminal record for serious offenses.
For news articles about public figures -- executives, politicians, entertainers, or professionals in regulated industries -- the proportionality test almost always favors the public interest. Google's rejection rate for RTBF requests is high overall, and it is higher still for requests targeting journalism about people who voluntarily entered public life. See our guide on the GDPR right to erasure for news articles for a deeper analysis of how Google applies this test in practice.
Private individuals with no public role have a significantly stronger position. If you are not a public figure, if the article concerns your private life rather than your professional conduct, if substantial time has passed since the events described, and if there is no ongoing public interest in the matter, a request has a meaningful chance of success.
Among all categories of news article content, those covering criminal records -- particularly arrests without conviction, charges that were dropped, acquittals, and spent convictions -- have the highest RTBF success rate under GDPR. The reasoning is clear: an individual who was charged but not convicted has not had their guilt established, and the continuing presence of an article that implies otherwise serves minimal legitimate public purpose relative to the significant ongoing harm to the individual.
Several EU and UK data protection authorities have taken strong positions supporting RTBF requests for spent convictions, arrests without conviction, and juvenile criminal records. The UK ICO in particular has issued guidance indicating that for minor historical offenses, especially where rehabilitation has occurred, de-indexing requests should be given substantial weight.
The counterbalancing factor is the seriousness and public interest nature of the original crime. A conviction for a serious violent offense or financial crime affecting many victims is unlikely to be de-indexed, even after the sentence is served. A minor conviction from years ago with no repeat offending presents a very different calculus. Our dedicated guide to criminal records and the right to be forgotten walks through the specific analysis for each scenario.
If you were arrested but never charged, or charged but acquitted, your RTBF claim is among the strongest available under GDPR and UK GDPR. An arrest or charge without a resulting conviction is precisely the category of "inadequate, irrelevant or no longer relevant" information the 2014 Google Spain ruling was designed to address. Pair the RTBF request with a request to the publisher for removal or correction to address both the search index and the source simultaneously.
The process for submitting a right to be forgotten request to Google is relatively straightforward. Executing it effectively -- with supporting documentation and a well-framed legal argument -- is where outcomes diverge. Our step-by-step guide to how to file the Google request covers the complete process. Here is the overview.
Timeline expectations are important to set correctly. A straightforward request that Google approves can result in de-indexing within weeks. A contested request that proceeds through DPA complaint resolution can take twelve months or more. Plan accordingly and do not rely on RTBF as a rapid solution to an active reputation crisis.
For those who want a ready-made framework for the submission itself, our GDPR request template provides a legally structured letter format that covers the key elements Google's reviewers look for.
A rejection from Google does not mean the process is over. It means you have moved to the next stage: escalation to a data protection authority. Each EU member state and the UK have their own DPA with authority to investigate RTBF complaints and order Google to comply if the DPA determines the rejection was incorrect.
The most active DPAs for RTBF enforcement include the CNIL (France), the ICO (UK), the BfDI (Germany), the Garante (Italy), and the AEPD (Spain). These authorities have each issued decisions compelling Google to de-index URLs that Google had initially refused to remove. The DPA complaint process is slower than the initial request -- most DPAs take six months to over a year to resolve complaints -- but it carries regulatory weight that a self-filed Google form does not.
To file a DPA complaint, you will typically need to demonstrate that you have already submitted a request to Google and received a rejection. Most DPAs have online complaint portals. You will need to explain the grounds for your request, provide Google's rejection response, and make the case for why Google's decision was wrong under the applicable legal standard.
DPA complaints are time-consuming and outcomes are not guaranteed. Even a DPA ruling in your favor may take over a year to produce actual de-indexing. During that entire period, the article remains visible in Google search results. For individuals facing active reputation damage, the editorial removal path -- going directly to the publisher to request removal or correction -- typically produces faster and more complete results, and it addresses the source rather than just the search index.
A point that is frequently overlooked even by applicants who understand the RTBF process: a successful de-indexing under GDPR applies only to EU and UK versions of Google search. Google geographically limits RTBF de-indexing to European search properties. This is consistent with the territorial scope of GDPR itself and with Google's longstanding position on the geographic reach of de-indexing orders.
In practical terms, this means a user searching on google.com from New York, a user searching from Tokyo, or a user using a VPN that routes through the United States will continue to see the de-indexed article in their search results. The de-indexing applies when a search is performed from within EU/UK territory using an EU/UK version of Google.
The French data protection authority (CNIL) attempted to extend RTBF obligations to all versions of Google globally. Google challenged that position, and in 2019 the ECJ ruled that GDPR does not require global de-indexing, only European de-indexing. This ruling settled the territorial question: RTBF is a European right with European reach.
For individuals whose reputation concern is primarily among a US-based audience -- business contacts, employers, clients -- the RTBF process offers essentially no protection even if it succeeds. Their audience is searching on google.com, which is unaffected.
The landscape of online information retrieval has changed substantially with the rise of AI-powered search and large language models. Tools like ChatGPT, Claude, Gemini, and AI-powered search features in Google and Bing now surface information from their training data in response to queries about individuals. This creates a dimension of information exposure that RTBF cannot address.
An RTBF de-indexing has no effect on AI model training data. These models were trained on large datasets scraped from the web, including news articles, before the de-indexing occurred. The information encoded in the model's weights remains there regardless of what happens to the source URL's index status. A user who asks ChatGPT about a person may receive information drawn from an article that was successfully de-indexed from European Google years ago.
This is a critical gap that is likely to grow in importance as AI-powered search becomes more prevalent. The only durable solution to AI exposure is source removal from the original publisher. When the source article is removed from the web, it is less likely to be re-crawled and incorporated into future model training, and it disappears from cached versions that AI tools draw on.
Our guide to ChatGPT and AI covers the emerging landscape of AI-based information retrieval and what individuals can do to address it. The intersection of RTBF and AI is one of the most active areas of data protection policy in 2026, with several EU DPAs actively investigating AI companies' handling of RTBF-related personal data.
Even if you obtain a successful RTBF de-indexing from Google, a journalist or researcher using an AI tool that was trained before the de-indexing can still retrieve the information. Source removal from the original publisher is the only approach that addresses the full information lifecycle: the original indexed URL, cached web copies, and AI training pipelines. For individuals with significant AI exposure concerns, editorial removal should be pursued simultaneously with or before any RTBF filing.
The following table summarizes RTBF applicability, the best available path, and realistic timelines for the most common scenarios.
| Who You Are | Does RTBF Apply? | Best Path | Expected Timeline |
|---|---|---|---|
| EU Resident (private individual) | Yes | GDPR Article 17 request to Google; DPA complaint if rejected; editorial removal to address source | Weeks to 12+ months depending on Google/DPA response |
| UK Resident (private individual) | Yes (UK GDPR) | Google RTBF form; ICO complaint if rejected; editorial removal for source | Weeks to 12+ months; ICO complaints average 6-12 months |
| US Resident | No | Editorial removal from publisher; Google deindex via content policy violations if applicable; search suppression | 3-12 months depending on publisher and approach |
| US Resident in California | No (CCPA is different) | CCPA applies to personal data held by businesses -- not news article de-indexing; use editorial removal path | 3-12 months; CCPA rights do not affect news search results |
| Criminal Record Subject (EU/UK) | Often Yes | RTBF request citing Article 17(1)(a) and rehabilitation; DPA complaint with criminal justice context; editorial removal | Weeks to 9 months; acquittals and dropped charges have highest success rate |
| Public Figure (EU/UK) | Rarely | RTBF may apply to genuinely private matters; public role content almost always denied; editorial removal or suppression | If RTBF succeeds: weeks; if denied: suppression is 6-18 months |
| Private Individual (EU/UK, stale content) | Likely Yes | RTBF citing Article 17(1)(a) -- information no longer relevant; pair with editorial removal request for full resolution | Weeks to 6 months; older, less public-interest content succeeds at higher rates |
Not sure which path applies to you? Our specialists assess your situation across RTBF eligibility, editorial removal prospects, and search suppression options -- and tell you which path will actually move the needle.
Get a Free AssessmentThis article is the hub of our comprehensive right to be forgotten content cluster. Each spoke article below covers a specific dimension of the topic in depth. Use this index to navigate directly to the guide most relevant to your situation.
RTBF de-indexing is one tool in a larger strategy. Our team addresses the full picture: source removal from publishers, Google de-indexing where applicable, and search suppression to protect your reputation across every search context.
Free assessment. Confidential. No obligation.