Most People Don’t Even Understand the Problem — and That’s Exactly Why Google Gets Away With Everything

Here are all my posts together — this is why I wrote this one.

https://discuss.ai.google.dev/u/bitu79/activity/topics

I’m not here to complain. I’m here to show what actually happens when Google ignores the law.

I’ve documented everything — deleted data still being processed, DSAR requests ignored, and official replies that say nothing.
I’ve posted publicly on Google’s own AI forum.
I’ve shared full email chains with Google’s Data Protection Office.
I’ve contacted the Data Protection Commission (DPC).
And still, nothing changes.

The problem isn’t just Google.
It’s the system that protects them.
It’s the regulators who do nothing.
It’s the public that doesn’t even understand what’s wrong.

Most people don’t know what GDPR or DSAR even mean.
They don’t understand why it’s illegal for Google to keep using deleted data.
They don’t understand why ignoring a DSAR is a violation.
They don’t understand why silence from the DPC is unacceptable.
And because they don’t understand, they don’t care.

That’s how Google gets away with it — behind policy, behind bureaucracy, behind ignorance.

I’ve written thousands of emails to Google and to the authorities.
I’ve shown proof, screenshots, archives, forum posts.
Everything is public.
Everything is documented.
And still, they pretend nothing exists.

This isn’t frustration — it’s evidence.
And if you read this and still don’t get it, that’s exactly the problem.

These two emails are only the last two — I’ve written thousands to Google and to the authorities, including the DPC.

https://web.archive.org/web/20260629101108/https://discuss.ai.google.dev/t/most-people-don-t-even-understand-the-problem-and-that-s-exactly-why-google-gets-away-with-everything/173014

And if anyone doubts what I’m saying, they can simply put any of my post links into Google’s AI mode and see it themselves.

The AI rewrites my posts as if Google were actually doing something — as if Google were responding, investigating, or taking action.
It creates a fake narrative where Google looks responsible, even though Google has ignored every DSAR, every email, every complaint, and every piece of evidence I’ve submitted.

Just take any of my post links, drop it into AI mode, and watch how it turns my documentation into a PR‑friendly summary that pretends Google is compliant.

That’s the real insanity here.

https://archive.org/details/fire-shot-capture-387-most-people-dont-even-understand-the-problem-and-thats-exa

https://archive.ph/jMk7w

https://archive.ph/jMk7w/image

The DPC instructed me to send my complaint to info@dataprotection.ie. I followed their instructions, and even then I received no response at all.

None of the emails I sent to info@dataprotection.ie have ever received a response.

https://web.archive.org/web/20260629111135/https://discuss.ai.google.dev/t/most-people-don-t-even-understand-the-problem-and-that-s-exactly-why-google-gets-away-with-everything/173014

I sent registered, return‑receipt letters to Google, and Google received them. The return receipts came back after about two months, signed by Google, and the dates clearly show that the letters were delivered long ago. I also have the official confirmation from the Hungarian Post, proving that the letters were delivered to the United States and accepted there. Not only does the DPO fail to respond — Google’s headquarters also does not reply to anything. Meanwhile, Google pretends to be a responsible, law‑abiding company to the outside world, which is nauseating. This is unlawful.

https://web.archive.org/web/20260629113658/https://discuss.ai.google.dev/t/most-people-don-t-even-understand-the-problem-and-that-s-exactly-why-google-gets-away-with-everything/173014/8

https://archive.org/details/fire-shot-capture-392-most-people-dont-even-understand-the-problem-and-thats-exa

Here is the full situation in plain language.

I wrote emails to Google about a data issue. They didn’t respond.
But what makes this far worse is that Google’s own AI mode publicly read, analyzed, summarized, and displayed my post.
This is not a private interaction anymore.
This is public.
People can see it in the AI mode.
And Google still stays silent.

Google’s AI didn’t just “answer a question.”
It processed my content.
It broke it into subtopics.
It searched the internet for related information.
It summarized it.
It displayed it publicly.

This is not a misunderstanding.
This is not a technical glitch.
This is not “the AI made a mistake.”

This is data processing by Google Search.

And legally, that means one thing:

This is knowledge acquisition by the company.

Here is the legal definition of knowledge acquisition:

“Knowledge acquisition occurs when the data controller actually accesses information, processes it, and the information is available to them.”

Three elements:

  1. Access

  2. Processing

  3. Availability

Google’s own documentation about AI mode confirms all three:

“AI mode breaks questions into subtopics and searches multiple data sources at once.”
“AI mode relies on Google Search’s deep understanding of information on the internet.”

This means:

Access – Google’s system read my post.
Processing – Google’s system analyzed and summarized it.
Availability – Google’s system stored and displayed it.

This is exactly the legal definition of knowledge acquisition.
There is no way to explain this away.

And because the AI mode is public, this is not just internal knowledge acquisition.
This is public knowledge acquisition.

Legally, this is the most serious category.

Under GDPR:

GDPR Article 12 – duty to inform after knowledge acquisition
https://eur-lex.europa.eu/eli/reg/2016/679/oj#d1e2704-1-1

GDPR Article 15 – duty to respond and provide access
https://eur-lex.europa.eu/eli/reg/2016/679/oj#d1e2854-1-1

