Does the GDPR right to erasure apply to AI chatbots?

Yes. Providers serving EU users must erase your stored personal data — account details, chat history, uploaded files — on request, normally within one month. The unresolved part is the model itself: data absorbed into trained weights currently cannot be deleted, only filtered out of responses.

Can OpenAI delete what ChatGPT "knows" about me?

Not from the model weights. OpenAI offers a Personal Data Removal Request form that can stop information about you from appearing in responses, but this works by filtering outputs — the underlying trained parameters are unchanged. OpenAI itself told regulators it can block, not correct, model outputs about a person, which is the basis of pending noyb complaints.

If I delete my chats, is my data gone from the AI?

Your stored copies are deleted on the provider's schedule (typically within about 30 days, absent a legal hold). But if those chats were already used in a training run, deletion does not untrain the model. A training opt-out only protects future conversations.

Is an AI model itself "personal data" under the GDPR?

It can be. EDPB Opinion 28/2024 says a model trained on personal data is not automatically anonymous — anonymity must be shown case by case, considering whether personal data can be extracted from the model or elicited through queries. If a model fails that test, GDPR obligations apply to it in principle.

Does Secret Chat hold chat data I would need to ask it to erase?

No. Your conversations and files are stored only in your own browser, not on Secret Chat's servers, and your queries reach the model providers anonymously — never linked to your email or identity. The content of your messages still reaches the providers verbatim, so redacting sensitive details before sending remains your responsibility.

GDPR and AI Chatbots: The Right to Erasure

Published July 23, 2026

This article is general information, not legal advice. Data protection law differs by country and is evolving quickly around AI. For your own situation, consult a qualified lawyer. Your use of Secret Chat is governed by our Terms of Service and Disclaimers.

The GDPR's right to erasure (Article 17) applies in full to the data an AI provider stores about you — your account, your chat logs, your uploaded files. That part a provider can and must delete on request, normally within one month. But the right collides head-on with how large language models are built: once personal data has been absorbed into a model's weights during training, no provider today can surgically remove it. What you actually get instead is output filtering — the model is instructed not to repeat certain facts about you — while the trained parameters stay exactly as they were. European regulators have refused to declare trained models automatically "anonymous" (EDPB Opinion 28/2024), Italy has already fined OpenAI €15 million over ChatGPT's data practices, and two formal complaints by the privacy group noyb turn precisely on OpenAI's admission that it can filter, but not correct or erase, what the model "knows". This article explains what the law says, what actually happens to an erasure request, and what it means for what you type into a chatbot.

What Article 17 Actually Says

The right to erasure — popularly the "right to be forgotten", a phrase that entered EU law with the Court of Justice's 2014 Google Spain ruling on search results — is set out in Article 17 GDPR. A person can require a controller to erase their personal data "without undue delay" when one of the listed grounds applies, including:

the data is no longer necessary for the purpose it was collected for;
the person withdraws consent and there is no other legal basis;
the person objects to processing based on legitimate interests and no overriding grounds exist;
the data was processed unlawfully in the first place.

Under Article 12(3), the controller must act on the request within one month (extendable by two more for complex cases). Article 17(3) carves out exceptions — freedom of expression, legal obligations, public-interest archiving, and the establishment or defence of legal claims. And the enforcement stick is real: violations of data-subject rights sit in the top fine bracket, up to €20 million or 4% of global annual turnover.

None of this was written with neural networks in mind. The GDPR assumes data lives in records that can be located and deleted. An LLM breaks that assumption in a very specific way.

Where Your Personal Data Actually Lives When You Use an LLM

To see what erasure can and cannot reach, separate the three places personal data exists in an AI chatbot system:

1. Your account and chat data. Your email, payment details, conversation history, uploaded files, and usage logs, stored in ordinary databases. This is classic personal data. Erasure works here the way the GDPR intends: the provider locates the records and deletes them.
2. The training corpus. The datasets the model was trained on — web scrapes, licensed archives and, at several providers, users' own chats. Data can be deleted from a stored corpus, but that only affects future training runs. It does nothing to models already trained.
3. The model weights. Billions of numerical parameters encoding statistical patterns learned from the corpus. There is no row in a database that says your name — yet models demonstrably memorize and reproduce facts (true and false) about real people. This is where the right to erasure currently has no working mechanism.

Most "delete my data" conversations mix these three layers together. Providers answer for layer 1, regulators are arguing about layer 3, and layer 2 quietly determines what the next model will know about you.

The Easy Part: Erasing Your Account and Chats

For layer 1 the mechanics are established. Major providers let you delete individual conversations or your whole account, and typically state that deleted data is removed from their systems within about 30 days. Two caveats keep this from being as clean as it sounds:

