Implement a user-facing data deletion mechanism
SkillDev toolsRight-to-erasure is a skill for AI agents that checks whether an app provides users a full way to permanently delete their personal data. It is used when auditing account settings pages, privacy dashboards, or API routes to verify that a complete data deletion path exists for users.
Use Implement a user-facing data deletion mechanism in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Implement a user-facing data deletion mechanism and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Implement a user-facing data deletion mechanism skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
No other account needed.
Have an AI agent that can load skills.
What your AI can do with it
- Audits account settings pages for a data deletion path
- Audits privacy dashboards for a data deletion path
- Audits API routes for a data deletion path
- Verifies that a complete data deletion path exists for users
Getting started
- Have an AI agent that can load skills.
- Add the right-to-erasure skill to the agent.
- Point the agent at the account settings pages, privacy dashboards, or API routes to audit.
- Ask the agent to verify that a complete data deletion path exists for users.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/right-to-erasure/SKILL.md and read by ahel’s review.
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
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Oct 2026
Questions
- What does right-to-erasure check?
- It checks whether an app provides users a full way to permanently delete their personal data.
- When should it be used?
- Use it when auditing account settings pages, privacy dashboards, or API routes to verify that a complete data deletion path exists for users.
Advanced
- Item type
- skill
- Key
right-to-erasure- Source
- github.com/thedaviddias/front-end-checklist
github.com/thedaviddias/front-end-checklist