https://archive.ph/qIl2L/image
If anyone wants to read it, please check it on the Internet Archive or archive.ph, because it is being censored here unlawfully.
The moderators deleted my post: https://discuss.ai.google.dev/t/the-google-cannot-deny-it-deletion-by-an-admin-legally-constitutes-knowledge/175460 , yet Google’s AI Overview still surfaced it — which means Google continues to retain and process content that has already been removed. After an admin deletion, the company has no legal basis to store, index, or reuse the material. The deletion itself proves the company received and reviewed the communication, so any further retention or use happens without lawful grounds.
https://archive.ph/VSeyJ/image
Since I can prove that my post was deleted 3–4 hours earlier, and I can also prove that afterwards Google’s AI Overview still found it cached, Google ends up in a very bad legal position, because the system logs and the Wayback snapshot together demonstrate that they stored and processed deleted data without any lawful basis.
The post was deleted, yet the snippet is still there — a stored fragment of my post in the Google index that AI Overview uses. As shown in the screenshots ‘Képernyőkép 2026‑07‑20 155225’ and ‘Képernyőkép 2026‑07‑20 155249’, this proves that Google continues to possess and process the deleted data
The platform continues to store the images that were deleted from the post, and they 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 doesn’t capture. The only reason those “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 user deletes the post. Because the images are still present on the CDN, systems like Google Lens 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:
If you don’t like the topic, feel free to leave. Nobody forced you to come here.
Do not write to me again, and stay out of my thread. You’re not a moderator, you’re not an admin, and you have nothing to do with me. I didn’t ask for your opinion, and I don’t need your commentary. If my posts bother you, that’s your problem — not mine. Move on and stop replying to me.
I don’t go into your threads to tell you what to write, so don’t come into mine. If my posts bother you, that’s your problem — not mine. Stop replying to me and stay out of my thread.