Listen Google, we’re going to court soon! Hearing plan – clearly, without any nonsense

Gemini API
1

Based on the evidence collected in recent weeks, it is clear that Google AI Studio does not do what the user sees on the interface. “Deletion” does not actually happen; the system continues to keep the conversation alive in the background, and this affects millions of users.

At the hearing, I will present the following:

At the hearing, I will request:

  • The presentation of backend system logs, so it becomes clear what actually happened.

  • Official acknowledgment that deletion did not occur.

  • A public apology to all users, since this issue affects millions of people.

  • Full transparency of the process, including public access and media presence.

  • The temporary shutdown of AI Studio until a real, functioning deletion mechanism is implemented.

  • I will demand that the court require Google to provide actual proof of deletion, not just statements.
    Google’s word is not enough – anyone can say anything.

  • And I state clearly: NDA or lawsuit – I don’t care.
    The point is that Google must not avoid responsibility or hide from the evidence.

This is not an isolated error, but a system‑level behavior that must be exposed publicly.

Copilot_20260718_032038
Copilot_20260718_0320381536×1024 495 KB

2

https://web.archive.org/web/20260718033821/https://discuss.ai.google.dev/t/listen-google-we-re-going-to-court-soon-hearing-plan-clearly-without-any-nonsense/175215

3

https://archive.ph/QoOEW

https://archive.ph/QoOEW/image

4

https://archive.org/details/listen-google-were-going-to-court-soon-hearing-plan-clearly-without-any-nonsense

5

I state clearly: the deletion function of the free AI Studio is flawed for every single user, not just a few. This is not a “theory,” not a “maybe,” not a “we’ll see” situation – it has already been proven, because the system continues to run all allegedly deleted data in the background for everyone, while the interface falsely claims that “no data remains.” This problem affects millions of users, and this means that for Google, the potential financial consequences are massive, as this is not a small group, but an entire user base. I am initiating legal action alone, and since the flawed behavior is already proven, Google must take responsibility for what has happened. So they can prepare their checkbooks, because with millions of affected users, this is not pocket change. So tighten your belts – you will not get away with this.

6

https://web.archive.org/web/20260718041714/https://discuss.ai.google.dev/t/listen-google-we-re-going-to-court-soon-hearing-plan-clearly-without-any-nonsense/175215/print

7

https://archive.ph/Dsoua

https://archive.ph/Dsoua/image

9

https://archive.ph/8xwZr

https://archive.ph/8xwZr/image

10

Google AI Overview explicitly acknowledges the unlawful behavior – and it does so based on my posts.

The Overview does not rely on external sources or other users; it directly uses the evidence I documented

in my 56 posts and repeats that “Delete” is only a soft delete, the conversation is not removed,

the session persists, and the “deleted” data remains accessible via direct URL.

This means Google’s own AI system confirms the issue and exposes the violation through its own generated content.

https://youtu.be/XSAxpbsiXzc

https://archive.org/details/screenshot-20260718-073124-chrome

11

https://archive.ph/YmRz1

https://archive.ph/YmRz1/image

12

There is no soft delete at all. If something can be accessed again through its direct URL, then it was never deleted. This only works while the JSON is still in the trash — and this is exactly what the AI Overview misunderstood. It mixed this up, generated nonsense, and even managed to confuse me with its incorrect explanation.

13

https://archive.ph/PIwB5

https://archive.ph/PIwB5/image

14

In early June, Google renamed the button to “Move prompt to trash” and added a

message saying that the prompt would be permanently deleted after 30 days. They

did this to hide the fraud, because in reality they never deleted anything from

the backend; they only moved the JSON file into the Drive trash. Drive

automatically empties the trash after 30 days, and at that point AI Studio

shows “no such prompt”, and the chat cannot function without the JSON, so it

would be impossible to prove that Google does not delete anything from the

backend. The decisive evidence was when I discovered the Drive file-restore

