Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when auditing account settings pages, privacy dashboards, or API routes to verify that a complete data deletion path exists for users.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-19 | ✗→✓ | ▲ Improved | -4% | 0% |
| case-02 | ✓→✓ | ＝ Same ✓ | -9% | 0% |
| case-20 | ✓→✓ | ＝ Same ✓ | 28% | 0% |
| case-21 | ✓→✓ | ＝ Same ✓ | 33% | 0% |
| case-22 | ✓→✓ | ＝ Same ✓ | 38% | 0% |
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.
Check whether this application provides a user-facing data deletion mechanism that clears all client-side storage and triggers a server-side deletion request.
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 GDPR Article 17 (right to erasure) and what a compliant data deletion flow must cover, including both client-side and server-side data.
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
Other measured skills in the registry, with their headline benchmark lift.