The case is moving forward.
NOYB (Max Schrems’ data‑protection organization) has already reached out to me from their official legal requests address.
This means Google should start sweating, because they’ve seen the evidence and they’re looking into it.
And regardless of how this develops, I’m launching the lawsuit anyway — the evidence is 100% solid and fully reproducible in AI Studio.
I uploaded the correspondence to the Internet Archive:
The official admission from Google: Lalit_Kumar states clearly that the files saved by Google AI Studio are stored in Drive without any file extension and are marked with “special metadata”. He also explains that if the user downloads the file and later manually copies the same extensionless JSON back into Drive, the special metadata is lost, Drive creates a completely new file with a new file ID, and AI Studio can no longer recognize the chat. This is documented here: Saved prompt history extension? The archive.ph backup is here: https://archive.ph/ghAaS
The Drive Restoration Paradox: When I delete the prompt and empty the trash, Google claims that the data has been permanently destroyed. However, when I trigger the Drive restore robot, the chat comes back fully intact and can be continued flawlessly inside AI Studio. The only reason this works is because the robot does not create a new file: it restores the original file with the original file ID and the original metadata.
The proof of the deception: If manually copying the extensionless JSON back into Drive causes Drive to generate a new file with a new ID and without the special metadata (making it unusable for AI Studio), then how is the Drive robot able to bring the chat back “alive”? The only possible technical explanation is that Google’s backend never deleted the special metadata or the backend session connection. The backend session remained intact the whole time, and the robot simply restores the original file ID that still points to the still‑existing backend chat.
0https://archive.org/details/kepernyokep-2026-07-22-0523281
The archive.ph snapshot does not only preserve the forum post — it also keeps the original Google CDN image URLs. These links appear in the browser (bottom‑left corner) when hovering over the images, and they open normally, which proves that the images are authentic and come directly from Google’s servers. I did not upload or modify them afterwards; the archive snapshot itself proves that they are real, server‑side content. I also uploaded the images to the Internet Archive for independent preservation. Here is the link: https://archive.org/details/kepernyokep-2026-07-22-060711
The Drive‑restore robot only restores the Drive file within 25 days. The chat starts working again after I bring back the JSON file from the emptied trash with the help of the Drive‑robot, because the Google backend actually didn’t delete anything: the session, the metadata and the pointer remained intact the whole time. The Drive‑robot can only operate inside Drive, it cannot influence the server‑side. This is why my evidence is irrefutable.
You can read about the Drive file restoration process here: https://knowledge.workspace.google.com/admin/drive/recover-deleted-files-and-folders-for-drive-users
The images I uploaded in Comment #18 of this topic are also saved separately and can be found on the Wayback Machine at the following links:
Here I uploaded the same images that appear on the original page, where the browser shows their links in the bottom‑left corner — and those links point to the CDN.
