Request and Misinterpretation by Newsquest - The Argus
All Media Reports > the argus
Newsquest / The Argus – No SAR Submitted by Me, No Erasure Requested, and Misinterpretation by Both the Privacy and Legal Teams date: 02/06/2026
For the avoidance of doubt, I, Riccardo Gresta, have never submitted a Subject Access Request to Newsquest or The Argus, nor have I ever made a request for erasure under Article 17 UK GDPR. The communication I sent on 30 March 2026 was a collaborative proposal, intended solely to offer a pragmatic resolution following the withdrawal of the original East Sussex County Council press release. In that communication, I explained that the ESCC publication was a pre‑sentencing prosecution summary, not a court record; that the originating authority had already removed it; that several platforms had de‑indexed or deleted their copies; and that the matter had cross‑border implications due to ongoing legal proceedings in Italy. The communication was not framed, presented, or intended as a SAR or as a deletion request, and it did not invoke any rights under Articles 12–23 UK GDPR.
Despite this, both the Newsquest Privacy Team (1 April 2026) and the Newsquest Legal Team (2 April 2026) treated my proposal as if it were a formal erasure request, issuing detailed refusals based on journalistic exemptions, open‑justice principles, and internal archive policy. These responses addressed a request that I never made, and therefore reflect a complete misinterpretation of my correspondence. Their replies cannot be characterised as responses to a SAR, because no SAR was ever submitted by me, and they cannot be characterised as refusals of an erasure request, because I never requested erasure. The misclassification was total: both teams responded as if they had received a deletion request, even though my communication was clearly framed as a non‑GDPR collaborative proposal.
In my subsequent rebuttal, I clarified that:
- my communication was not a SAR and not an erasure request;
- the original ESCC source had been withdrawn, materially altering any public‑interest assessment;
- the article published by The Argus is a derivative reproduction of that withdrawn source, not a contemporaneous or independently verified court report;
- Newsquest conducted no legitimate‑interest balancing test, no proportionality assessment, no accuracy review, and no consideration of less intrusive measures, all required under Articles 5, 6, 17, 18 and 21 UK GDPR;
- the journalistic exemption cannot be invoked to refuse a request that was never made.
This systemic misclassification is further demonstrated by Newsquest’s handling of the SAR submitted by (Former Carer). That SAR 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 failure in their internal processes for recognising and handling data‑subject rights.
As Newsquest/The Argus responded only to a communication that was neither a SAR nor a deletion request, and misclassified even a genuine SAR submitted by (Former Carer), their replies are procedurally misplaced and do not constitute engagement with any data‑protection right exercised by me.
Systemic Failures Across Multiple Controllers – Misclassification and Non‑Response (Consolidated Master Paragraph with Integrated Page Titles)
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.
