docsloth.com
Privacy
See what is collected, where it is processed and how to control it.
Approval status
A counsel-approved privacy notice has not been supplied. The processing facts below are the implemented behaviour of this build; the final notice must be reviewed for the jurisdictions actually served before launch.
Purposes and consent
| Purpose | Data | Consent rule |
|---|---|---|
| Essential service and security | Account, source, job and audit records needed to run what you asked for. | No consent toggle; required to provide the service. |
| Optional analytics and replay | Consented reader events and masked replay sessions. | Off until the published site consents; replay is never captured on first load. |
| Personalization | Preferences that change what you see. | Separate consent; not bundled with essential processing. |
| Marketing | Product updates and announcements. | Separate consent; never bundled with hosting or necessary processing. |
Retention
- Source checkouts
- 24 hours by default.
- Operational logs
- 14 days.
- Replay sessions
- 30 days.
- Cloud backups
- 35 days; expired on the retention schedule.
- Raw model request/response bodies
- Not logged by default; diagnostics require explicit bounded opt-in and redaction.
- Analytics
- Per plan, with the window stated in the workspace.
Rights, export and deletion
- You retain rights to your code and content subject to their licences; Docsloth needs only the limited processing authorization in the reviewed terms.
- Export is available before downgrade or deletion except where security or legal restrictions apply, and an export refuses credential fields.
- Deletion creates a scoped erasure job: ingestion stops, tokens are revoked, live and private artifacts are removed, and completion is recorded.
- Backups expire on the retention schedule; we do not claim immediate physical removal from immutable backups.
- Data-subject requests are verified without collecting unnecessary identity documents.
- BYOK still sends selected content to the provider you chose; the workspace discloses provider, region and retention policy rather than promising zero external processing.
Actions
Actions
- Manage consent
Jumps to the purpose table above. Consent is configured per published site; this build runs no managed deployment, so no consent surface is active here.
- Request data export
Routes to support. Export runs from an authenticated workspace before downgrade or deletion; no account credentials are collected through this public page.