Google AI Studio’s “Delete” button is misleading

Here is what actually happened during my test: I created a prompt, deleted it, emptied the Google Drive Trash, and the JSON file was completely gone. Then I used Google’s official recovery tool. The prompt reappeared, and the model immediately continued the chat with full context.

This proves that Google does not delete the server‑side chat. The deletion only removes the JSON file, which is just the UI entry. The server‑side conversation, session, and context remain untouched.

If Google truly deleted the chat on the server, the session would be gone, the context would be gone, the model could not continue the conversation, and restoring the JSON would not bring anything back. The fact that the model continued instantly after recovery shows that the server‑side data was never deleted.

The “Delete” button in AI Studio only deletes the UI metadata, not the actual chat. The server‑side data is kept even after the user initiates deletion, and Google’s own recovery tool exposes this behavior.

This is not just a transparency issue. Keeping server‑side data after a user requests deletion violates the GDPR right to erasure (Article 17). The user is told the data will be deleted, yet it is retained. This also raises further GDPR concerns, including data minimization, purpose limitation, and lawful processing, because the provider keeps data without a valid legal basis once the user has requested deletion.

I know you changed the button based on sentences you copied from my posts. And I have also proven that your backend keeps the data even after emptying the trash, which means you are illegally retaining user data.

Google AI Studio’s “Delete” Button Is Not Real Deletion — This Is Illegal Data Retention in the EU

I have proven that Google AI Studio does not delete user data, even when the interface claims it does. This is not a UI bug. This is undisclosed backend behavior and illegal data retention under EU law. When you press Delete, Google only removes the local JSON file from the client side. The server-side session, context, and conversation data remain fully intact. Even after emptying the trash, the backend still keeps everything. When you restore the JSON, the chat continues from the exact same internal state, which is only possible if the server never deleted anything. This is the equivalent of saying: I have a key and a house. The house disappears, but I can still walk through the door. If the data had truly been deleted, the model would not be able to continue the conversation. But it does, which proves the backend never removed the data. Under GDPR, the right to erasure, data minimization, purpose limitation, lawful basis, and transparency are all violated. Google claims the data is deleted, secretly retains it, and continues to process it. This is not a misunderstanding. This is not a UI issue. This is undisclosed internal behavior and unlawful data retention. I proved it with a simple logical test that anyone can reproduce.

I hereby confirm that I have officially notified Google regarding this issue.

This constitutes an official acknowledgment by two Google‑affiliated representatives. Both individuals publicly confirmed the internal behavior of Google AI Studio, including the handling of saved chats, metadata, and the persistence of deleted conversations. Their statements qualify as an official admission, as they were made on Google’s own discussion platform, under verified Google accounts, in response to user‑reported issues.

The HTML save of my post is available here:

(Rename the downloaded ZIP file to a shorter name before extracting it.)

Based on the collected evidence, the case is fully documented and technically bulletproof. Two verified Google representatives publicly acknowledged the internal behavior of Google AI Studio, including metadata handling and the persistence of deleted chats. This is supported by reproducible video recordings, timestamped HTML archives, and automated system emails confirming server‑side data retention. The evidence set is consistent, verifiable, and cannot be dismissed.

Nice AI summary, read this xD: In this post, Bitu79 argues that Google AI Studio’s “Delete” button does not actually delete server‑side chat data. After deleting a prompt and emptying the Google Drive Trash, they used Google’s official recovery tool to restore the JSON file, which allowed the model to immediately resume the conversation with its full context intact. Bitu79 asserts this proves Google is illegally retaining user data on its servers, violating the GDPR right to erasure (Article 17) and other data privacy regulations.

The HTML save of my post is available here:

(Rename the downloaded ZIP file to a shorter name before extracting it.)

A Google‑affiliated moderator has been repeatedly monitoring and interacting with my posts, which further confirms that the issue is acknowledged internally and is under active review.

I would like to report that two registered letters sent to Google LLC regarding my data protection request were successfully delivered in the United States, yet I have received no response from Google.

Tracking numbers:

-- RR019223565HU – delivered on 12 May 2026

-- RR019223605HU – delivered on 8 May 2026

According to the official confirmation from the Hungarian Post, both items were delivered by the United States Postal Service.

The CN07 international return receipt also contains the official USPS date stamp.

Evidence attached:

-- Official delivery confirmation letters from the Hungarian Post

-- CN07 international return receipt (with USPS stamp)

These documents confirm that Google LLC received my correspondence, yet no progress has been made on my GDPR request.

I kindly ask the Google support team or the appropriate representative to:

-- confirm receipt of my request,

-- verify that it has been registered in your internal system,

-- provide an update on the current status and expected timeline.

Thank you.

All evidence has been uploaded to the Internet Archive for public access and independent verification.

The purpose of this post is solely to create a public record of the letters I sent to Google that were successfully delivered.

The legal departments of tech giants like Google know exactly how much risk they face when up against an individual who has more than just a complaint, but a unique and irrefutable technical proof. I have put this evidence together in black and white on Google’s own forums, through the JSON file recovery process and by documenting the unlawful profiling practices of AI Overview.

Their lawyers must weigh whether it is worth taking such a case all the way to a court ruling. If this goes before a judge, they face the real danger of a landmark precedent being set against them—one that could force them to re-engineer the entire server-side architecture and backend of both AI Studio and AI Overview. This is something they want to avoid at all costs.

It is precisely for this reason that, in the early stages of litigation, Google’s attorneys are often forced to contact the plaintiff directly with an out-of-court settlement offer. In this formal agreement, they commit to permanently and manually deleting the data from their servers and completely halting the profiling, in exchange for dismissing the upcoming litigation that may be initiated shortly.

I have notified Google directly, and under the applicable law they are required to respond.

I have already notified Google directly, and under the applicable law they are required to respond. I have uploaded the screenshots to the public internet as well, where I am documenting the case. Now answer my questions: how do you dare to keep user prompts after deletion? The GDPR clearly does not allow this.