Backed by: your Worker’s compliance reads: the control plane’s evidence pack, erasure, holds and processing record, the audit capability’s chain and sinks, and the consent capability’s records. Scopes: evidence:read · audit:events:export · erasure:read · audit:events:read · retention:read · consent:read · processing:read, and retention:hold for a hold. Plan: Enterprise.
What it answers
Show me the evidence. What an auditor asks for, derived by your Worker from its own declarations and records rather than assembled by hand.
One pane, seven sections, each the answer to one read on your Worker. Compliance evidence, erasure attestation, retention and legal holds and the record of processing are the control-plane reads behind them, tamper evidence and shipping are the audit trail’s, and consent is the consent capability.
The pane sits in the rail’s Compliance group, per environment. The index lists the sections; each record reads its own route, parses the answer with the schema the kit exports for it, and draws it. Every answer is dropped with the screen, like every other pane.
The seven sections
| Section | What it shows |
|---|---|
| Evidence pack | Each control with its SOC 2 and ISO 27001 references, the facts your Worker read and where each came from, and its state: evidenced, gap with what is missing, or not derivable with why. The mapping version is named on every pack |
| Audit trail | For a tenant and a range, whether the chain verifies, how many events and checkpoints it was held to, and where it first breaks when it does not. The chain’s own export, a page at a time |
| Erasure | Over the last 30, 90 or 366 days, every purge that came due, the failed and overdue ones first, each naming the step it stopped at. A purge opens to its subject’s attestation: every step, whether it erased or retained, and the audit events it cites |
| SIEM | Each sink your Worker ships the trail to: delivering, failing or never attempted, its last delivery and last failure, its backlog, how many events were dead-lettered, which actions it takes, and whether personal values go out as recorded or as salted hashes |
| Retention and holds | The effective retention for each purge window, the audit trail and each privacy class, with where each number came from, and every legal hold, standing ones first |
| Consent | Grants, withdrawals and expired grants per purpose and notice version, the signed grants expired or expiring within 30 days, and one account’s or visitor’s record, with the signed document it holds |
| Processing record | Every activity with its purpose, data classes, legal basis, recipients, retention and measures, and every gap the record names, a phi field no signed consent covers among them |
None of it is a verdict. The evidence pack says evidence for an auditor, and never that a control passed or that anything is compliant. An auditor weighs it.
The trail’s export is the file pithy audit verify checks offline. A Worker that binds no checkpoint bucket is verified on its links alone, and the section says so, because a chain rewritten end to end would read as whole.
Every section exports
Export as JSON saves your Worker’s answer byte for byte, as <section>-<environment>-<when>.json, built in your browser and held nowhere. A signed document saves as the document it is.
A legal hold, the one act
Placing or releasing a hold is the only act on the pane, and it is the exception, named as one: a hold suspends acts and performs none. While it stands, every purge, prune and inactivity deletion touching its subject stops.
A hold is on a user, an organization, a tenant’s audit trail or the untenanted trail. Each act asks why, up to 256 characters, and confirms once. It goes to your Worker through POST /control-plane/holds or POST /control-plane/holds/:holdId/release, and the holds read again.
retention:hold is a write, so it is never in the default grant. A connection without it shows the act unavailable, naming the scope. Scopes is how to add it.
Each act is on our trail too, as customer/hold_placed or customer/hold_released, with the hold, what it preserves, where it now stands and the reason you gave.
On Free, Solo and Team
The pane is drawn locked, and says what Enterprise buys. Every section is listed, and nothing is read. Each one is a route on your Worker, readable by your own client on any plan.
When a section cannot answer
It sends nothing it would be refused, and the others still render. A section whose route your Worker does not declare says so. One whose scope this connection was not granted names the scope and offers to add it. An answer that does not match the kit’s schema, or is about something other than what was asked, is not drawn.
It keeps nothing
Nothing here is kept. Every answer is fetched from your Worker for this screen and held in no Pithy table, cache or log. The one row we write is the hold act’s, on our own trail.