Public-interest and retention exceptions can justify refusal

What it is

Exceptions to the right to erasure permit specified necessary processing to remain even when a request otherwise appears applicable. GDPR exceptions include freedom of expression and information, legal obligation or public task, public health, safeguarded public-interest archiving or research and statistics, and the establishment, exercise, or defense of legal claims. An exception is bounded by purpose and necessity; saying “compliance” or “public interest” does not authorize retention of an entire account.

Why it happens

Erasure can conflict with other rights and social obligations. Universal removal could defeat evidence preservation, statutory accounting, or particular public research, while unlimited exceptions would hollow out the right. Necessity and proportionality connect the two: retained scope should be restricted to the data, use, and duration supporting the basis, with unrelated processing isolated. A request may therefore be partially fulfilled rather than wholly granted or denied.

Studying it

Process audits can sample refusals and partial approvals for consistency of basis, data class, necessity reasoning, duration, access restriction, and review. Scenario studies can test whether refusal notices let requesters understand what remains, why, and what action is available. Inter-reviewer agreement can reveal ambiguous policy, but legal judgment should not be reduced to classifier accuracy; boundary cases require qualified review.

Where it stops holding

These categories describe the GDPR framework and are not universal across jurisdictions. Public interest is not synonymous with corporate interest, and hypothetical litigation does not justify indefinite preservation. Research exceptions ordinarily require safeguards and a showing that erasure would make the objective impossible or seriously impair it; possible future research is insufficient. Lawful retention still does not authorize unrelated display, marketing, or recommendation.

Applying it

• Record basis, necessary data, permitted purpose, readers, end condition, and reviewer for every exception.
• Support partial erasure: clear unrelated copies and move retained records into a purpose-isolated access domain.
• Give a specific refusal notice naming retained classes, reason, duration or review condition, and available objection or regulatory channel.
• Sample retained records for reads outside the permitted task and automatically return them to deletion when the hold or public task ends.

Related

• Same group: O1.07.1 Deletion must cover backups and derived data · O1.07.2 Deletion scope and timing must be stated · O1.07.3 Disappearance from the interface is not backend deletion · O1.07.4 Erasure is an assertable legal right, not an optional feature · O1.07.5 Deletion requests must propagate to downstream recipients · O1.07.7 Completion needs verifiable evidence, not a verbal promise
• Adjacent: O1.02 Data minimization · O1.03 Purpose limitation
• Search terms: erasure exceptions · legal hold · public interest processing