Subject Access Export
A subject-access export flow — open, manifest, seal — that proves the pipeline end-to-end with content-hashed receipts, without touching live PII systems.
The problem
/ 01When demonstrating a subject-access-right workflow, you need a pipeline that opens a request tagged by a subject reference, completes it with an export manifest, seals the receipt into a tamper-evident carrier image, and reports status — while being honest that this is a demo catalog, not production SAR handling.
What it does
/ 06Opens a subject-access request by subjectRef (a reference hash, not a real identity), with optional scope, requesterId, dueBy, and meta.
Returns a requestId, contentHash, and initial status (open).
Completes a request with an exportManifest (JSON array or object) or exportManifestText, optional artifactHash, and status (completed).
Returns a receiptId, contentHash of the manifest, artifactHash, and updated status.
Optionally seals a receipt into a carrier PNG via imageBase64 + dimensions + optional key binding.
Fetches a full record by request ID and lists all requests.
Private pilot adds
/ pilotPilot-ready: durable subject-access store available under NDA with a /v1 API for private pilots. The public studio card runs against /demo (ephemeral).
Who it’s for
/ 03- Privacy engineers building SAR pipelines
- Compliance teams demonstrating access workflows
- Auditors verifying manifest sealing
In context
/ 01Complements Consent Receipt Registry (consent integrity), Stego Audit Carrier (carrier sealing), and the Consent Receipt Registry seal flow.