Legal Effect of Moderator Awareness on User Reports

The moderators on this forum are Google employees acting on behalf of the company. This is not an assumption but a verifiable fact: the official moderator list shows their names, roles and the “Google” affiliation next to them.

Because of this, when a moderator opens, views, flags or interacts with a post, it legally counts as the company becoming aware of the information. In law, it does not matter which channel the information arrives through. What matters is whether a representative of the organization has seen it. If they have, the organization is considered informed.

This means the following:

  • Google cannot claim they “did not know” about the facts described in the post

  • Google cannot claim they “did not receive” the information

  • Google cannot claim they “never saw” the report
    because the moderator’s activity is documented and time‑stamped.

The forum is not an official complaint channel, so Google has no obligation to respond here. However, the lack of obligation to reply does not change the fact that knowledge has been obtained. From the moment a moderator sees the content, the company is legally considered aware of it.

The moderator view, the moderator list, the timestamps and the archived snapshots together form a complete and verifiable evidence chain showing that Google has been informed of the issue.

All my posts can be found here:

I created this post because the issues I reported are not simple feedback or random comments. They involve concrete problems related to user data, privacy, system behavior and potential data‑handling failures. When a company becomes aware of a possible data‑related issue, they are not free to ignore it. Under GDPR and general legal standards, they are required to assess, investigate and, if necessary, respond. This obligation begins the moment the company becomes aware of the issue.

On this forum, the moderators are not anonymous volunteers. They are Google employees acting on behalf of the company, which is clearly shown on the official moderator list. When a moderator opens a post, reads it, flags it or interacts with it in any way, it legally means that Google has become aware of the content. Organizational knowledge works like this: if a representative sees it, the organization sees it. Because of this, the moment a moderator viewed my posts, Google became aware of the issues I reported.

I created this post to document this fact in a clear, traceable and verifiable way. The moderator view, the timestamps, the archived snapshots and the official moderator list together form a complete chain of evidence. This makes it impossible for the company to later claim that they “did not know,” “did not receive,” or “never saw” the information. They did. Their own moderator saw it.

This post is not about demanding a reply on the forum. It is about establishing that the company has already reached the point where a response is legally required. Once they are aware of a potential data‑handling issue, they have obligations under GDPR and their own internal compliance rules. Whether they choose to respond here or through another channel is their decision, but the responsibility to act already exists.

I am no longer writing about the original error itself — I am writing about the legal consequences of covering up that error. The company knew about it and did nothing. This is exactly what qualifies as a “cover‑up.” My post makes it clear that the company has a legal obligation to respond, because this is a data‑handling issue

All my posts can be viewed here:

This is no longer about the original error, but about the legal consequences of Google having verifiably received, acknowledged, internally registered — and later even removed from its own support dashboard — the case, yet still choosing to take no action, which elevates the situation from a simple technical failure to a documented act of willful neglect with clear GDPR implications.

The removal of an already‑existing, timestamped, internally registered case from the Google Support dashboard — while the corresponding legal correspondence, case ID, and delivery confirmation remain intact — constitutes not a technical glitch but an act of evidence suppression, indicating intentional destruction or concealment of records.

The company has violated the GDPR. They received my letter, they knew about it, they did not respond, they removed the ticket, they violated the obligation to respond, they violated the obligation of transparency, they violated the obligation of cooperation, they violated the deadline, they violated the obligation to preserve evidence. This constitutes grounds for compensation. According to Article 82 of the GDPR: ‘Every data subject who has suffered material or non‑material damage as a result of a violation of this Regulation shall have the right to receive compensation.’ My rights have been violated multiple times, and this is documented. The combination of prior knowledge, non‑action, DPO‑level GDPR violations, and externally timestamped evidence suppression creates a liability scenario that companies typically resolve through confidential settlement (NDA + compensation) to avoid precedent. If they fail to do so, it constitutes the continuation of the violation, the aggravation of liability, and the necessity of initiating regulatory or judicial proceedings, the consequences of which fall entirely on the company.

I sent this letter to the Google DPO :

"Subject: GDPR Violations – Formal Notice and Request for Immediate Action

Dear Data Protection Officer,

The company has violated the GDPR. They received my letter, they knew about it, they did not respond, they removed the ticket, they violated the obligation to respond, they violated the obligation of transparency, they violated the obligation of cooperation, they violated the deadline, they violated the obligation to preserve evidence.

This constitutes grounds for compensation. According to Article 82 of the GDPR:
“Every data subject who has suffered material or non‑material damage as a result of a violation of this Regulation shall have the right to receive compensation.”

My rights have been violated multiple times, and this is documented.

The combination of prior knowledge, non‑action, DPO‑level GDPR violations, and externally timestamped evidence suppression creates a liability scenario that companies typically resolve through confidential settlement (NDA + compensation) to avoid precedent.

If you fail to do so, it constitutes the continuation of the violation, the aggravation of liability, and the necessity of initiating regulatory or judicial proceedings, the consequences of which fall entirely on the company.

Please also review the following forum post, which documents moderator awareness and the timeline of the ticket disappearance:
https://discuss.ai.google.dev/t/legal-effect-of-moderator-awareness-on-user-reports/169375

I request your immediate written response."

Evidence‑grade images and Internet Archive backup:

The corrected images are available here without grid view, so they display properly on the Internet Archive

These screenshots show the raw server‑side results from Google’s own Gmail API Explorer. They clearly display how many messages I sent to the DPC’s addresses (info@dataprotection.ie, CBAssessment@dataprotection.ie) and how many messages I received from them. The same applies to the official reports I sent to Google: I sent hundreds of messages, and they did not respond to any of them. All of this data comes directly from Google’s backend logs — it cannot be altered, denied, or disputed.

My support case keeps disappearing from the Google Support Dashboard every few hours, and this has been happening since February. Google never responds. The dashboard shows data that does not reflect reality: the actual ticket vanishes, and only a six‑month‑old placeholder ticket remains visible. The repeated disappearance of the real ticket is not a bug but a data‑handling inconsistency. Under the GDPR, this raises concerns of data loss, record manipulation, and obstruction of the complaint‑handling process. The system does not preserve user submissions, is not transparent, and presents a misleading view to the user.