Skip to content

A customer asks for erasure, how do I handle that technically?

The right to erasure is not a single button. You need to know where the data sit, what you may actually delete, and what you must keep under other laws.

Try this first

  1. 1Map where the data live: CRM, accounting, mail archive, backups, support tickets, newsletter tool, analytics. A map per record helps.
  2. 2Check retention obligations. Invoices fall under tax law, complaints often have a limitation period. You may keep what you genuinely need, but document why.
  3. 3Decide per system: hard delete where possible, otherwise structured anonymisation or move to a sealed retention zone.
  4. 4Backups do not get wiped immediately. Document that the data are gone from the primary system and will roll out at the next backup rotation.
  5. 5Confirm in writing what was deleted and what you retain, on what basis, and for how long.

When to bring us in

If requests clash with tax or labour-law retention, a GDPR lawyer helps you ground the trade-off.

See also

None of the above fits?

Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.

Who are you?

For the AI question we need your email and company, so we can follow up if the AI gets stuck, and to prevent abuse.

Limited to 2 questions per hour and 5 per day, kept lean so the AI stays useful. For more, contacting us directly works better for you and us.

Or skip the DIY entirely

Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.