OpenParable
Skip to content
← Back to skills

Right To Erasure

DevOps & Security
right-to-erasure

Right To Erasure is an Agent Skill for devops & security published in the thedaviddias/Front-End-Checklist repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when auditing account settings pages, privacy dashboards, or API routes to verify that a complete data deletion path exists for users.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/thedaviddias/Front-End-Checklist/blob/HEAD/skills/right-to-erasure/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/right-to-erasure, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Implement a user-facing data deletion mechanism

GDPR Article 17 gives EU residents the right to have their personal data erased when it is no longer necessary for the purpose it was collected, or when they withdraw consent. Failing to honour this right can result in regulatory fines of up to €20 million or 4% of global annual turnover. Providing a clear deletion flow also builds trust with users who value control over their data.

Quick Reference

  • Provide a visible "Delete my account / data" option in account settings
  • Clear all client-side storage: localStorage, sessionStorage, IndexedDB, and cookies
  • Send a deletion request to the server and confirm receipt to the user
  • Complete deletion within 30 days as required by GDPR Article 17

Check

Check whether this application provides a user-facing data deletion mechanism that clears all client-side storage and triggers a server-side deletion request.

Fix

Implement a data deletion flow that clears localStorage, sessionStorage, IndexedDB, and cookies, then sends a deletion request to the server and shows confirmation to the user.

Explain

Explain GDPR Article 17 (right to erasure) and what a compliant data deletion flow must cover, including both client-side and server-side data.

Code Review

Review account settings, privacy pages, and API routes for a data deletion endpoint. Flag missing client-side storage clearance, absent confirmation UI, or missing server-side deletion calls.

For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/en/rules/privacy/right-to-erasure