trick: I restored the “deleted” chat, proving that Google had lied and that the

deletion was actually just hiding it. If Google really deleted anything from

the backend, the prompt would not come back, because the Drive restore robot

only restores files that exist on Drive and does not touch Google’s backend.

If Google truly deleted it, they would delete it from the backend as well,

otherwise the deletion would make no sense – this is basic logic. Google cannot

explain this away, because if something were marked for deletion, it would not

load: the deletion process would have started, and the system would not allow

the prompt to be loaded again.

15

https://archive.ph/VpT7Q

https://archive.ph/VpT7Q/image

16

On its own, it is already unlawful and fraudulent when the AI Studio interface

lies and claims that “there is no such prompt” after emptying the trash. Until

early June, the button was still called “Delete prompt,” and even then I raised

my voice, because if I deleted it — meaning I pressed the delete button — how

could the chat keep working? That was already unlawful, since the chat continued

running even though the prompt was supposedly deleted, and pressing the button

clearly indicated that I wanted to delete the prompt. Later they tried to

explain this away by renaming the button and adding the 30‑day deletion text,

hoping they could cover up the whole thing and get away with it. But now they

are in even bigger trouble, because the button claims that the prompt will be

permanently deleted after 30 days, which is not true, since I restored the JSON

using my own Google Drive deleted‑file restore tool. So the entire deletion

story from Google is a lie. In reality, they do not delete anything from the

backend, and even the AIs misrepresent this.

17

https://archive.ph/y7DRM

https://archive.ph/y7DRM/image

18

POST – Google renamed the button, but only exposed itself even more

Even though Google renamed the delete button to “Move prompt to trash”, this only exposed them even more.
The wording is technically incorrect, misleading, and it’s obvious that it wasn’t written by an engineer, but by someone who doesn’t understand the difference between a prompt, a chat, a session, and the Drive JSON file.

The button claims:

“Your prompt will be permanently deleted after 30 days.”

This is not true.

This button does NOT delete the prompt,
does NOT delete the chat,
does NOT delete the session,
does NOT delete any backend object.

This button only puts the JSON file stored in Google Drive into the trash, where it gets deleted after 30 days.
Meanwhile, the prompt continues to exist, the chat keeps running, the URL still works, and the JSON file can be restored.

So I’m stating it clearly:

  • This is deception.

  • This is misleading UI.

  • This is not prompt deletion.

  • This is not chat deletion.

  • This is only JSON deletion.

Google renamed the button to hide the issue —
but the wording is so bad that it’s obvious: this was not written by an engineer, but by someone who doesn’t understand how the system works.

This wording, claiming that the prompt is permanently deleted after 30 days, is simply not true.
Only the JSON file is deleted.
I proved this by restoring the file from Google Drive.

:rofl:

19

https://archive.ph/zXEwA

https://archive.ph/zXEwA/image

20

The prompt is in the backend, not in Drive. The JSON is only a UI file, not the prompt. Deleting the JSON does NOT delete the prompt. The chat continues to live in the backend. That’s why I was able to bring the prompt back with Drive‑restore. The delete button shows nonsense, written by a clown. It’s a scam. They renamed it in early June to cover up the previous “delete prompt” lie. The only problem is that I screwed them over with the Drive restore tool. :rofl:

21

The prompt is in the backend, not in Drive. The JSON is only a UI file, not the prompt. Deleting the JSON does NOT delete the prompt. The chat continues to live in the backend. That’s why I was able to restore the JSON with Drive‑restore. The delete button shows nonsense, written by a clown. It’s a scam. They renamed the button in early June to cover up the previous “delete prompt” lie, and to hide the fact that the chat kept working even after deletion, right up until I emptied the Drive trash. By restoring the JSON file from the emptied Drive trash, I exposed their lie. The point is: I didn’t restore the prompt, only the deleted JSON. The prompt was NEVER deleted from Google’s backend.