Extracted from Schedule 3 of the A1 Voice Data Processing Agreement. For the full DPA see /dpa.
The Sub-processors listed below are authorised at the date of this DPA. Each one processes Customer Personal Data on behalf of the Processor under a written contract imposing data-protection obligations no less protective than this DPA, except the telephony and messaging Sub-processor (Telnyx), which contracts on its own standard terms and is also an independent controller for the purposes its row states. Updates are made under clause 4.4.
| Sub-processor | Purpose | Region of processing |
|---|---|---|
| Amazon Web Services (AWS) | Hosting, compute, storage, networking — including the call-handling pipeline (WebRTC, audio storage, transcripts, dashboard, database) | UK (eu-west-2, London) — all infrastructure pinned to AWS's London region |
| Google (Gemini API via Vertex AI) | Large-language-model inference for call handling | EU multi-region (eu) — pinned via the Vertex AI EU multi-region endpoint (aiplatform.eu.rep.googleapis.com); auth via service-account ADC. Live on both staging and production since 2026-09-08. Requests are served from a location within the European Union; the multi-region does not extend outside the EEA. Previous pins: europe-west8 (Milan) from 2026-05-28, and europe-west2 (London) from 2026-05-11. A second endpoint also ran, and this row did not disclose it at the time: from 2026-05-30 until 2026-09-08 a latency backup leg at europe-west4 (Netherlands) was live alongside the Milan primary, engaging on the slow tail of turns; it was retired on 2026-09-08 with the rest of the hedge. Both were EU endpoints, so processing stayed inside the EEA throughout and the clause 5.2 residency commitment was met — what was incomplete was this Schedule, which clause 5.4 makes the statement of the regions in which Sub-processors process Customer Personal Data. The omission and its correction are recorded in full in the Processor's Transfer Impact Assessment (Appendix C, v0.4.1), which is shared with Controllers on request. The 2026-09-08 move was compelled by Google's retirement of the Gemini 2.5 series on 2026-10-16 — its replacement generation is not served from any single-region endpoint — and NOT by a relaxation of residency: the alternative global endpoint was rejected precisely because it would route outside the EEA. Where a fail-over outside the UK / EEA is exceptionally required, UK IDTA / SCCs apply. |
| Telnyx (Telnyx LLC and its affiliates) | Telephony and messaging: carries inbound telephone calls to the practice's A1 Voice number and the Services' replies (call audio in transit), presents the number a call is made from, connects a caller to the practice's own line when a live transfer is used, sends text messages the Services compose (appointment confirmations and change notices, links, acknowledgements to callers, and messages taken for the practice, which can include a caller's name, number and reason for calling), and supplies the practice's telephone number. Call recordings and transcripts are made and stored by the Processor on its own infrastructure, not with Telnyx. Telnyx keeps records of each call and message (numbers, times, durations, status). | Not region-pinned. The Services address Telnyx's EU API host (api.telnyx.eu). Telnyx's Data Processing Addendum states that its primary processing facilities are in the United States. Its data-residency documentation, written for its Voice AI products, says a European anchorsite influences but does not guarantee where voice is processed, and that text messages leave through carriers whose handling cannot be constrained to a region; we have found no Telnyx documentation stating whether the chosen site is guaranteed for plain call streaming, which is what the Services use. Telnyx stores its records of the Processor's calls and messages (call and message detail records) in Germany; that setting governs where those records are kept, not where calls and messages are carried. Calls to the Processor's numbers are handled at Telnyx's London site (its "anchorsite"); as with the Voice AI statement above, this is not treated as a guarantee of where calls are processed. Treated as a transfer outside the UK / EEA. Safeguards: Telnyx's Data Processing Addendum incorporates the EU SCCs and the UK International Data Transfer Addendum, and states Telnyx's certification under the UK Extension to the EU-U.S. Data Privacy Framework. Telnyx is not only a processor. Its Data Processing Addendum makes it an independent controller of (i) the records it keeps to route, secure and bill calls and messages — telephone numbers (including the number a call is made from), call and message detail records, and the time, duration and status of each — and (ii) call and message content that it de-identifies, pseudonymises or aggregates, and then uses to improve its own services, including training models. Otherwise it handles call audio and message content as a processor. The public telephone network and the caller's and recipient's own telephone providers carry each call and message before and after Telnyx. |
| OpenRouter (where configured) | Alternative LLM routing for some agent roles | Not currently configured in the production profile; this row is retained for transparency in case it is re-enabled. If re-enabled, OpenRouter would route to the underlying provider it judges best (no region pin); UK IDTA / SCCs would apply, and the Processor would re-notify Controllers per clause 4.4.4. |
Notes:
https://voice.a1ergo.tech/privacy § 4) lists the same Sub-processors. Schedule 3 and the Privacy Policy stay in lock-step — when one moves, the other moves.