Use a real privacy path, not the demo flow.

If you are a public client and you have an active verified phone session, use /api/public/privacy/export to retrieve your profile, linked phones, orders, appointments, and worker reviews.

Use /api/public/privacy/delete when you want supported erasure or anonymisation for your client record. The request requires confirmErasure=true and the same verified phone-session context.

If you no longer have a verified session, start from the public phone verification flow first so the request can be tied to the correct workspace client identity.

Authenticated owners and admins can export their own account and administered workspace access data through /api/privacy/export.

Authenticated workspace owners and admins handling tenant customer requests can use /api/admin/clients/privacy/export and /api/admin/clients/privacy/delete with the relevant workspaceId and clientId.

For contract, billing, or implementation questions that require workspace context, sign in and use the in-app feedback form so the request can be tied to your authenticated workspace membership.

Workspace owners and admins remain responsible for customer-facing notices and instructions when they use Ralevio to process end-customer records inside their workspace.

Review /privacy for controller/processor roles, processors, cookies, rights, and retention disclosures that match the current codebase.

Review /terms for service, account, billing, suspension, and data-governance obligations.

If you need a processor, transfer, or accountability clarification beyond those public pages, start with /contact and then continue through the authenticated feedback form where applicable.