GDPR Article 24 – responsibility of the data controller
https://eur-lex.europa.eu/eli/reg/2016/679/oj#d1e3184-1-1

These are the official EU legal texts.

They say:

  • If a company acquires knowledge of a data-related request, it must respond.

  • If it does not respond, it commits a violation.

  • If the content is public, the company cannot claim “we didn’t know about it.”

Google cannot say:

“We didn’t receive it.”
“We didn’t see it.”
“We didn’t know about it.”
“There was no request.”

Because their own AI publicly processed it.

This situation should not be possible under the law.
But it is happening.
That’s why it feels impossible to understand.
Not because I misunderstand anything, but because the system itself is contradictory.

This is the core problem:

Google’s AI publicly acknowledges the content.
Google as a company officially ignores it.

Legally, this is knowledge acquisition + failure to respond = violation.

That’s the entire point.

https://archive.org/details/https-discuss.ai.google.dev-t-most-people-don-t-even-understand-the-problem-and-

https://web.archive.org/web/20260629131851/https://discuss.ai.google.dev/t/most-people-don-t-even-understand-the-problem-and-that-s-exactly-why-google-gets-away-with-everything/173014

https://kephost.net/p/MjQ2MzM4Mw.png

According to the GDPR, “awareness” (tudomásszerzés) happens when the data controller:

accesses → processes → and makes the information available.

AI does exactly this:

  • it accesses the text

  • it processes the text

  • it generates a new text

  • it shows it to me,

  • shows it to others,

  • and shows it to Google itself, because the system was created and operated by Google.

Therefore:

  • The AI’s output is itself proof of processing.

  • LLMs generate text — that’s how they work.

  • Processing = awareness under the GDPR.

  • Awareness = a legal fact.

This means:

AI‑generated answers legally count as the company’s own official statements, and the company is responsible for them.

The Munich I Regional Court (May 28, 2026, 26 O 869/26) explicitly ruled that:

The party who ACTIVATES the AI is responsible for its output.

Google activates and operates the AI Overview →
Google is responsible for the output.

https://kpw.law/en/google-is-liable-for-ai-results/

https://web.archive.org/web/20260629145541/https://discuss.ai.google.dev/t/most-people-don-t-even-understand-the-problem-and-that-s-exactly-why-google-gets-away-with-everything/173014

Google’s AI Overview used my post from the Google AI Developers Forum as a source and generated new text from it in multiple answers.
My post appears in every screenshot — the AI didn’t just link it, it actually created new content based on what I wrote.

This means the model is acting as a content producer, not a neutral summarizer.
And according to the Munich I Regional Court (May 28, 2026, 26 O 869/26), when the AI generates content, Google is legally responsible for it, because they are the ones who activate and operate the system.

So when the AI Overview rewrites my post and publishes it inside Google Search,
that output legally counts as Google’s own content — and they are accountable for it.

https://web.archive.org/web/20260629153706/https://discuss.ai.google.dev/t/most-people-don-t-even-understand-the-problem-and-that-s-exactly-why-google-gets-away-with-everything/173014/14

https://archive.org/details/fire-shot-capture-398-most-people-dont-even-understand-the-problem-and-thats-exa

I saved Google’s own AI Overview activity as HTML files — not just screenshots.
This means I have exact, verifiable copies of how Google’s AI system used my post, generated new text from it, and published it inside Google Search.

The AI Overview didn’t just reference my content.
It rewrote it, summarized it, and presented it as Google’s own AI output in multiple answers.
And now I have the full HTML evidence of Google’s system doing this.

Under the Munich I Regional Court ruling (May 28, 2026, 26 O 869/26), when the AI generates content, Google is legally responsible, because they activate and operate the system.

So with these HTML files, Google is not only caught —
they’re caught by their own system, in their own format, doing their own processing.

This is direct, technical proof of:

  • content generation

  • data processing

  • publication

  • and Google’s legal responsibility for the output

All captured and preserved exactly as Google produced it.

https://archive.org/details/google-sajat-tevekenysegek-2026.-06.-29.-17-57-24

https://web.archive.org/web/20260629160354/https://discuss.ai.google.dev/t/most-people-don-t-even-understand-the-problem-and-that-s-exactly-why-google-gets-away-with-everything/173014/16

https://archive.ph/IvU48

https://archive.ph/IvU48/image

I’ve saved the full forum data archive — user_archive‑Bitu79‑260629‑162628‑2796.zip — exported directly from Google’s AI Developers Forum. This ZIP contains the official CSV record of my posts and interactions, generated by Google’s own system. That means it’s not just a screenshot — it’s verifiable legal evidence showing that Google’s automated systems processed and stored my content. Together with the HTML snapshots and AI Overview outputs, this archive proves that Google’s AI actively handled my data and generated new text from it.

https://archive.org/details/user_archive-Bitu79-260629-162628-2796

https://web.archive.org/web/20260629163317/https://discuss.ai.google.dev/t/most-people-don-t-even-understand-the-problem-and-that-s-exactly-why-google-gets-away-with-everything/173014/19

https://archive.org/details/fire-shot-capture-399-most-people-dont-even-understand-the-problem-and-thats-exa