Skip to main content
azothos
← Back to home

Legal

Data Processing Agreement

GDPR Article 28 · Effective: 1 May 2026 · Last updated: 13 November 2026

This Data Processing Agreement (“DPA”) sets out how Beweird SAS processes personal data on behalf of a Customer in connection with providing the Service. For a signed DPA, contact legal@azothos.ai.

1. Definitions

  • “Controller” — the Customer, who determines the purposes and means of processing.
  • “Processor” — Beweird SAS, who processes personal data on behalf of the Controller.
  • “Personal Data” — any information relating to an identified or identifiable natural person that the Customer's workspaces send through the Service, or that the Service records about them, as described in section 2.
  • “GDPR” — Regulation (EU) 2016/679 of the European Parliament and of the Council.

2. Subject matter and nature of processing

Purpose. Governing, routing, recording and proving the AI calls a customer’s workspace sends through Azoth, as the customer instructs (the Data Processing Agreement).

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.

Nature. Collection, recording, storage, consultation, transmission to the model providers the Customer chooses, pseudonymisation and erasure, for the duration of the Service.

Special categories. Prompts, answers and images are free text: they may contain special categories of personal data (GDPR article 9) if the Customer sends them. Azoth does not seek such data; the Customer decides whether to send it. No content is kept unless the workspace's data policy collects it, and none in vault mode.

Accounts, sign-in, billing and the Service's own e-mails are processed by Beweird SAS as a controller, as described in the Privacy Notice, not under this DPA.

3. Processor obligations

Azoth shall:

  • Process personal data only on documented instructions from the Controller: this DPA, the Terms of Service, and the Controller's configuration of the Service (its data policy, retention, providers and rules).
  • Ensure persons authorized to process personal data are bound by confidentiality.
  • Implement technical and organizational measures as described in our Security Policy.
  • Assist the Controller in responding to data subject rights requests.
  • Delete or return all personal data upon termination of the Service.
  • Make available to the Controller all information necessary to demonstrate compliance.

4. Sub-processors

Current sub-processors — list of 13 November 2026:

  • Supabase Inc. — Database, authentication and file storage · European Union (Frankfurt, Germany)
  • Vercel Inc. — Hosting: the application runs in the EU (Frankfurt), behind a worldwide edge network · European Union (Frankfurt) for the application; edge locations worldwide
  • Upstash, Inc. — Rate limiting and short-lived caches · European Union (Frankfurt)
  • Brevo (Sendinblue SAS) — Sending the service’s e-mails (confirmations, invitations, alerts, summaries, receipts) · European Union (France)
  • Resend, Inc. — Fallback e-mail delivery when Brevo fails. Only when it is configured and Brevo cannot send · United States
  • Functional Software, Inc. (Sentry) — Error tracking; and, only with your consent, session replay of the website and dashboard · European Union (Germany)
  • 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 · United States
  • Mistral AI SAS — The onboarding trial key: a new workspace’s first calls, answered with Azoth’s key; and the workspaces that route calls to Mistral · European Union (France)
  • OpenAI, L.L.C. — 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 · United States
  • Google LLC (Gemini) — 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 · European Union and United States (to verify)
  • Hugging Face, Inc. — 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 · United States (to verify)
  • Staan (Qwant, European Search Perspective) — Web search for the agents’ web_search tool, with Azoth’s key. When its key is set · European Union (EU data centres, as Staan states it — to verify)
  • Serper.dev — 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 · United States (to verify)
  • The model providers a customer chooses — 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 · 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 · United States
  • Backup object storage (S3-compatible, EU bucket) — Keeping the encrypted nightly backups · European Union

The full list, with the data each receives and its transfer safeguard, is available from legal@azothos.ai.

Changes. We tell the owners and admins of every workspace by e-mail of each change to this list, at least 30 days before a new or replacement sub-processor takes effect. A Customer may object on reasonable data-protection grounds until that day, by writing to legal@azothos.ai; we then look for a solution together, such as not sending its data to that sub-processor.

  • 13 November 2026 — effective 13 November 2026. Named on the list, already engaged: Google LLC (Gemini), Hugging Face, Inc., Staan (Qwant, European Search Perspective), Serper.dev — Named on their own rows: already engaged for processing Azoth does with its own keys (image reading in Inventory Object, the agents’ web search) and described in the full sub-processor list, they were listed only inside « the model providers a customer chooses ».

5. International transfers

Customer data is stored in the European Union (Supabase, Frankfurt) and the application runs in the European Union (Vercel, Frankfurt). Where personal data is transferred outside the EEA — to a sub-processor that is a US company, or to a model provider outside the EEA that the Customer chooses — Azoth relies on the Standard Contractual Clauses approved by the European Commission (Decision 2021/914).

6. Data subject rights

Azoth will assist the Controller in fulfilling data subject rights within the timeframes required by GDPR. Data portability requests are fulfilled via GET /api/v1/export (JSON or NDJSON). Erasure requests are processed within 30 days.

7. Security incidents

In the event of a personal data breach, Azoth will notify the Controller without undue delay and within 72 hours of becoming aware of the breach, providing information about the nature of the breach, categories and approximate number of records affected, likely consequences, and measures taken.

8. Contact

Data protection contact: privacy@azothos.ai
For signed enterprise DPAs: legal@azothos.ai

© 2026 Beweird SAS
Mentions légalesPrivacyCookiesTermsSecurityAccessibilityDPA