Implementation deadlineCore obligations enforceable — 13 May 2027

Time left—

Protect · Retention & Erasure

Delete what you should. Keep what you must. Say which.

Set how long you keep each kind of data, and the law that requires it. When the time comes, every record is either deleted or kept, and if it's kept, you record which law requires it and until when.

What it does

Retention & Erasure in practice

Every rule has a reason

Each rule names the data, the time period and the law behind it. If a tax rule and a banking rule both apply, the longer one wins, and you can see why.

s.8(7): erase once the purpose is served

Deleted or kept, nothing in between

Each record is either deleted or kept. 'Pending' and 'partly deleted' are not allowed. A record kept without an end date isn't accepted either.

Legal hold

A court case or investigation can pause deletion for specific records. Someone is named as responsible, a reason is given, and the pause is lifted the same way.

Also included

The details that matter

  • Every deletion run is dated and kept as proof.
  • Deleting from the vault destroys the key, so backups can't be read either.
  • Copies sent to suppliers are followed up, not assumed gone.

Questions

About Retention & Erasure

All questions
What if the DPDP Act says delete and another law says keep?

Both apply. You keep what the other law requires, for as long as it requires, and use it only for that. The record shows which law and until when.

Does erasure cover backups?

With the Privacy Vault, yes. Each person's data is locked with its own key. Deleting it destroys the key, so old backups can't be read. Systems outside the vault are tracked and tested separately.

See Retention & Erasure on your own systems

A 45-minute working session. Bring a notice or consent form you use today and we will check it with you.