Prototype case · Fictional data
TR-0241 is an invented case built to demonstrate the proposed information structure. It did not come from a customer, no real person is represented and no legal conclusion should be inferred.
Case TR-0241 · Illustrative customer
Assemble available requester records, expose gaps and questions, prepare a response structure and stop before disclosure or erasure until an authorised person approves the next action.
Sample event record
The sequence shows the proposed audit language. It is a normal timestamped activity record—not a claim of cryptographic immutability.
Illustrative access and erasure request entered through a privacy inbox.
Verification status recorded as pending; no sufficiency decision is implied.
Three sample sources associated with the agreed requester identifiers.
Twenty-four fictional records added to the source inventory.
Seven fictional billing records added; retention question opened.
Eleven fictional conversation records added through a sample manual-import path.
One fictional support record marked for authorised review.
Prototype response structure assembled from the sample case facts.
Two open decisions passed to the fictional reviewer role.
The example stops at the review boundary. No real disclosure or deletion occurred.
Sample source ledger
A credible pack records the path to each result. “No record found” only means something when the source, identifier and retrieval method are visible.
Scroll horizontally to view the complete illustrative ledger.
| Source | Access path | Sample result | State |
|---|---|---|---|
| Supabase | Controlled query · prototype | 24 fictional records | Mapped |
| Stripe | Restricted export · prototype | 7 fictional records | Retention review |
| Intercom | Manual import · prototype | 11 fictional records | Third-party review |
These rows demonstrate format only. Trace does not represent that one-click connectors retrieved this data or that these systems are live integrations.
Illustrative response pack
The pack is designed to make verification and decision-making easier. Actual formats, secure-delivery controls and retention are agreed for an accepted pilot.
Request, scope, identity state and open decisions
Fictional source folders and sample record manifests
Sources, access methods, counts, query notes and gaps
Illustrative structure awaiting authorised review
Third-party reference and retention question
Sample event sequence; no immutable-log claim
Founding design partners
Share the operating context—not personal data. Trace is looking for privacy professionals and SaaS teams willing to test where the pack helps, where it fails and where judgement must remain visible.