PRIVACY / REQUEST WORKFLOW
Data deletion requests
How customers and individuals request deletion, what we verify, and which records may need to be retained.
The workflow is implemented as a support intake. Production identity verification, support ownership, and automated retention jobs must be verified before launch.
Submit a request
- Open the support page and select “Data or privacy request.” Identify the product and organization, but do not include passwords, access tokens, medical records, or full payment details.
- An organization admin should submit workspace-wide deletion. An individual request should identify the relevant work email and customer organization.
- We verify identity, authority, affected systems, contractual retention, and legal holds before deletion. A request is not complete until its scope is confirmed.
Deletion sequence
After verification, active diagnostic data and connector credentials are scheduled for deletion first, followed by derived results and eligible support records. Encrypted backups age out under the backup schedule and remain access-restricted in the interim.
We may retain narrowly required billing, fraud-prevention, security, audit, dispute, or legal records. Where full deletion is not permitted, access is restricted and the reason is recorded. The requester receives confirmation through the verified channel.
Uninstalling a marketplace app
Uninstalling should revoke future platform access and queue credential removal. It does not replace a deletion request where an audit history or customer-selected evidence record remains. Each production connector must pass an uninstall and erasure test before marketplace submission.