Deletion is a schedule, not an instant. "Temporary" and deleted chats generally persist in backend systems for a retention window first — we walked through the fine print of those windows in "Temporary Chat" Isn't What You Think.
A legal hold overrides your delete button. When litigation intervenes, courts can order chats preserved despite deletion — as the order covering roughly 20 million ChatGPT logs showed in the New York Times case, covered in Your AI Chats Can Be Subpoenaed.

One more structural nuance: this all describes consumer products, where the provider is the data controller. On business and API tiers, the provider usually acts as a processor for the customer — so if your employer wires a chatbot into its tools, your erasure request goes to the employer, not the AI company.

The Hard Part: A Model Cannot "Forget" on Request

Model weights are not a database. Training distributes what the model learns across billions of parameters; no engineer can point at the ones that "contain" you. That leaves three theoretical routes to erasure, none of which works today at frontier scale:

Retraining from scratch without your data would genuinely erase it — and costs months of computation on some of the most expensive infrastructure on earth. No provider will do this per request.
Machine unlearning — techniques to make a trained model behave as if specific data had never been in the corpus — is an active research field, but current methods either degrade the model, don't scale to LLMs, or can't prove the data is actually gone.
Output filtering is what providers actually deploy: guardrails instruct the model not to output information about a listed person. The data remains in the weights; the model is merely told not to say it.

Whether filtering satisfies Article 17 is one of the sharpest open questions in European data protection. Suppressing an answer is not the same as erasing the data — and that gap is exactly what the current complaints are about.

What Regulators Have Said So Far

The regulatory picture firmed up considerably between mid-2024 and today:

Hamburg's DPA lit the fuse (July 2024). In a discussion paper, the Hamburg Commissioner argued that LLM weights as such do not store personal data — tokens and embeddings are not "information relating to an identifiable person" — which would conveniently place the weights outside the GDPR. The position was influential and immediately contested.
The EDPB declined to agree (Opinion 28/2024, adopted 17 December 2024). Asked by the Irish supervisory authority, the European Data Protection Board held that an AI model trained on personal data cannot automatically be considered anonymous. Anonymity must be assessed case by case, and requires both that the likelihood of extracting personal data from the model (via attacks like membership inference or model inversion) is insignificant, and that queries cannot elicit identifiable personal data. If a model fails that test, the GDPR — including data-subject rights — applies to it in principle. The opinion also warned that unlawful processing during training can taint the model's later deployment.
Italy showed the price tag (23 December 2024). The Garante fined OpenAI €15 million, finding no appropriate legal basis for the personal data processed to train ChatGPT, transparency failures, insufficient age verification, and a failure to notify a March 2023 breach. OpenAI was also ordered to run a six-month public information campaign explaining, among other things, how users and non-users can exercise their rights to object, rectify and erase. OpenAI called the fine disproportionate and appealed — but the message to the industry stands.

The Test Cases: When ChatGPT Gets You Wrong

The right to erasure travels together with Article 16's right to rectification — and the pending complaints show why the pair is so hard for LLMs.

The birth-date complaint (Austria, April 2024). The privacy NGO noyb filed a complaint after ChatGPT repeatedly stated an incorrect date of birth for a public figure. OpenAI's answer, as recorded in the complaint, is the crux of this whole topic: it could not correct the specific fact — it could only filter, blocking responses about the person entirely. noyb argues that neither hallucinating false data nor all-or-nothing suppression is compatible with the GDPR's accuracy principle or with Articles 16 and 17.
The fake child-murderer (Norway, March 2025). Asked "Who is Arve Hjalmar Holmen?", ChatGPT invented a detailed story that this entirely ordinary Norwegian man had killed two of his sons and been sentenced to 21 years — wrapping the fabrication around real details like his home town and children. noyb's complaint asks the Norwegian DPA to order the false output eliminated and to fine OpenAI. OpenAI responded that newer, search-grounded versions no longer repeat the claim — which mitigates the symptom without answering the legal question of what remains in the model.

Both cases are undecided as of this writing. Whichever way they land, they will effectively define whether "we filtered it" counts as "we erased it" in Europe.

What an Erasure Request Actually Gets You Today

If you exercise your rights against a major AI provider now, the realistic outcomes are:

Account and chat deletion — real erasure. Your stored conversations, files and account records are deleted on the provider's stated schedule.
An output-suppression request — filtering, not erasure. OpenAI, for example, offers a "Personal Data Removal Request" form through its privacy portal, available under the GDPR and similar laws, to stop certain information about you from appearing in ChatGPT's responses (expect identity verification). Granted requests apply filters; the weights are untouched.
A training opt-out — protection for the future only. Turning off "improve the model for everyone" (or its equivalent) keeps your future chats out of training runs. It does not unwind any training that already used your past chats. Step-by-step instructions for every major platform are in our 2026 opt-out master guide.

The Direction Nobody Thinks About: What You Type In

Public debate focuses on data about you that models learned from the web. When you prompt an LLM, the data flows the other way too — and the same erasure problem applies:

