I can prove that my posts were deleted 3–4 hours earlier, and I can also prove that afterwards Google’s AI Overview still found them cached. This puts Google in a very bad legal position, because the system logs and the Wayback snapshot together show that they stored and processed deleted data without any lawful basis. In this post you can find the full demonstration of this fact:
The posts were deleted, yet the snippet was still there — a stored fragment of my post in the Google index that AI Overview uses. The screenshots ‘Képernyőkép 2026‑07‑20 155225’ and ‘Képernyőkép 2026‑07‑20 155249’ clearly prove that Google continues to possess and process the deleted data.
Here are the images:
The platform also continues to store the images that were deleted from the post, and these files remain physically present on Cloudfront. The deletion only hides the images in the user interface; it does not remove the actual files from the CDN. Because the image files are still stored on Cloudfront, Google Lens can find and recognize them without any issue. This proves that the platform keeps the deleted images on its servers, unchanged and accessible, which constitutes unlawful data retention.
Archive.ph does not save the Cloudfront‑hosted images, because Cloudfront is a separate CDN layer that the archiver does not capture. The only reason these “deleted” images still open is that the platform never removed them from its own servers. The files remain physically stored on Cloudfront, unchanged and accessible, even after the post is deleted. Because the images are still present on the CDN, Google Lens and other systems can find and analyze them without any issue. This proves that the platform’s deletion is only a UI‑level hide, not an actual removal, and that the service is unlawfully retaining deleted images on its Cloudfront infrastructure.
Google AI Studio doesn’t delete chats from the backend (JSON trick). Google Developers Forum doesn’t delete posts from the backend (AI Overview snippet trick). Google Cloudfront doesn’t delete the physical media files, so Google Lens can still read the “deleted” images.
The system pretends it actually deleted the post, while every part of the content continues to exist in the background: the post itself, the attached image, the metadata, the snapshot, and even the Cloudfront link remain accessible, moderators can still see it, so the “removed” label is misleading, incorrect, and not transparent, because in reality no deletion happened, only simple hiding. This is fraud!!! It’s the same mechanism as the AI Studio “backend deletion” lie. The user thinks their post was deleted, while the system continues to retain the associated data. This is not a technical error, not an accident, and not a Discourse characteristic. This is the same pattern we already saw in AI Studio! The user relaxes because they believe their content was deleted, while the system still keeps all the related data. On my posts the system message says: “Hello,
This is an automated message from Google AI Developers Forum to let you know that your post was removed.
Your post was flagged as inappropriate: the community feels it is offensive, abusive, to be hateful conduct or a violation of our community guidelines.
This post was flagged by the community and a staff member opted to remove it.”
If Google Lens can find the title of my deleted post and the image attached to it —“The Google cannot deny it: deletion by an admin legally constitutes knowledge” —then my post is still stored in Google’s cache, even if the Discourse interface pretends it was deleted.This means Google does not actually remove the data, but continues to store my deleted posts illegally on its servers.
This page is the cached version stored by Google. Google Lens displayed the title of my deleted topic only because Google still retained the full metadata in its cache. This behavior constitutes unlawful data processing, because despite the user’s explicit intention to delete the content, Google continues to keep the deleted data, associate it with the image, process it, index it, and return it in search results.
