Data retention and legal hold

Evidence stays,
the person goes.

Erasure doesn't destroy the record, it cuts the link to the person: the record stays readable but can no longer be tied to anyone.

Retention policy

  • Retention period120 months
  • Pseudonym
  • Legal holdcase

Erasure under a hold is queued and runs once the hold lifts.

What's included

From retention to erasure.

  • 120-month retention

    10 years by default; it can be shortened per setup but never below 12 months.

  • Archive, not delete

    Expired partitions are archived logically, never deleted; the archive record is written first.

  • Pseudonyms

    The raw customer key lives only in one encrypted table; everywhere else uses keyed per-organisation pseudonyms.

  • Person-link erasure

    Irreversible, and only with the fraud:erase_customer permission.

  • Legal hold

    By organisation, customer, case or date range; only the platform can lift a hold and hold records are never deleted.

  • Queued erasure

    Erasure under a hold is rejected and queued, then runs on its own once the hold lifts.

How it works
  1. 01

    Written pseudonymised

    Records are pseudonymised when written.

  2. 02

    Archived

    Expired partitions move to the archive.

  3. 03

    Erasure request

    The person link is cut for good.

  4. 04

    Hold freezes

    Archiving and erasure stop until the hold lifts.

Make fraud decisions
with your own rules.

Let's set up your flows and thresholds together with our team.

For enterprise inquiries: [email protected]

Data retention and legal hold — Fraud and Risk | Lunixi