Compliance
Records of Processing Activities
GDPR article 30 · Controller: Beweird SAS, 128 rue La Boétie, 75008 Paris, France · Data protection contact: privacy@azothos.aiLast updated: 17 November 2026 · Review cycle: quarterly, and upon any material change
How to read this document
Each record describes one processing activity: its purpose, legal basis, the people and data concerned, the recipients, how long the data is kept, and the transfers outside the European Economic Area. Activities marked controller are those Beweird SAS decides on (article 30(1)); the activity marked processor is carried out for customers, on their instructions, under the Data Processing Agreement (article 30(2)). The same facts are published in the Privacy Notice.
ACT-01Accounts and sign-in
| Role | Controller |
|---|---|
| Purpose | Creating your account, signing you in, securing it with two-factor authentication, and recording each sign-in. |
| Legal basis | Contract (GDPR art. 6(1)(b)). Sign-in events: our legitimate interest in securing accounts (art. 6(1)(f)). |
| Data subjects | People who create an account or accept an invitation; members an organisation provisions through its identity provider. |
| Personal data | 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). |
| Recipients | Supabase Inc.; Vercel Inc.; Brevo (Sendinblue SAS); Cloudflare, Inc. (Turnstile); Google |
| Retention | 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. 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. |
| Transfers | 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; Cloudflare, Inc. (Turnstile) — EU Standard Contractual Clauses (Commission Decision 2021/914), in the vendor’s data processing agreement |
ACT-02Acceptance of the Terms
| Role | Controller |
|---|---|
| Purpose | 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). |
| Legal basis | Our legitimate interest in being able to prove the contract (art. 6(1)(f)). |
| Data subjects | Account holders. |
| Personal data | 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. |
| Recipients | Supabase Inc. |
| Retention | 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. |
| Transfers | 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 |
ACT-03Providing the service to a workspace
| Role | Processor (for the customer, the controller) |
|---|---|
| Purpose | Governing, routing, recording and proving the AI calls a customer’s workspace sends through Azoth, as the customer instructs (the Data Processing Agreement). |
| Legal basis | The customer’s, as controller — Azoth processes this data only on its documented instructions (GDPR art. 28). |
| Data subjects | The customer’s members, and the people its AI calls are made for or are about. |
| Personal data | 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. |
| Recipients | Supabase Inc.; Vercel Inc.; Upstash, Inc.; Brevo (Sendinblue SAS); Resend, Inc.; Functional Software, Inc. (Sentry); Anthropic, PBC; Mistral AI SAS; OpenAI, L.L.C.; Google LLC (Gemini); Hugging Face, Inc.; Staan (Qwant, European Search Perspective); Serper.dev; The model providers a customer chooses; GitHub, Inc.; Backup object storage (S3-compatible, EU bucket) |
| Retention | 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. 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. 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. Loop-detection events: 6 months. Webhook delivery records: 6 months. 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. 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. Assistants connected to a workspace (remote MCP connector): 13 months after their last use or their revocation. |
| Transfers | 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; 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; 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 |
ACT-04Billing
| Role | Controller |
|---|---|
| Purpose | Charging paid plans, managing subscriptions and issuing invoices. |
| Legal basis | Contract (art. 6(1)(b)); keeping invoices: legal obligation (art. 6(1)(c), accounting and tax law). |
| Data subjects | Customers’ billing contacts. |
| Personal data | 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. |
| Recipients | Stripe; Supabase Inc. |
| Retention | Invoices and payment records: Kept by Stripe and in our accounts for the period accounting law requires (ten years in France for accounting records). |
| Transfers | Stripe — EU Standard Contractual Clauses (Commission Decision 2021/914), in the vendor’s data processing agreement; 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 |
ACT-05Service e-mails
| Role | Controller |
|---|---|
| Purpose | 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. |
| Legal basis | 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. |
| Data subjects | Account holders. |
| Personal data | E-mail address, name, and the content of the e-mail. |
| Recipients | Brevo (Sendinblue SAS); Resend, Inc. |
| Retention | Azoth keeps no copy of a sent e-mail; the sending provider keeps its delivery logs. |
| Transfers | Resend, Inc. — EU Standard Contractual Clauses (Commission Decision 2021/914), in the vendor’s data processing agreement |
ACT-06Security and abuse prevention
| Role | Controller |
|---|---|
| Purpose | 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. |
| Legal basis | Our legitimate interest in securing the service and the accounts (art. 6(1)(f)), and the duty to secure processing (art. 32). |
| Data subjects | Visitors and account holders. |
| Personal data | IP address, browser, request identifiers, rate-limit counters, bot-check signals, audit-log entries, error reports (without IP address, cookies or user identity). |
| Recipients | Vercel Inc.; Upstash, Inc.; Cloudflare, Inc. (Turnstile); Functional Software, Inc. (Sentry); Supabase Inc. |
| Retention | Rate-limit counters (keyed by IP address or account): The length of their window — one day at most. 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. |
| Transfers | 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; Cloudflare, Inc. (Turnstile) — 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; 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 |
ACT-07Support
| Role | Controller |
|---|---|
| Purpose | Answering your support requests. |
| Legal basis | Contract (art. 6(1)(b)). |
| Data subjects | People who contact support. |
| Personal data | 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. |
| Recipients | Supabase Inc.; Brevo (Sendinblue SAS) |
| Retention | 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. |
| Transfers | 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 |
ACT-08In-app assistant
| Role | Controller |
|---|---|
| Purpose | Answering the questions you ask the assistant about your workspace, with an AI model. |
| Legal basis | Contract (art. 6(1)(b)) — a feature of the service you choose to use. |
| Data subjects | Members who use the assistant. |
| Personal data | 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. |
| Recipients | Anthropic, PBC |
| Retention | The assistant’s usage counters (counts only, no conversation): 13 months. |
| Transfers | Anthropic, PBC — EU Standard Contractual Clauses (Commission Decision 2021/914), in the vendor’s data processing agreement |
ACT-09Product analytics and session replay
| Role | Controller |
|---|---|
| Purpose | Understanding how the website and the dashboard are used, and fixing bugs. |
| Legal basis | Your consent (art. 6(1)(a); ePrivacy art. 5(3)), which you can withdraw at any time. |
| Data subjects | Visitors and members who accept it. |
| Personal data | 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. |
| Recipients | PostHog, Inc.; Functional Software, Inc. (Sentry) |
| Retention | Kept by PostHog and Sentry under the retention settings of our accounts with them; the identifier cookie is removed when you withdraw. |
| Transfers | PostHog, Inc. — PostHog is a US company: 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 |
ACT-10Contact requests, support chat and marketing
| Role | Controller |
|---|---|
| Purpose | Answering the requests you send from the website, the support chat, and following the visits of people who accept the marketing cookies. |
| Legal basis | 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)). |
| Data subjects | Prospects, visitors who write to us or accept the marketing cookies. |
| Personal data | 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. |
| Recipients | HubSpot, Inc. |
| Retention | What you send through the website’s form: a copy kept by us for 13 months, then deleted, so that a request is not lost when HubSpot is unavailable; in HubSpot, until you ask us to delete it. The cookies are removed when you withdraw. |
| Transfers | HubSpot, Inc. — HubSpot is a US company: EU Standard Contractual Clauses (Commission Decision 2021/914), in the vendor’s data processing agreement |
ACT-11Consent records
| Role | Controller |
|---|---|
| Purpose | Being able to show what you accepted or refused (GDPR art. 7(1)). |
| Legal basis | Legal obligation (art. 6(1)(c), art. 7(1)). |
| Data subjects | Visitors and members who answer the cookie choice. |
| Personal data | The purposes accepted or refused, the policy version, the time, your IP address, browser and, when signed in, your account. |
| Recipients | Supabase Inc.; Vercel Inc. |
| Retention | Your cookie choices: In the audit log for 24 months when you are signed in; otherwise in the application log only. |
| Transfers | 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 |
ACT-12Backups
| Role | Controller |
|---|---|
| Purpose | Restoring the service after an incident. |
| Legal basis | Our legitimate interest in the continuity of the service (art. 6(1)(f)) and the duty to secure processing (art. 32). |
| Data subjects | Everyone whose data the database holds. |
| Personal data | An encrypted copy of the whole database. |
| Recipients | GitHub, Inc.; Backup object storage (S3-compatible, EU bucket); Supabase Inc. |
| Retention | 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. |
| Transfers | GitHub, Inc. — EU Standard Contractual Clauses (Commission Decision 2021/914), in the vendor’s data processing agreement; 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 |
Technical and organisational measures
- Encryption in transit — HTTPS only on every endpoint, HSTS with a long max-age.
- Encryption at rest — the database is encrypted at rest by Supabase; provider keys and other secrets are encrypted by the application (AES-256-GCM); backups are encrypted (AES-256) before they leave the backup job.
- Access control — row-level security on every customer table; roles (owner, admin, member and read-only roles) enforced by the application and the database; two-factor authentication available to every account; sessions expire after 8 hours by default.
- API keys — stored as keyed hashes (HMAC-SHA256); keys created before that scheme remain SHA-256 hashes until rotated.
- Accountability — an append-only audit log of significant actions (actor, IP address, browser); each customer's decisions sealed in a hash-chained journal anyone can verify; every access by Azoth staff to production sealed in a platform journal, and to a customer's data only through an access its owner grants.
- Data minimisation — call content is kept only when the customer's data policy collects it, with PII patterns redacted, never in vault mode; error reports carry no IP address, cookie or user identity.
- Retention — a nightly purge (
purge_expired_data_batch) applies the windows above; customers can shorten them. The nightly retention run also removes each workspace's oldest sealed decisions past its plan's journal retention, behind a sealed checkpoint, so the rest of the chain still verifies. - Continuity — encrypted nightly backups, a restore drilled every month.
- Breach handling — error tracking and alerting; a documented breach procedure, with notification to the CNIL within 72 hours where required (article 33) and to customers without undue delay.
Data subject rights
- Access (art. 15) — the dashboard's Account & Privacy › Download my data (
GET /api/v1/me), or by e-mail. - Portability (art. 20) — a workspace's data through
GET /api/v1/export(JSON or NDJSON). - Erasure (art. 17) — Account & Privacy › Delete my account (
DELETE /api/v1/me): immediate, with the workspaces the person owns, unless a litigation hold applies. - Rectification (art. 16) — in the account, or by e-mail.
- Restriction and objection (art. 18, 21) — by e-mail to privacy@azothos.ai; answered within one month.
Supervisory authority
Beweird SAS is established in France: its lead supervisory authority is the CNIL (Commission nationale de l'informatique et des libertés). A person may also complain to the authority of the EU country where they live or work.