• the original version published on 26 December 2022, and
• the current version served in 2026.

• modified, corrected, contextualised, or restricted the article
• applied any form of de‑indexing or visibility reduction
• updated the content or merely re‑served the 2022 version through a new CMS
• continued to process judicial and health data unlawfully

• identical metadata
• identical descriptions
• identical health and judicial data
• identical publication dates
• identical JSON‑LD
• identical narrative structure
• identical factual inaccuracies

• a CMS migration
• absence of editorial oversight
• absence of content review
• absence of corrective action

• og:url now incorrectly points to /news/article

• @type: NewsArticle
• headline identical
• keywords identical
• datePublished = 2022
• dateModified = 2022
• description includes health data
• articleBody empty (ITV CMS behaviour)

• same paragraphs
• same errors
• same fabricated hospital confirmation
• same health data
• same inverted chronology
• same ESCC narrative

• special category health data (Art. 9 UK GDPR)
• criminal offence data (Art. 10 UK GDPR)
• non‑notified judicial data (ROA 1978)
• inaccurate data (Art. 5(1)(d) UK GDPR)

• ESCC removing the primary source
• PressReader removing the article
• Internet Archive excluding all snapshots
• Google de‑indexing the URLs
• What’s On in Brighton removing the article

• full indexability
• full visibility
• unchanged metadata
• unchanged publication dates
• unchanged health and judicial data
• unchanged narrative

• the article has not been updated
• the article has not been corrected
• the article has not been contextualised
• the article has not been de‑indexed
• the article continues to process unlawful health and judicial data
• the article continues to disseminate inaccurate information
• the article continues to replicate the ESCC press release

• persistent unlawful processing
• absence of rectification
• continued GDPR violations
• continued ROA 1978 violations
• ongoing reputational harm

---

⭐ Universal Consolidation Paragraph (British English Version)

FORENSIC–LEGAL Consolidation Note — Cross‑Outlet Pattern of Derivation  
The comparative assessments contained in this section demonstrate a consistent, recurring, and technically recognisable pattern across all five media outlets examined (The Argus, ITV Meridian, SussexWorld, What’s On In Brighton, and BourneFree Live). Each article reproduces the same structural elements, the same grammatical error (“Ombudsmen”), the same chronological impossibility (the alleged post‑interview LGO complaint), the same fabricated claim (“hospital confirmation”), the same omissions (including the removal of the only exculpatory statement contained in the Prosecution Case Summary), and the same political and moralising statements originating from the ESCC press release. None of the outlets introduces independent verification, external sources, or consultation of judicial, medical, or administrative records.

Taken together, these elements constitute a forensic pattern of churnalism: the uncritical reproduction of a manipulated institutional narrative, lacking factual verification, editorial independence, or evidential scrutiny. The repeated presence of identical errors, fabrications, omissions, and narrative structure provides a clear analytical basis for distinguishing independent journalism from derivative, unverified content. This consolidation note therefore serves as the interpretative key for all comparative analyses presented in this section.

Across the different components of my archive — The ITV Case and Google’s Technical Response, The Argus Case and Google’s Technical Response, ITV – Digital Evidence Analysis, and Sussex Express – Digital Evidence Analysis — a consistent forensic pattern becomes evident. In each case, legacy articles containing inaccurate judicial and health data were initially removed by Google under GDPR, only to resurface later through newly generated or technically regenerated URLs. Google’s behaviour was identical in both the ITV and The Argus cases: the reappearing URLs were not treated as remnants of incomplete propagation, but as newly surfaced entries, requiring immediate removal. This confirms that the resurfacing was triggered not by Google reversing its decision, but by publisher‑side technical actions, such as CMS migrations, topic‑hub rebuilds, canonical inconsistencies and metadata replication. My ITV – Digital Evidence Analysis and Sussex Express – Digital Evidence Analysis both demonstrate that the underlying articles remain unchanged, uncorrected and structurally intact, while the surrounding technical frameworks continue to emit fresh indexation signals. Taken together, these cases show that the persistence of harm arises from publishers repeatedly re‑exposing the same unlawful and inaccurate content through evolving infrastructures, thereby necessitating renewed GDPR enforcement each time.

A broader systemic issue emerges when examining the conduct of all controllers involved, as evidenced across the full set of analytical pages on this website — including ITV article analysis, ITV source code analysis, Comparative Analysis: ITV vs ESCC Newsroom, ITV – Digital Evidence Analysis, SussexWorld article analysis, SussexWorld source code analysis, Comparative Analysis: Sussex Express/SussexWorld vs ESCC Newsroom, Sussex Express – Digital Evidence Analysis, The Argus article analysis, The Argus source code analysis, Comparative Analysis: The Argus vs ESCC Newsroom, Request and Misinterpretation by Newsquest – The (WOIB) Brighton source code analysis, Comparative Analysis: WOIB vs ESCC Newsroom, WOIB authorship article, Bourne article analysis, Bourne source code analysis, Comparative Analysis: BFL vs ESCC Newsroom, and BFL authorship article.

Across all these pages, a consistent pattern emerges. Both ITV and Newsquest/The Argus misclassified my communication of 30 March 2026. I, Riccardo Gresta, did not submit a Subject Access Request and did not request erasure. My communication was a collaborative proposal, intended solely to offer a pragmatic resolution following the withdrawal of the original East Sussex County Council press release. Despite this, both ITV and Newsquest independently treated my proposal as a request for deletion, issuing formal refusals under Article 17 UK GDPR to a request that I never made. This demonstrates a shared failure to correctly identify and route non‑GDPR correspondence.

This pattern is further confirmed by Newsquest’s handling of the SAR submitted by (Former Carer), which was a standard access request under Article 15, yet Newsquest again treated it as a request for erasure, applying journalistic exemptions and refusing deletion — even though no deletion had been requested. The fact that Newsquest misclassified both a collaborative proposal (mine) and a formal SAR (submitted by (Former Carer)) in the same manner indicates a structural problem in their internal processes for recognising and handling data‑subject rights.

In parallel, several other publishers — including Sussex Express (National World), BourneFree Live, and What’s On In Brighton (WOIB) — have not responded at all either to my collaborative proposal or to the SAR submitted by (Former Carer). This includes WOIB, which removed the article from its website but nevertheless failed to issue any SAR response, provide any Article 15 information, or communicate any lawful basis for its processing. Removal of the article does not extinguish the obligation to respond to a SAR, nor does it satisfy the transparency requirements under Articles 12 and 15 UK GDPR.

Taken together, these behaviours — misclassification by ITV and Newsquest, the identical misclassification of a formal SAR submitted by (Former Carer), and total non‑response by the remaining controllers — demonstrate a systemic failure across multiple publishers to correctly identify, classify, and process data‑protection‑related correspondence. This pattern is consistently reflected across all analytical sections of this website, from article‑level textual analysis to source‑code forensics, comparative assessments, and digital‑evidence evaluations. It raises concerns regarding the adequacy of controllers’ internal procedures, their ability to distinguish between collaborative proposals and statutory rights requests, and their compliance with the transparency and accountability principles under Articles 5(1)(a) and 5(2) UK GDPR.