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.
Bitu79•54m ago
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:
https://discuss.ai.google.dev/t/they-deleted-my-post-so-i-m-...
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:
https://discuss.ai.google.dev/t/they-deleted-my-post-so-i-m-...
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.
The proof‑of‑evidence video is available here:
https://archive.org/details/unknown_2026.07.20-17.19
These are the deleted posts:
https://archive.ph/qIl2L
https://archive.ph/qIl2L/image
https://web.archive.org/web/20260720054146/https://discuss.a...
https://web.archive.org/web/20260720055537/https://discuss.a...