Privacy requests let customers, prospects, or workspace contacts ask for access, correction, deletion review, export, consent withdrawal, marketing opt-out, or another privacy action without signing in.
Who can submit a request
The privacy request form is public and does not require a Cendaro login. It is meant for people who want Cendaro or a workspace owner to review privacy-related information connected to a business workspace.
Request types
- Data access request.
- Correction request.
- Deletion review.
- Export request.
- Consent withdrawal.
- Marketing opt-out.
- Other privacy request.
What happens after submission
- 1The requester submits /privacy/request with contact details, request type, workspace context when known, subject contact details when relevant, and request details.
- 2Cendaro creates a unique request reference and stores the request with Received status.
- 3Cendaro may need to verify identity and confirm the request scope before disclosing, correcting, exporting, deleting, or restricting information.
- 4Cendaro or the workspace owner reviews whether Cendaro controls the relevant information or acts as a service provider for the workspace.
- 5The request is updated as it moves through review, completion, or closure.
Status checking
The requester can use /privacy/request-status with the request reference and requester email. Cendaro shows status only when both values match.
- The status checker can show reference, request type, status, created date, and completed date when available.
- Sensitive request details should not be shown through status lookup unless identity has been verified.
Workspace owner role
Workspace owners remain responsible for customer notices, consent, and responding to privacy obligations where they control the customer relationship. Cendaro records and supports the workflow, but some actions may require the workspace owner to confirm scope or instructions.
Audit and evidence
- Privacy request creation should write a privacy_request_created audit log.
- Operational notes should avoid unnecessary sensitive details.
- Request verification should be completed before releasing customer data or confirming account-specific details.
Was this article helpful?
Your answer helps Cendaro improve launch documentation.