Legal
Privacy Notice
1. Who we are, and how to reach us
Beweird SAS, 128 rue La Boétie, 75008 Paris, France, operates Azoth OS, a platform that governs and records the use of AI models by organisations.
Azoth OS is offered only to businesses and professionals, never to consumers (see our Terms of Service). The people this notice is about are therefore professionals acting for their organisation — account holders, the members of a workspace, billing contacts — and the people at the organisations we talk to as prospects.
Data protection contact: privacy@azothos.ai. We have not appointed a data protection officer; this address reaches the people responsible for data protection at Beweird SAS.
2. Our two roles
As controller, we decide why and how we process the data needed to run our business: your account and sign-in, the acceptance of our Terms, billing, the service's e-mails, security, support, the in-app assistant, the website's analytics and our contacts with prospects. This notice describes that processing.
As processor, we process the data an organisation (our customer) sends through Azoth — its AI calls, the prompts and answers its data policy lets us keep, the decisions we seal for it, its agents and rules — only on its instructions, under our Data Processing Agreement. The customer is the controller of that data: if you are one of its members, or a person its AI calls concern, its own privacy notice applies, and requests about that data go to it first. We help it answer them.
3. What we process, why, and on which legal basis
| Purpose | Personal data | Legal basis | Must you provide it? |
|---|---|---|---|
| Accounts and sign-in Creating your account, signing you in, securing it with two-factor authentication, and recording each sign-in. | E-mail address, name, company, language, password (stored hashed by Supabase Auth), Google or single sign-on identity when you use one, two-factor factor, sign-in events (time, method, IP address, browser). | Contract (GDPR art. 6(1)(b)). Sign-in events: our legitimate interest in securing accounts (art. 6(1)(f)). | An e-mail address and a password, a Google account or your organisation’s single sign-on are required to have an account; the sign-up form asks your name; your company is optional. |
| Acceptance of the Terms Recording that you accepted the Terms of Service, which version, and when, with your declaration that you act on behalf of a business or professional activity (the service is offered to professionals only). | The Terms version, the Privacy Notice version shown, the time, whether you accepted at sign-up or at your first sign-in, and your declaration that you sign up on behalf of a business or professional activity. | Our legitimate interest in being able to prove the contract (art. 6(1)(f)). | Accepting the Terms, and declaring that you act on behalf of a business or professional activity, are required to use the service. |
| Billing Charging paid plans, managing subscriptions and issuing invoices. | Billing contact, business name, address, VAT number or other business tax identification number, Stripe customer and subscription identifiers, invoices. Card details are held by Stripe only. | Contract (art. 6(1)(b)); keeping invoices: legal obligation (art. 6(1)(c), accounting and tax law). | Required for a paid plan; the Free plan needs none of it. |
| Service e-mails Sending the e-mails the service needs: confirmations, password resets, invitations, security and spending alerts, receipts — and the weekly point, a summary e-mailed each week to workspace owners and admins. | E-mail address, name, and the content of the e-mail. | Contract (art. 6(1)(b)). The weekly point: our legitimate interest in keeping those responsible for a workspace informed (art. 6(1)(f)) — it can be turned off. | The account e-mails cannot be turned off while the account exists; the weekly point can. |
| Security and abuse prevention Protecting the service and the accounts: rate limits, the bot check on the sign-in pages, refusing disposable e-mail addresses at sign-up, the audit log, error tracking. | IP address, browser, request identifiers, rate-limit counters, bot-check signals, audit-log entries, error reports (without IP address, cookies or user identity). | Our legitimate interest in securing the service and the accounts (art. 6(1)(f)), and the duty to secure processing (art. 32). | Necessary to use the service. |
| Support Answering your support requests. | The ticket’s subject and messages, who wrote them, a technical context the server computes (the page, the plan, error codes, a call reference — never a prompt, an answer or a key), and the assistant conversation if you choose to attach it. Azoth staff reach a workspace’s data only through an access an owner grants, for 4 hours at most. | Contract (art. 6(1)(b)). | Optional. |
| In-app assistant Answering the questions you ask the assistant about your workspace, with an AI model. | Your question, the last messages of the conversation and the workspace figures its tools read, sent to Anthropic; a fingerprint of each model call, sealed in the workspace’s journal; counts of questions and of their outcome. Azoth keeps no copy of the conversation unless you attach it to a support ticket. | Contract (art. 6(1)(b)) — a feature of the service you choose to use. | Optional: every suggested question can be answered without the model. |
| Product analytics and session replay Understanding how the website and the dashboard are used, and fixing bugs. | Pages opened, clicks and features used, a random browser identifier, browser and device type; a replay of a sample of visits, and of visits with an error, with every text masked and every image blocked. | Your consent (art. 6(1)(a); ePrivacy art. 5(3)), which you can withdraw at any time. | Optional: refusing changes nothing in the service. |
| Contact requests, support chat and marketing Answering the requests you send from the website, the support chat, and following the visits of people who accept the marketing cookies. | What you send (name, e-mail address, company, message) and the page it came from; with your consent, HubSpot’s visitor cookies, the pages you visit and your chat conversations. | Contact requests: steps you asked us to take (art. 6(1)(b)) and our legitimate interest in answering (art. 6(1)(f)). Chat and tracking cookies: your consent (art. 6(1)(a)). | Optional. |
| Consent records Being able to show what you accepted or refused (GDPR art. 7(1)). | The purposes accepted or refused, the policy version, the time, your IP address, browser and, when signed in, your account. | Legal obligation (art. 6(1)(c), art. 7(1)). | Recorded with each choice. |
| Backups Restoring the service after an incident. | An encrypted copy of the whole database. | Our legitimate interest in the continuity of the service (art. 6(1)(f)) and the duty to secure processing (art. 32). | Not applicable. |
For the data we process as processor (providing the service to a workspace): Call metadata (usage traces); prompts and answers only when the workspace’s data policy collects content (never in vault mode), with PII patterns redacted; sealed decisions holding fingerprints and keyed pseudonyms of the person a call was made for and of the people who approved it; agents, mandates and rules. The legal basis is the customer's.
We do not sell personal data, and we do not use it to train AI models. We make no decision based solely on automated processing that has legal or similarly significant effects on you (art. 22). Sign-up refuses addresses from disposable-mail services, and the bot check can stop automated traffic: if you think you were refused in error, write to us.
4. The decision journal and per-person attribution
For each customer, Azoth seals the decisions taken on its AI calls in a journal: each entry is chained to the previous one by a cryptographic hash, so that anyone can verify that nothing was changed, and that nothing was removed except as the retention below provides. A sealed entry is therefore never edited.
Sealed entries are kept for the journal retention the customer's plan includes (see /pricing), or for the period its contract sets. Each night, the oldest entries older than that period are removed, oldest first, behind a sealed checkpoint from which the rest of the chain can still be verified. None is removed sooner than the applicable law requires, nor while a litigation hold, an incident, a statement or a timestamp anchor still needs it.
A sealed entry holds no content: fingerprints (hashes) of the prompt and the answer, codes, costs, and keyed pseudonyms — a code computed with a secret of the workspace — of the person a call was made for (when the customer names that person, through a personal API key or a key allowed to name the person), of the person who answers for the AI system, and of the people who approved a request. The link between a pseudonym and a person is kept apart, outside the journal. When the customer's data policy collects content, the prompt and the answer, with PII patterns redacted, are kept beside the entry in an erasable part, never in the sealed part.
When your account is erased: the erasable part of the decisions made by you or for you is erased in every workspace, the link between your pseudonyms and you is deleted, and your audit-log rows lose their link to you. The sealed entries stay — they keep your former account's internal identifier and the pseudonyms, which no longer lead to you. An entry that a litigation hold designates keeps its erasable part until the hold is released (GDPR art. 17(3)(e)).
5. Who receives personal data
Only the service providers below, and only for what each does for us, under a data processing agreement — what is still being confirmed with a provider (its agreement, a region or a safeguard) is marked to verify. Google acts as a separate controller when you choose to sign in with it. We may also disclose data to a court or an authority when the law requires it.
| Recipient | What it does | Personal data | Where |
|---|---|---|---|
| Supabase Inc. | Database, authentication and file storage | All account and workspace data, encrypted provider keys, audit logs | European Union (Frankfurt, Germany) |
| Vercel Inc. | Hosting: the application runs in the EU (Frankfurt), behind a worldwide edge network | Every request and response in transit, request logs (IP address, browser) | European Union (Frankfurt) for the application; edge locations worldwide |
| Upstash, Inc. | Rate limiting and short-lived caches | IP addresses and account or workspace identifiers in rate-limit counters; cache entries | European Union (Frankfurt) |
| Stripe | Payments, subscriptions and invoices — and, as a separate controller, its own fraud-prevention and financial-regulation duties. For paid plans. | Billing contact, company, address, VAT number, payment method (held by Stripe only), invoices | European Union and United States |
| Brevo (Sendinblue SAS) | Sending the service’s e-mails (confirmations, invitations, alerts, summaries, receipts) | Your e-mail address, name, and the content of the e-mail | European Union (France) |
| Resend, Inc. | Fallback e-mail delivery when Brevo fails. Only when it is configured and Brevo cannot send. | Your e-mail address, name, and the content of the e-mail | United States |
| Functional Software, Inc. (Sentry) | Error tracking; and, only with your consent, session replay of the website and dashboard | Error reports (without IP address, cookies or user identity); with consent, a replay of a visit with every text masked and every image blocked | European Union (Germany) |
| PostHog, Inc. | Product analytics of the website and dashboard. Only with your consent (product analytics). | Pages opened, clicks and features used, a random browser identifier, browser and device type; it may receive the IP address the request comes from | European Union (PostHog EU cloud), sent through Azoth’s own domain |
| HubSpot, Inc. | Support chat and contact requests (CRM); with your consent, its tracking code on the site. One HubSpot account serves Beweird’s products, each tagged by business unit. Contact forms always; the chat and tracking only with your consent. | What you send through a contact form or the chat (name, e-mail, company, message); with consent, visitor cookies and the pages you visit | The account’s data region: European Union |
| Cloudflare, Inc. (Turnstile) | Bot check on the sign-up, sign-in and password-reset pages | Signals from your browser and your IP address, seen by Cloudflare when its check loads | Cloudflare’s worldwide network |
| « Continue with Google »: Google confirms who you are. Only if you choose to sign in with Google. | Google sends us your name, e-mail address, profile picture link and Google account identifier; Google knows you signed in to Azoth | Google’s infrastructure | |
| Anthropic, PBC | Azoth’s in-app assistant (Claude, with Azoth’s key); and, on a customer’s behalf, with Azoth’s key: its agents’ planner and llm_call tool, and image reading in Inventory Object (second in order, only when its key is set); and the workspaces that route calls to Anthropic | For the assistant: your question, the last messages of the conversation and the workspace figures its tools read. On a customer’s behalf: an agent’s goal, context and plan; the images uploaded to Inventory Object; the prompts and answers of those calls | United States |
| Mistral AI SAS on a customer's behalf | The onboarding trial key: a new workspace’s first calls, answered with Azoth’s key; and the workspaces that route calls to Mistral | The prompts and answers of those calls | European Union (France) |
| OpenAI, L.L.C. on a customer's behalf | With Azoth’s key: embeddings for the semantic cache, agent memory and the Inventory Object catalogue, and image reading in Inventory Object (first in order, only when its key is set); and the workspaces that route calls to OpenAI | The text embedded; the images uploaded to Inventory Object; the prompts and answers of those calls | United States |
| Google LLC (Gemini) on a customer's behalf | Image reading in Inventory Object with Azoth’s key (third in order, only when its key is set); and the workspaces that route calls to Google Gemini | The images uploaded to Inventory Object; the prompts and answers of those calls | European Union and United States (to verify) |
| Hugging Face, Inc. on a customer's behalf | Last-resort image captioning in Inventory Object, with Azoth’s key. Only when its key is set and the providers before it could not read the image. | The images uploaded to Inventory Object | United States (to verify) |
| Staan (Qwant, European Search Perspective) on a customer's behalf | Web search for the agents’ web_search tool, with Azoth’s key. When its key is set. | The search queries an agent’s plan produces — they may carry the customer’s goal or context | European Union (EU data centres, as Staan states it — to verify) |
| Serper.dev on a customer's behalf | Fallback web search for the agents’ web_search tool, with Azoth’s key. Only when its key is set and Staan’s is not; never for a workspace whose residency allows EU providers only. | The search queries an agent’s plan produces — they may carry the customer’s goal or context | United States (to verify) |
| The model providers a customer chooses on a customer's behalf | Answering the calls a workspace routes to them, with the customer’s own keys (AWS Bedrock, Azure OpenAI, DeepSeek, OpenRouter… — the sub-processor list). Only the providers the workspace configures. | The prompts and answers of those calls, as the workspace’s data policy allows | Per provider (the sub-processor list) |
| GitHub, Inc. | Source code and continuous integration; the nightly backup job reads the database and encrypts the dump before it leaves the job’s machine | During the backup only: all database content, in the job’s memory, encrypted before upload | United States |
| Backup object storage (S3-compatible, EU bucket) | Keeping the encrypted nightly backups | Encrypted database dumps — the key never leaves Azoth | European Union |
The sub-processors that process customer data, and their safeguards, are listed in our Data Processing Agreement.
6. Transfers outside the European Economic Area
Our database and our application run in the European Union (Frankfurt). Some providers are US companies, or process data outside the EEA; a transfer relies on the European Commission's Standard Contractual Clauses (Decision 2021/914) in the provider's data processing agreement, and a safeguard still being confirmed with a provider is marked to verify:
- Supabase Inc. — Supabase is a US company: EU Standard Contractual Clauses (Commission Decision 2021/914), in the vendor’s data processing agreement, for any access from outside the EEA.
- Vercel Inc. — EU Standard Contractual Clauses (Commission Decision 2021/914), in the vendor’s data processing agreement.
- Upstash, Inc. — Upstash is a US company: EU Standard Contractual Clauses (Commission Decision 2021/914), in the vendor’s data processing agreement.
- Stripe — EU Standard Contractual Clauses (Commission Decision 2021/914), in the vendor’s data processing agreement.
- Resend, Inc. — EU Standard Contractual Clauses (Commission Decision 2021/914), in the vendor’s data processing agreement.
- Functional Software, Inc. (Sentry) — Sentry is a US company: EU Standard Contractual Clauses (Commission Decision 2021/914), in the vendor’s data processing agreement.
- PostHog, Inc. — PostHog is a US company: EU Standard Contractual Clauses (Commission Decision 2021/914), in the vendor’s data processing agreement.
- HubSpot, Inc. — HubSpot is a US company: EU Standard Contractual Clauses (Commission Decision 2021/914), in the vendor’s data processing agreement.
- Cloudflare, Inc. (Turnstile) — EU Standard Contractual Clauses (Commission Decision 2021/914), in the vendor’s data processing agreement.
- Anthropic, PBC — EU Standard Contractual Clauses (Commission Decision 2021/914), in the vendor’s data processing agreement.
- OpenAI, L.L.C. — EU Standard Contractual Clauses (Commission Decision 2021/914), in the vendor’s data processing agreement.
- Google LLC (Gemini) — To verify — the safeguard in the vendor’s terms is being confirmed.
- Hugging Face, Inc. — To verify — the safeguard in the vendor’s terms is being confirmed.
- Serper.dev — To verify — the safeguard in the vendor’s terms is being confirmed.
- The model providers a customer chooses — Per provider (the sub-processor list).
- GitHub, Inc. — EU Standard Contractual Clauses (Commission Decision 2021/914), in the vendor’s data processing agreement.
You can ask us for a copy of these safeguards at privacy@azothos.ai.
7. How long we keep it
| Data | How long |
|---|---|
| Your account (e-mail address, name, company, sign-in identities, two-factor factor) | As long as the account exists. Deleting it from Account & Privacy › Delete my account erases it at once, with the workspaces you own. |
| The record of your acceptance of the Terms (version, time, your declaration that you act for a business or professional activity) | As long as the account exists; its audit-log copy for 24 months. |
| Usage traces — the metadata of each model call (model, tokens, cost, latency, status, identifiers) | 12 months by default, then deleted by the nightly purge. |
| Prompt and answer kept with a sealed decision — only when the workspace’s data policy collects content, never in vault mode, PII patterns redacted | 12 months by default, then erased by the nightly purge; the sealed entry stays until the journal retention below removes it — with its content, when that comes first. |
| Sealed decisions in the decision journal (fingerprints, codes, keyed pseudonyms — no content) | For the journal retention the workspace’s plan includes (see /pricing), or the period its contract sets, and at most as long as the workspace exists. Each night, the oldest sealed entries older than that period are removed, oldest first, behind a sealed checkpoint from which the rest of the chain can still be verified — and only entries already verified intact. None is removed sooner than the applicable law requires, nor while a litigation hold, an incident, a statement or a timestamp anchor still needs it. A sealed entry is never edited; all are deleted with the workspace. |
| Semantic cache entries (an answer, the words of its prompt and, when the data policy allows embeddings, an embedding of the prompt) — only when the workspace’s data policy collects answers, PII patterns redacted when it asks, the prompt’s words left out when it does not collect prompts or anonymises them, never in vault mode | Served for 7 days at most (a call may ask for less), then deleted by the next nightly purge. A data policy made stricter for the whole workspace, or removed, empties its cache at once. |
| Audit logs (who did what, when, from which IP address and browser) | 24 months, then deleted. When an account is erased, its rows lose the link to the person. |
| Alert receipts (which alert a workspace raised, where it was sent, who acknowledged it) | 24 months after it was raised — or acknowledged, when later — then deleted by the nightly purge. A critical or high-severity alert nobody acknowledged is kept until it is; a longer audit-trail period the applicable law requires, or an active litigation hold, keeps it longer. |
| In-app notifications (the member they are for, a title and a short text) | Once read, 90 days after they were sent; 12 months at most; then deleted by the nightly purge. |
| Agent runs (the goal given to an agent, its plan, its status and cost) | 12 months, then deleted by the nightly purge. |
| Guard findings on agents (the risk found, with a redacted excerpt of the evidence) | 24 months after the finding was last seen, then deleted by the nightly purge. |
| Loop-detection events | 6 months. |
| Webhook delivery records | 6 months. |
| Single sign-on (SAML) sessions | 6 months. |
| Users an organisation’s identity provider provisions (SCIM: e-mail address, name, the identity provider’s identifiers and attributes) | While they are active; 6 months after the identity provider deactivates them, then deleted by the nightly purge. |
| Support tickets and their messages | 24 months after the ticket is closed, unless a litigation hold names it. |
| Support access to a workspace (who asked for it, who decided, the reason, for how long) | 24 months after the access ended, then deleted by the nightly purge; what was sealed of it stays in the journals. |
| The assistant’s usage counters (counts only, no conversation) | 13 months. |
| Assistants connected to a workspace (remote MCP connector) | 13 months after their last use or their revocation. |
| Contact requests sent through the website’s form (e-mail address, name, company, message, the page it came from) — the copy we keep so that none is lost when our CRM (HubSpot) is unavailable, and send to it again | 13 months after it was sent, then deleted by the nightly purge, whether or not it reached HubSpot. In HubSpot, it is kept until you ask us to delete it. |
| Invitations to a workspace or an organisation (the invited e-mail address, the role offered, who sent it) | Until accepted or expired (7 days), then 30 days, then deleted by the nightly purge. The membership and the audit log keep what happened. |
| Answers kept for a human review of the grounding check (encrypted) | 14 days at most, erased once reviewed. |
| Red-team and model-change replay answers (encrypted) | 30 days. |
| Your cookie choices | In the audit log for 24 months when you are signed in; otherwise in the application log only. |
| Rate-limit counters (keyed by IP address or account) | The length of their window — one day at most. |
| Encrypted database backups | Our own nightly copies expire after 35 days; our database provider keeps its own daily backups for a shorter period. Data erased from the service disappears from the backups as they expire. |
| Invoices and payment records | Kept by Stripe and in our accounts for the period accounting law requires (ten years in France for accounting records). |
A workspace may shorten these windows (Settings › Retention, or its data policy). Only a longer window set in its data policy, a retention period the applicable law requires, or an active litigation hold keeps data longer.
8. Your rights
You have the right to access your data, to have it corrected or erased, to restrict its processing, to object to processing based on our legitimate interest, and to receive the data you gave us in a portable format (GDPR articles 15 to 21).
- Access and portability — in the dashboard, Account & Privacy › Download my data, or by e-mail. A workspace's data can be exported through the API (
GET /api/v1/export). - Erasure — Account & Privacy › Delete my account erases your account at once, with the workspaces you own (unless a litigation hold applies), or ask us by e-mail.
- Rectification — in your account, or by e-mail.
- Objection and restriction — by e-mail; the weekly point can be turned off in your notification preferences.
- Withdrawing consent — at any time, as easily as you gave it: . Withdrawing does not affect the processing that took place before.
Write to privacy@azothos.ai. We answer within one month, which may be extended by two months for complex requests (we will tell you). We may ask you to prove your identity. For data we process for a customer, we pass your request to it.
You can lodge a complaint with a supervisory authority — in France, the CNIL (Commission nationale de l'informatique et des libertés, 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, www.cnil.fr), or the authority of the EU country where you live or work.
10. Security
Every connection is encrypted (HTTPS only, with HSTS); the database is encrypted at rest by our provider and isolates each customer's data with row-level security; provider keys and other secrets are encrypted with AES-256-GCM; API keys are stored as keyed hashes (HMAC-SHA256 — keys created before that scheme stay as SHA-256 hashes until they are rotated); two-factor authentication is available to every account; sessions expire after 8 hours by default. Details in our Security Policy. If a breach is likely to put your rights at risk, we notify the CNIL within 72 hours and tell you without undue delay.
11. Children
Azoth OS is offered only to businesses and professionals, and is not directed at children under 16. We do not knowingly collect their data.
12. Changes
We update this notice when our processing changes, and change the date at the top. We tell account holders of a material change in the dashboard or by e-mail before it applies; a change to the cookies we use asks you again.
13. Contact
Data protection: privacy@azothos.ai
Security: security@azothos.ai
Beweird SAS · 128 rue La Boétie, 75008 Paris, France