Privacy: export, deletion and admin audit
Owner-api 1.9.0 (R-389, R-390). Personal data on a core is operational identity and contact data - not the signed money trail. Export and delete are owner-token (or console) routes; organisation members cannot call them.
What is personal data here
| Field | Where | Deleted by |
|---|---|---|
| Alert email recipients | host store alert_settings | POST /owner/v1/privacy/delete |
| Mail-queue recipients | host store mail_queue | full delete |
| Organisation members and roles | primary engine org_members / org_roles | full or memberId |
| SSO member sessions | host store member_sessions | full or memberId |
| Payee destinations (address, Connect id, wire bank id) | host store | exported, never deleted here (see below) |
| KYA attestations | host store | full delete |
| End-user budget links and portal/budget tokens | DevX tables | full or endUserRef |
| Console sessions | host store | full delete |
| Account email (multi-tenant) | tenancy registry | POST /tenant/v1/privacy/delete |
What is kept, and why
Signed authority records, vouchers, consume rows, payment records, organisation records and evidence bundles are not deleted. Neither are payee payout destinations: they route money the payee is owed and were written under the payee's own signature, so only the payee changes them (deleted.payeeDestinations is always 0). They are offline-verifiable facts needed for disputes and so that a payee can still claim proven work (rules 25, 27, 39). The export answer lists them under keeps with that reason.
Routes (self-hosted / tenant core)
Pin Dynamo-Version: 1.9.0 (or later).
# Export
curl -sS -H "Authorization: Bearer $OWNER_API_TOKEN" -H "Dynamo-Version: 1.9.0" \
"$CORE/owner/v1/privacy/export"
# Erase all operational personal data on this core
curl -sS -X POST -H "Authorization: Bearer $OWNER_API_TOKEN" -H "Dynamo-Version: 1.9.0" \
-H "content-type: application/json" \
-d '{"confirm":"delete-personal-data"}' \
"$CORE/owner/v1/privacy/delete"
# Erase one end-user's links only
curl -sS -X POST -H "Authorization: Bearer $OWNER_API_TOKEN" -H "Dynamo-Version: 1.9.0" \
-H "content-type: application/json" \
-d '{"confirm":"delete-personal-data","endUserRef":"user-42"}' \
"$CORE/owner/v1/privacy/delete"
Multi-tenant account email
On the front door, with a dashboard session or owner key:
GET /tenant/v1/privacy/export- account email, email-link count, sessions, API key prefixesPOST /tenant/v1/privacy/delete-{confirm:"delete-personal-data"}; revokes keys, drops sessions and email links, replaces the email with a non-deliverable placeholder; the tenant core and its signed records stay
Then call POST /owner/v1/privacy/delete on that tenant's owner token to scrub the core.
Admin audit (R-390)
GET /owner/v1/admin-audit?since=&after=&limit=&actor= returns actor-attributed rows for freeze, thaw, stop, amend, approvals, org role changes, scoped credentials, main-switch pause/resume, revenue changes and privacy export/delete. Retention is CORE_ADMIN_AUDIT_RETENTION_SECONDS (default 90 days). On the multi-tenant front door, key create/revoke and account privacy delete appear on GET /tenant/v1/admin-audit.
Manual procedure for design partners (before stage 1)
Until every partner uses the routes above, an operator can serve a data-subject request by hand:
- Identify the deployment (single-tenant path or
tenantId+ env). - Export: call
GET /owner/v1/privacy/export(and/tenant/v1/privacy/exportwhen multi-tenant) with the owner credential; deliver the JSON to the requester over an agreed channel. Do not put secrets or raw card data in the package (there are none in these tables). - Erase: call
POST /owner/v1/privacy/deletewithconfirm, then/tenant/v1/privacy/deletewhen multi-tenant. Confirm in the admin-audit log. - Tell the requester what was kept (signed money and authority records) and why.
- Record the request id, timestamps and the actor who ran the commands in your own ticket system (the admin-audit row is the in-product proof).