Legal information
Sub-processors
Last updated: 2026-11-06
These are the providers that process personal data on behalf of Guimauve Digital SAS to run Allomi, as set out in the privacy policy and the data processing agreement. The facts below come from each provider's own documents (linked, read on 2026-11-06); where a document does not say, this page says so rather than assuming.
| Processor | Purpose | Data location | Transfer safeguard |
|---|---|---|---|
| Infomaniak | Hosting of the Service (OpenStack public cloud) | Switzerland (Geneva) | European Commission adequacy decision |
| OpenAI | Real-time voice (voice model) | United States | European Commission standard contractual clauses, built into the processing agreement |
| Twilio | Telephony, numbers, verification SMS | United States | EU–US Data Privacy Framework (certified provider); standard contractual clauses as a fallback |
| Stripe | Payments and invoicing | Ireland, EU (Stripe Payments Europe Ltd) and United States | EU–US Data Privacy Framework (certified provider); standard contractual clauses as a fallback |
| Resend | Email (sign-in links, receipts) | United States | EU–US Data Privacy Framework (certified provider); standard contractual clauses as a fallback |
| Anthropic (via TeamCode) | Assistant reasoning (Claude model, through the Publisher's TeamCode gateway) | United States | European Commission standard contractual clauses, built into the processing agreement |
| Cloudflare | Network, DNS, CDN and attack protection (allomi.ai, api., voice.) | Global network (edge servers); the origin stays in Switzerland | EU–US Data Privacy Framework (certified provider); standard contractual clauses as a fallback |
Details by provider
Infomaniak (hosting)
- What: the VM that runs the apps and the database, backups.
- Data: everything the Service stores (accounts, contacts, notes, call transcripts and summaries, logs without call content).
- Where: Switzerland. Infomaniak's terms state that data "is stored and hosted exclusively in datacenters located in Switzerland" that it owns (terms, article 15.1, GDPR page).
- Safeguard: no transfer outside Switzerland; Switzerland benefits from a European Commission adequacy decision (list of decisions). Infomaniak's DPA (GDPR art. 28 and Swiss FADP) is part of its terms; it relies on the EU standard contractual clauses for any transfer outside the EEA.
OpenAI (real-time voice)
- What: the voice model that speaks and listens during calls.
- Data: call audio and text, the assistant's instructions.
- Where: the United States by default. The API offers European data residency (processing and storage in Europe) only on request and with OpenAI's approval (data controls); no such configuration is documented for Allomi's account (to be confirmed by the Publisher): assume the United States.
- Safeguard: standard contractual clauses (module 2) in the OpenAI DPA; EEA and Swiss customers contract with OpenAI Ireland Ltd according to that page. Whether the Publisher's account is the Irish entity's is to be checked in its OpenAI account.
Twilio (telephony)
- What: phone numbers, the calls themselves, verification SMS.
- Data: phone numbers, call metadata, call audio carried on the network, SMS content.
- Where: the DPA does not name data-centre countries; the importer is Twilio Inc. in the United States, and carriers may receive data as telephony requires (Twilio DPA, sub-processors listed on twilio.com/legal/sub-processors).
- Safeguard: ranked in the DPA: EU–US Data Privacy Framework (Twilio Inc. is self-certified), then Twilio's binding corporate rules, then the standard contractual clauses (module 2).
Stripe (payments)
- What: subscriptions, cards, invoices, tax.
- Data: name, e-mail, billing address, tax id, card details (held by Stripe, never by Allomi), invoices.
- Where: EEA users contract with Stripe Payments Europe, Limited (Ireland); Stripe also processes in the United States and says it may transfer data worldwide, without naming regions for hosting (DPA, Privacy Center, sub-processors).
- Safeguard: Stripe, LLC is certified under the EU–US, Swiss–US and UK Data Privacy Framework; the standard contractual clauses (modules 1, 2 and 3) are the fallback (Data Transfers Addendum). Stripe is a controller for some purposes (fraud prevention, regulatory checks), as its DPA says.
Resend (e-mail)
- What: sign-in links, receipts and payment notices.
- Data: e-mail address, message content.
- Where: the United States. Resend states that all account data, including e-mail metadata and logs, is stored in the United States whatever sending region is chosen (GDPR page, regions).
- Safeguard: certified under the EU–US Data Privacy Framework and its UK extension since March 2025 (announcement); the standard contractual clauses are built into its DPA, pre-signed for every account.
Anthropic (assistant reasoning, through TeamCode)
- What: the Claude model that handles requests the voice model delegates (searches, missions, memory).
- Data: the text of the request, contact notes and call summaries needed for the task.
- Where: Anthropic's documents read for this page do not state the processing location; assume the United States. The requests pass through the TeamCode gateway operated by the Publisher (its hosting location is to be added by the Publisher).
- Safeguard: Anthropic's data processing addendum, including the standard contractual clauses and the UK and Swiss addenda, is incorporated in its commercial terms (how it applies). Anthropic does not train its models on data sent through its commercial products.
Cloudflare (network)
- What: DNS, CDN and attack protection in front of the site and the API.
- Data: IP addresses and the content of requests in transit to allomi.ai and api.allomi.ai (voice traffic from Twilio goes directly to the origin).
- Where: Cloudflare's global network; requests are handled at the nearest edge location. Regional controls exist (Data Localization Suite) but are a paid option that, to our knowledge, Allomi has not enabled.
- Safeguard: EU–US, Swiss–US and UK Data Privacy Framework certification, with the standard contractual clauses (modules 2 and 3) as a fallback (DPA, GDPR FAQ).
Changes
We tell account owners by e-mail at least 30 days before adding or replacing a sub-processor that handles call content, so you can object or close your account (see the DPA). Questions: [email protected].