What are the sovereignty profiles?

Every organisation runs on exactly one profile — AU Sovereign, Global or UK Sovereign — chosen when the organisation is created and applied to everyone in it. It can’t be switched in place. Clinical records are stored in Australia on AU Sovereign and Global; UK Sovereign stores them in London.

The profile decides one thing: where audio and transcripts are processed. It doesn’t change where the record is kept.

AU Sovereign

For organisations in Australia and New Zealand. On AU Sovereign, everything stays in Australia: transcription and note drafting run on vetted Australian services over private links inside Akoua’s cloud — disclosed on every note, under the consent your organisation gives for that processing. Ordinary consent to record is a separate authority, given for each consultation. Speaker identity, including any voice profile you record, is matched only on Akoua’s own infrastructure and never sent to a provider. Nothing is processed outside Australia without a separate, explicit request for that specific session.

All processing in Australia — vetted Australian services over private links; speaker identity only ever on Akoua infrastructure.
Clinical record stored in Sydney.
Anything beyond that pathway — offshore above all — only by explicit per-session consent.
Audio deleted by default.

Global

For organisations outside Australia and New Zealand once rest-of-world access opens; it is currently coming soon and public account creation is not available. On this profile, vetted global managed providers process audio and transcripts by default under your organisation’s consent. Akoua stores the clinical record in Australia. No provider uses that data to train its models.

Clinical record stored in Sydney, Australia.
Inference by vetted global providers.
Organisation-level provider consent.
Audio deleted by default.

Storage is not processing. Storage in Sydney does not make Global processing Australian. On Global, inference happens with those vetted providers; the Sydney residency applies to the stored record, not to where the audio was processed.

What’s the same either way

Both profiles keep the parts that aren’t negotiable: the audio Akoua holds is deleted by default, clinical data is never used to train models, and every access is written to an append-only audit log. On Global, Akoua does not yet collect independent deletion proof from the third-party processors — see what happens to consult audio. Akoua is a documentation aid, not a diagnostic device — it makes no clinical inferences, and every draft needs your explicit review and confirmation, on either profile.

The profile is chosen at sign-up and applied to everyone in the organisation, not per clinician. If you’re not sure which one you’re on, ask whoever set up your organisation’s account, or get in touch.

New Zealand organisations run AU Sovereign: audio and transcripts are processed in Australia and the clinical record is stored in Sydney — across the Tasman, and nowhere further without explicit acceptance for that session. NZ-resident processing is on the roadmap.

UK Sovereign

The United Kingdom has its own live region: on UK Sovereign, the clinical record is stored in the United Kingdom (London), and transcription and note drafting run in the European Union for every consult — transcription on Deepgram’s EU regional service, note drafting on Amazon Bedrock, invoked from AWS London and served in AWS’s EU regions — under the UK’s adequacy regulations for the EEA. The service is open to United Kingdom organisations — Akoua in the UK has the detail. The UK privacy notice, Data Processing Schedule and sub-processor list are published. Everything on this page about storage in Australia describes the AU Sovereign and Global profiles.

More detail on the split between storage and processing is in where your data is stored and processed, and the whole picture is on privacy by design.