Skip to content
Platform · Data Principal Rights

Rights, fulfilled on the clock.

Give people a portal to exercise every right the law affords them — and give your team the routing, deadlines and proof to fulfil each one on time, without it becoming an inbox of spreadsheets.

How it works

Four steps, one accountable trail.

Every request follows the same disciplined path — so nothing slips, and you can show exactly how it was handled.

  1. 01

    Raise

    A Data Principal opens a request from a self-service portal — access, correction, erasure, nomination or grievance — without emailing anyone or waiting in a queue.

  2. 02

    Verify & route

    Identity is verified, the request is logged with a clock started, and it is routed to the owner who actually holds the data.

  3. 03

    Fulfil

    The owner acts within the deadline. An access request is gathered and returned as a signed pack; a correction is applied and re-sealed; an erasure destroys the key material that protects the data.

  4. 04

    Prove

    Every step — who, what, when — is written to the audit trail, and erasure produces cryptographic proof the data is unrecoverable.

What you get

Every right, one workflow.

Access

Return a complete, structured copy of the personal data held about a Data Principal, gathered across your connected systems.

Correction & update

Let people fix what's wrong or out of date, with the change propagated to the systems that hold it.

Erasure

Crypto-shred removes the data by destroying its key — making it cryptographically unrecoverable, with proof.

Nomination

Capture a nominee who can exercise rights on a Data Principal's behalf in the event of death or incapacity.

Grievance

A first-line grievance channel with tracking, so concerns are logged, owned and answered before they escalate.

SLA & deadline tracking

Configurable timers on every request type, with reminders and escalation so a deadline is never quietly missed.

Open requests SLA tracked
Erasure DPR-4821 · Verified · crypto-shred Done
Access DPR-4822 · Gathering across 6 sources Due 9d
Correction DPR-4823 · Routed to data owner Due 21d
Grievance DPR-4824 · Awaiting first response Due 3d
Deadline Tracked
Owner Assigned
Proof
Inside the request queue

No request falls through the cracks.

Each request carries its own clock, owner and status. Erasure is the hard one — and it ends in cryptographic proof that the key was destroyed and the data can never be read again, not a promise that someone deleted a row.

  • Routed to the owner who holds the data
  • Deadlines tracked, with escalation before they lapse
  • Erasure ends in verifiable proof, not assurance

See a right requested, routed and proven.

A 30-minute walkthrough of the rights portal, routing and deadline tracking — mapped to your own data and teams.