Your prompts are personal data. A chat in which you describe your health, finances, relationships or workplace is a dossier in your own words, stored under your account and, on several consumer platforms, used for training by default.
Once a chat has been trained on, deleting it doesn't untrain the model. Erasure removes the stored copy; the completed training run keeps whatever it absorbed. The time to control this is before you send, not after.
Other people's data raises your own GDPR exposure. Pasting a client's, patient's or colleague's details into a consumer chatbot can make you (or your firm) the controller who just disclosed personal data to a third party without a basis. Purely personal household use is exempt from the GDPR — professional use is not. We cover the professional angle in our guide for lawyers and for business owners.

A Practical Playbook

What actually works, in order of leverage:

Minimize before you send. The only data guaranteed never to need erasure is data that never left your device. Strip names, identifiers and unique details from prompts — with any provider, this part is always your own responsibility.
Opt out of training everywhere you chat. It closes the layer-2 door for the future.
Use the formal channels. Start with an Article 15 access request (what do you hold about me?), then erasure for stored data and the provider's removal form for outputs. The one-month clock applies.
Delete chats routinely anyway. Ordinary deletion still shrinks what a breach, subpoena or future training run could reach — see our 13-provider retention audit for who keeps what, for how long.
Escalate if ignored. A refused or ignored request can go to your national data protection authority — that route is free, and it is exactly how the noyb cases got moving.
Prefer tools that don't build the archive in the first place. Erasure is a remedy for stored data; the stronger position is that there is nothing stored to remedy.

How Secret Chat AI Fits — and Its Honest Limits

That last point is the design principle behind Secret Chat AI, so here is the honest version of what it does and does not change about this article.

What it does. Secret Chat keeps no server-side archive of your conversations — chats and files live only in your own browser's local storage (IndexedDB and OPFS), so on our side there is no conversation history to erase, subpoena or breach; deleting it is a local action you perform yourself, instantly, no one-month clock. And Secret Chat is an anonymizer: it builds no profile of you, no chat is ever associated with you, and your queries reach the top LLMs anonymously — your email is used only for account access and payment, never linked to your prompts, and queries are never used for training. So even where a model provider briefly retains API data under its own terms, that log is not tied to your name, account or IP — you use the model as a stranger.

What it does not do. Secret Chat AI removes you from your queries — it does not remove the data from your messages. Whatever you type still reaches the model provider verbatim (anonymously, but verbatim), and that provider processes it under its own terms. Anonymization does not exempt anyone from the GDPR: if you paste someone else's personal data into a prompt, the legal responsibility for that disclosure is yours, and redacting identifying details before sending remains your job with Secret Chat exactly as with any other tool. What changes is your side of the erasure problem: no profile of you accumulates anywhere, and no archive of your words sits on our servers waiting for an Article 17 request.

Frequently Asked Questions

Does the GDPR right to erasure apply to AI chatbots?
Yes. Providers serving EU users must erase your stored personal data — account details, chat history, uploaded files — on request, normally within one month. The unresolved part is the model itself: data absorbed into trained weights currently cannot be deleted, only filtered out of responses.
Can OpenAI delete what ChatGPT "knows" about me?
Not from the model weights. OpenAI offers a Personal Data Removal Request form that can stop information about you from appearing in responses, but this works by filtering outputs — the underlying trained parameters are unchanged. OpenAI itself told regulators it can block, not correct, model outputs about a person, which is the basis of pending noyb complaints.
If I delete my chats, is my data gone from the AI?
Your stored copies are deleted on the provider's schedule (typically within about 30 days, absent a legal hold). But if those chats were already used in a training run, deletion does not untrain the model. A training opt-out only protects future conversations.
Is an AI model itself "personal data" under the GDPR?
It can be. EDPB Opinion 28/2024 says a model trained on personal data is not automatically anonymous — anonymity must be shown case by case, considering whether personal data can be extracted from the model or elicited through queries. If a model fails that test, GDPR obligations apply to it in principle.
Does Secret Chat hold chat data I would need to ask it to erase?
No. Your conversations and files are stored only in your own browser, not on Secret Chat's servers, and your queries reach the model providers anonymously — never linked to your email or identity. The content of your messages still reaches the providers verbatim, so redacting sensitive details before sending remains your responsibility.

Conclusion

The right to erasure was designed for a world where data sits in records; LLMs moved part of it into weights, where today it can be masked but not removed. The stored layer of your data — accounts, chats, files — remains fully within your GDPR rights, and you should use them. The model layer is being fought over right now, in the EDPB's anonymity test, Italy's €15 million fine, and the noyb complaints heading through Austrian and Norwegian regulators. Until that fight resolves, the practical conclusion is unglamorous but solid: the strongest privacy right is the one you never have to invoke. Send less, opt out of training, delete what you can — and prefer tools that keep no archive of your words and no link between your words and your name.

GDPR and AI Chatbots
What "Right to Erasure" Means When You Prompt an LLM