Core Concepts
Deletion jobs & Rights cases
Cases, verification, durable jobs, and worker execution.
Deletion jobs & Rights cases
What it is
A Rights case (deletion request) is the aggregate for one subject erasure. Execution uses durable jobs claimed by a worker.
Why it exists
Email threads and one-off SQL do not scale and leave no consistent trail.
How Erasure uses it
| Concept | Role |
|---|---|
| Case status | OPEN → IN_PROGRESS → COMPLETED / FAILED / CANCELLED |
| Verification | UNVERIFIED / VERIFIED / FAILED (orthogonal to status) |
| Job | Durable unit of work (rights.delete) |
| Worker | Process that claims jobs and runs Systems |
| Activity | Timeline of what happened |
Start requires VERIFIED + readiness. Without a worker, jobs remain pending.
Public intake vs operator verification
| Path | VERIFIED means |
|---|---|
| Public OTP | Subject proved control of email |
| Operator | Operator asserted verification |
Do not conflate the two in compliance narratives (app_docs/guide/faq.md).
Case shape (API)
Cases include type: "DELETE", status, verificationStatus, subject (email / externalId / label), timestamps, and events on detail (list omits events). See Rights API.
Related
- Systems · Evidence
- Guide: Handle a deletion request
- DPDP: Deletion requests