United Kingdom

Sub-processor List

Incorporated into the Data Processing Schedule (§7) · Version 1.10 — 4 September 2026

Every external processing hop the service makes is recorded immutably and is disclosable to your practice in-product — this list cannot silently drift from what actually runs. Organisations in Australia and New Zealand run a separate deployment with its own geography — that list is at Australian sub-processors. Practices receive advance notice of changes per the Schedule and may object on reasonable data-protection grounds.

Automated transcription and note drafting for the United Kingdom service run on the two clinical-data sub-processors below as the ordinary route for every consult: transcription on Deepgram's EU regional service, and note drafting on Amazon Bedrock, invoked from AWS London (eu-west-2) and served in Amazon Web Services' European Union regions under its EU inference profile. Akoua is the processor, and the record itself stays in the United Kingdom. AWS supplies the underlying London infrastructure.

Clinical Data sub-processors

Sub-processorPurposeProcessing locationSafeguard
Amazon Web Services (AWS)Cloud infrastructure: storage, database, compute for the UK deploymentUnited Kingdom (eu-west-2, London)Processing in-country; AWS DPA
Deepgram, Inc.Automated speech-to-text of consult audio — the transcription route for every consultEuropean Union (Frankfurt, Germany — Deepgram EU regional service)UK→EU under UK adequacy for the EEA; zero-retention configuration and model-improvement opt-out (live configuration); anonymous diarisation only; Deepgram DPA
Amazon Web Services (AWS) — Amazon BedrockAutomated drafting of clinical documentation from the transcript, for the clinician's review — the note-drafting route for every consultInvoked from the United Kingdom (eu-west-2, London); served in Amazon Web Services' European Union regions under the EU cross-region inference profileUK→EU under UK adequacy for the EEA; Bedrock does not store prompts or outputs or use them to train models under AWS's published commitments; AWS DPA

Practice-management integrations (optional; only if your practice connects one)

Cliniko is enabled for the United Kingdom deployment; Nookal is currently disabled, and listed here ahead of any activation. Neither engages unless your practice connects it, and each receives only practitioner and appointment identifiers, one linked patient's minimum demographics, and a confirmed note or letter when the clinician explicitly sends it — never your patient list, and never anything you have not confirmed. How connecting works. The service is open to United Kingdom organisations.

Connecting one writes into your own practice-management account. The destination is that account — and Akoua checks it in code against the regions approved for this deployment, so an out-of-region account cannot be connected. That is what keeps a confirmed note you choose to send inside the same residency envelope as the rest of this list, and why §8.3 of the Schedule still holds.
Sub-processorPurposeProcessing locationSafeguard
ClinikoPractitioner and appointment identifiers, one linked patient's minimum demographics, and a confirmed note or letter when the clinician explicitly sends itUnited Kingdom or the European Union — your practice's own Cliniko account, which must sit in a region approved for the United Kingdom deploymentYour practice's own system under its own agreement with the vendor; approved-region allowlist enforced in code; only what the clinician explicitly sends
NookalSame as Cliniko. Integration currently disabled; listed for completeness ahead of any activation.United Kingdom or the European Union — your practice's own Nookal account, which must sit in a region approved for the United Kingdom deploymentYour practice's own system under its own agreement with the vendor; approved-region allowlist enforced in code; only what the clinician explicitly sends

Account Data sub-processors (business operations; no Clinical Data)

Sub-processorPurposeProcessing locationSafeguard
StripeSubscription billing and payment processingStripe's standard locations (US/EU)Stripe DPA and its transfer mechanisms
CloudflareMarketing site hosting; signup bot-protection (Turnstile)Global edgeNo Clinical Data touches Cloudflare — the application hosts are deliberately not proxied
Amazon Web Services (AWS) — Simple Email ServiceTransactional email (sign-in codes, billing notices)United Kingdom (eu-west-2, London)Processing in-country; AWS DPA
AppleApp Store purchases and App Attest device attestation for the iOS and macOS appsApple's standard locationsApple's terms and its transfer mechanisms
GoogleGoogle Play billing and Play Integrity attestation for the Android appGoogle's standard locationsGoogle's terms and its transfer mechanisms

Questions about this list: privacy@akoua.ai.