Retention & erasure: Data retention and erasure, rule by rule, with proof
Decide how long each kind of data is kept, let sector laws hold what they must, and erase the rest on time, at you and at your processors.

What it does
Sets retention per purpose and data category, warns before erasure, and erases in your systems and at processors with evidence.
Who it's for
Privacy teams and system owners who must stop keeping data once its purpose is served.
The law it covers
Erase personal data when consent is withdrawn or the purpose is no longer served, unless a law requires keeping it, and keep processing logs for at least a year.
- s.8(7)
- R.6(1)(e)
- R.8
- Third Schedule
Rules per purpose
- Retention for each purpose and data category
- Sector laws that require longer kept on top
- Processing logs kept at least one year
- Rules from your sector pack to start with
An illustration of rules per purpose in Retention & erasure.
Erasure on time
- Erasure when consent is withdrawn or the purpose ends
- A warning to the person before inactivity erasure
- Erasure at processors as well as at you
- Kept data explained when a law requires it
An illustration of erasure on time in Retention & erasure.
Proof of every erasure
- What was erased, where, when and by whom
- Each step written to the evidence trail
- Records you can show the Board
- Your own full export when you leave the platform
An illustration of proof of every erasure in Retention & erasure.
Works with
Related modules
See Retention & erasure at work
We show you the module with sample data and talk through how your team would use it.