Under the DPDP Act 2023, individuals can request erasure of their personal data, and you must also delete data once its purpose is served. True deletion is hard because personal data spreads across databases, caches, search indexes, analytics and backups. This checker rates whether your systems can actually honour erasure end-to-end and flags where data would be left behind.
Find out whether your systems can really delete a person's data everywhere it lives.
Deleting a row in the primary database is the easy part. The same personal data often persists in read replicas, caches, search indexes, event logs, analytics warehouses and backups. Honouring a DPDP erasure request means reaching all of them — or having a defensible approach where you cannot (such as backup expiry cycles).
Engineering teams that map these data paths and design deletion in advance can honour requests reliably; those that do not discover the gaps during an actual request.
A data-path map, deletion patterns (incl backups and analytics), and an erasure-request runbook.
One real DPDP development explained in plain English, one practical how-to, one number from our own assessment data. Nothing else — no daily noise, no sales pitch.
No spam. Unsubscribe with one click, anytime.
