Miért pontozzátok le? Ja,hogy Google fanok vagytok! Értem már! Akkor nyalogassátok ti is a Google talpát....

https://d3qe71uytubmmx.cloudfront.net/original/3X/d/2/d2616473355c728e552b3e242ea849e5cee0f08a.jpeg

You're not even a mod, stop acting like an unpaid hall monitor. If you don't like the post, just keep scrolling. xD

You're not even a mod, stop acting like an unpaid hall monitor. If you don't like the post, just keep scrolling. xD

You're not even a mod, stop acting like an unpaid hall monitor. If you don't like the post, just keep scrolling. xD

You're not even a mod, stop acting like an unpaid hall monitor. If you don't like the post, just keep scrolling. xD

Using a browser to audit Google's tools doesn't give a corporation the legal right to fake a 'Delete' button and illegally hoard data in violation of GDPR Article 17. If your best counter-argument is inspecting my taskbar icons instead of the actual forensic evidence, you've already lost.

Google AI Studio’s “Delete” button is misleading and does not do what users expect. I documented the entire process — from deletion to recovery — in three separate videos:

First part: https://youtu.be/LBQfNbPCxQw
Second part: https://youtu.be/m4U6ajKuLRo
Third part: https://youtu.be/8Pg-7eNPUWM

During the test, I created a prompt, deleted it, and then permanently removed the JSON file from Google Drive by emptying the Trash. The file was completely gone. After that, I used Google’s official recovery tool. The JSON file came back, and the model immediately continued the conversation with full context.

This can only mean one thing: Google does not delete the server‑side chat, even when the user explicitly requests deletion. The “Delete” button only removes the client‑side JSON pointer that appears in the UI. The server‑side session, context, and conversation state remain intact.

If the backend had truly deleted the chat, then:

the session would be gone,

the context would be gone,

the model would not be able to continue the conversation,

restoring the JSON would do nothing.

The fact that the model instantly continues the conversation proves that the server‑side data was never deleted.

This is not a simple UI bug. It is undocumented backend behavior that violates the GDPR right to erasure (Article 17). The user is told the data will be deleted, yet Google continues to retain and process it. This raises further GDPR concerns: data minimization, purpose limitation, lack of lawful basis, and transparency issues.

The question is simple:
Why does Google keep server‑side chat data even after the user explicitly requests deletion?

The developer and Google are quietly avoiding the issue: they are fully aware of the question, yet they still refuse to respond. All evidence is documented here:
https://discuss.ai.google.dev/t/noyb-has-contacted-me-google-should-start-sweating-repost-2/176524

@ all: Downvotes don’t delete a single byte from my archives, they don’t invalidate my videos, and they don’t affect my EU registration numbers in the slightest—kiss Google’s ass!

@ all: Downvotes don’t delete a single byte from my archives, they don’t invalidate my videos, and they don’t affect my EU registration numbers in the slightest—kiss Google’s ass!

@ all: Downvotes don't delete a single byte from my archives, they don't invalidate my videos, and they don't affect my EU registration numbers in the slightest—kiss Google's ass!

Knowing a company is shady is not the same as catching them red-handed with forensic evidence and forcing their internal systems into an admission. Cynicism doesn't hold corporations accountable; evidence does. 😆