Legal center
The versioned legal and compliance documents behind AnyBot (terms, privacy, a DPA and more), where to read them, and how acceptance and re-acceptance work.
Every legal and compliance document that governs your use of AnyBot lives in one place, is versioned, and can be read without signing in. This page explains which documents exist, where to find them, and how acceptance (and re-acceptance when a document changes) works. For the broader stance on GDPR, a DPA, residency and the audit trail, see Security & data handling; for the controls you operate over your own data, see Data & privacy controls.
The documents
These are the documents AnyBot publishes today. The set is maintained by AnyBot and can grow over time; two of them must be accepted to use the product, and the rest are reference documents you can read at any time.
| Document | Purpose | Acceptance |
|---|---|---|
| Terms and Conditions | The agreement governing your use of AnyBot | Required |
| Privacy Policy | What data we collect and how it's handled | Required |
| Data Processing Agreement (DPA) | Processor terms for teams that need one | Reference |
| GDPR Notice | Data-subject rights and how to exercise them | Reference |
| Cookie Policy | Cookies and similar technologies we use | Reference |
| Acceptable Use Policy | What you may and may not do with AnyBot | Reference |
| Refund Policy | How refunds are handled | Reference |
Each document carries a version label and a publish date. Today every document is at its first published version. As documents are revised, the version advances and the change is timestamped.
Where to read them
You don't need an account to read any of these:
- From the app footer: the Privacy Policy and Terms links appear at the bottom of the app.
- On the sign-in and sign-up screens: creating an account links the Terms and Privacy Policy inline, so you can review them before you agree.
- Direct link: each document has a stable URL of the form
/legal/<slug>(for example/legal/privacy-policyor/legal/data-processing-agreement).
Documents render as formatted text, so the DPA, GDPR Notice and the rest are readable in the browser without downloading anything.
Accepting and re-accepting
The Terms and Conditions and Privacy Policy require acceptance; the other documents are reference-only and don't need a click.
When you're signed in, AnyBot checks whether you've accepted the current version of each required document. If a required document is unaccepted, or has been updated to a newer version since you last agreed, a dialog appears with the full text and an Accept button. It's shown one document at a time and can't be dismissed until you accept, so agreement is always tied to a specific published version.
When you accept, AnyBot records the exact version, a timestamp, and technical metadata (your IP address and browser) as proof of consent. This is a deliberate, standard record kept for compliance evidence.
Versioning and updates
Documents are managed by AnyBot's team, and each one keeps a history of versions. Only the published version is what you read and accept. Drafts aren't shown. When a new version of a required document is published, everyone is re-prompted to accept it on their next visit; reference documents simply update in place. Publishing a new version is itself recorded in the internal governance audit trail, so there's a record of when each version went live.
Languages
Documents are served in English today. The API accepts a locale parameter and the platform is built to return translated copies, but localized legal text isn't populated yet.
Reading them programmatically
The document set is also available through the AnyBot v3 API, useful if you want to surface the current Terms or Privacy version in your own onboarding, or check a user's acceptance status.
GET /legal # list active documents + current version
GET /legal/{slug} # full document content (Markdown); ?locale=xx
POST /legal/{slug}/accept # record acceptance (authenticated)
GET /legal/acceptances # a user's acceptance status per documentThe list and content endpoints are public; accepting and reading acceptance status require authentication.