Request population
A synthetic DROP request population with request identity, cycle dates and controlled matching keys.
Synthetic product walkthrough
California DROP cycle control
A synthetic 45-day operating cycle turns authorized request records, downstream-system evidence and repeat-appearance checks into a reviewable deletion-control packet.
Synthetic inputs
See exactly what enters the control
No customer, provider or production data is used in this demonstration.
Downstream system register
A synthetic register of downstream systems that should participate in the deletion-control cycle.
Prior-cycle evidence
Synthetic prior-cycle receipts and retained evidence used to detect reappearance and evidence gaps.
Scope3 systems checked
Findings2 exceptions
OutputEvidence packet
Controls exercised
- Request-to-record matching
- Deletion-routing completeness
- Downstream evidence coverage
- Repeat-appearance detection
- Cycle deadline control
Synthetic findings
- A synthetic subject reappears in one downstream CRM after prior completion evidence and is reopened.
- One downstream processor lacks retained completion evidence, so the cycle cannot be represented as fully evidenced.
- All other matched systems retain traceable cycle evidence without claiming regulator acceptance.
Proof boundary
What this demonstration proves
The demo proves how Saxum controls a synthetic DROP cycle from intake through evidence closure.
What it does not prove
It does not prove that a real downstream provider deleted a person, satisfy a broker’s legal duty, or replace the registered broker’s DROP actions.
Bring a real cycle →Evaluate the workflow before onboarding
The synthetic walkthrough shows the shape of the control. A real assessment tests your sources and exceptions without silently granting provider authority.