Policy & trust
User Data Deletion
Last updated:
Unchained does not currently provide a one-click full-account deletion endpoint. To request deletion of hosted account data, send a request from your account email to:
What to Include
- Your account email address.
- Subject line:
Data Deletion Request. - Whether the request covers the full hosted account or only specific records.
- For a full hosted-account request, specify account/authentication records, encrypted provider-credential records (including inactive records), hosted conversation files that still exist, scheduler definitions/state/run history, account-linked analytics records, and pending or approved public-result records.
- List each public-result slug if available. Public-result rows are stored separately, so deleting an account or source conversation does not automatically delete them.
Deletion Coverage
- Requests are handled manually. We verify account ownership and confirm the records covered by the request before removing eligible account-linked data from active service storage.
- Revoking a provider credential only marks it inactive; include provider-credential records in the request if you want the encrypted database record removed.
- Deleting a scheduler job does not remove its prior state or run history; include scheduler state and run history in the request if you want those files removed.
- Starting a new hosted trial chat removes the prior active trial session file, but other hosted conversation files must be included in the request.
- Rejecting a pending public result deletes its stored row. Approved public results have no self-service deletion control and must be named in a manual deletion request.
- Records that must be retained for security or legal reasons are outside the scope of removal from active service storage.
What a Server-Side Request Does Not Delete
A server-side request cannot delete local CLI chat slots or archives stored on your machine, browser history or downloads in your Chrome profile, or public-result copies already indexed, cached, copied, or redistributed by search engines, AI systems or training datasets, social-preview networks, Google, Facebook, GitHub, an AI model provider, or another third party. Remove local data on the relevant device and contact third parties about data they control.
For policy details, see /privacy.