Prove each DROP cycle without replacing your privacy stack
Saxum reconciles the request population, downstream action evidence, exceptions and completion records around the tools you already use. It is an independent control layer—not a replacement DSR platform.
No portal credentials. No guaranteed external result. Scope confirmed before sensitive material is transferred.
Current requirement snapshot
Beginning 1 August 2026, registered California data brokers must access DROP at least once every 45 days and process applicable requests made available through the mechanism within the required statutory cycle. Saxum manages preparation and evidence; the registered broker remains responsible for its legal obligations and portal actions.
Why the standard portal or checklist is not enough
Established privacy platforms can orchestrate deletion. The remaining control problem is proving that every downloaded request reached the right systems, that exceptions were authorized, and that completion evidence reconciles back to the original DROP population.
Best-fit customer
Privacy consultancies managing recurring DROP cycles and registered California data brokers
Problems this product helps control
California DROP deletion cycles where request populations, suppression evidence, exceptions and 45-day operating cadence need a reviewable control record.
A bounded intake, not an open-ended data dump
The case starts with enough context to reproduce the problem and define responsibility. Credentials, unrelated personal data and unsupported assumptions are excluded.
- Registration and current operating model
- Record-system inventory and approximate volume
- Customer-controlled hashed or tokenized matching inputs
- Prior-cycle procedure or evidence, when available
What arrives at the end of the engagement
The output is designed to be reviewed, handed off and defended—not merely marked “passed.”
- Source-to-action population reconciliation
- System-by-system completion evidence register
- Unmatched and exception worklist
- Authorized waiver and suppression record
- Cycle receipt with counts, timestamps and hashes
- Independent management-ready control summary
From messy source material to a reviewable release packet
Each stage has a clear stop condition. When evidence is insufficient, the case pauses rather than manufacturing certainty.
Scope
Confirm registration, systems, data minimization and responsibility split.
Process
Run the controlled matching and exception workflow against customer-supplied inputs.
Verify
Reconcile totals, document unresolved records and produce an evidence index.
Close
Customer completes required system actions and retains the signed cycle packet.
Track every work item from official download to evidenced outcome
Saxum can run from an official file package or authorized API connection, receive signed webhook events, match privacy-minimized identifiers and keep unresolved actions visible until the broker confirms deletion, exemption or opt-out.
Cycle completeness ledger
Reconcile official list counts, matched records, ready responses, removed items, pending exceptions and exact-filename response files.
System handoffs
Produce deletion worklists and suppression seeds, attach evidence, assign owners and retain API receipts without claiming that an unconfirmed action occurred.
Event-driven control
Use signed webhook replay protection, source-version watches, credential-backed retrieval, notifications and partner portfolio reporting across segregated clients.
Run segregated DROP cycles across a consultancy portfolio
Keep each registered broker isolated while reusing approved intake mappings, cycle controls and evidence templates across the firm.
Segregated accounts
Each customer, entity or operating unit keeps separate source evidence, mappings, exceptions and outputs.
Reusable controls
Approved mappings and review policy reduce repeat setup without allowing one client's assumptions to leak into another.
Portfolio oversight
Firm teams can see recurring due work, unresolved exceptions and evidence-backed outcomes without flattening client boundaries.
Show the buyer exactly what Saxum proved
The first controlled cycle produces customer-visible proof before the workflow is expanded. Saxum keeps internal completion separate from external/provider acceptance and never turns estimates into verified outcomes.
Source coverage
See which files, mappings and authority sources were used, what was missing and which assumptions remained unresolved.
Exception register
Every blocker has a reason, owner and current state. Unsupported facts remain open instead of disappearing into a generic pass.
Evidence-graded scorecard
Separate Saxum-completed work from provider-final evidence, verified value, source-backed exposure, observed time savings and estimates.
Use this when the cost of an unresolved exception exceeds the cost of review
Best fit: a registered broker or privacy consultancy already using execution tooling but lacking an independent, source-linked cycle-control packet.
Every engagement starts with scope confirmation. Pilot and research offers are intentionally limited until the workflow is proven on paid cases.
Request a DROP cycle assessment →DROP Cycle Desk FAQ
Direct answers on access, responsibility, deliverables and limits.
No. Saxum does not request portal credentials. The customer’s authorized personnel retrieve and submit any portal-controlled material.
The workflow is designed around minimization. Exact inputs depend on the customer’s architecture, and tokenized or hashed handling is preferred wherever technically workable.
No. It provides operational controls and evidence. Legal interpretation and final compliance responsibility remain with the customer and its counsel.
The value is the repeated control: matching, exceptions, evidence and deadline ownership are recreated on each required cycle.
Yes. A partner model can standardize the workflow across several data-broker clients while preserving client-specific evidence.
Verify the underlying requirement
Saxum product pages link to primary agency or platform material so buyers can confirm the official requirement themselves.
Primary-source review date: 20 August 2026. Re-check before each engagement.
Continue the control layer
Bring the real case, not a hypothetical
Describe the workflow, deadline and evidence you already have. Do not send passwords, API keys or regulated data through the public form.
Saxum Control Platform
Run this workflow in the encrypted control room
Schedule or run the engine, apply saved mappings and connectors, assign exceptions, collect evidence, complete Human ReviewPass and publish signed outputs with measurable value reporting.
Open the control roomSee the workflow before you bring customer data
Every executable Saxum product now has a synthetic first-cycle walkthrough. Where a free checker or guide exists, it is linked here too.