Privacy policy v1.1 · in effect Updated 27 July 2026 Privacy Act 1988 (Cth)
This policy reflects how aurii handles information today. It follows the Australian Privacy Principles under the Privacy Act 1988 (Cth). We keep it accurate as the service develops, and version and date any change; the stamps above always show the version in effect. Questions are welcome: [email protected].
Who we are.
aurii is built for specialists in Australian private hospitals. Speak the consult once. aurii drafts the note, the letters and the discharge, and captures the billing for you to sign.
In this policy, “aurii”, “we”, “us” and “our” mean Aurii Pty Ltd (ABN 52 697 638 538), which operates the aurii platform. “You” means the people whose personal information we handle: the specialists and hospital staff who use aurii, and the patients whose clinical information passes through it.
This policy explains what we collect, why, where it lives, who can access it, and your rights under the Australian Privacy Principles (APPs) in the Privacy Act 1988 (Cth). For clinical (health) information we also follow the obligations that attach to health records in Australia.
What we collect, in three groups.
We collect only what aurii needs to do its job:
- Accounts Account & practice information Names, work emails, provider numbers, specialty, hospital affiliations and role of the clinicians and staff who use aurii, supplied by you or your hospital at account creation.
- Clinical Clinical information you create The consult audio, the transcript, and the documents aurii drafts from it (notes, letters and discharge summaries), plus the private health fund billing items you record and the patient identifiers attached to them.
- Operational Operational & device information The records a clinical system must keep: sign-in events, the device and app version in use, actions taken on a record, and diagnostic logs needed to keep the service safe and available.
We do not buy personal information from data brokers, and aurii is not advertising-funded. We do not run third-party advertising or tracking pixels on the clinical application.
Clinical data, held to a higher standard.
Patient health information is the consult audio, the transcripts, and the documents drafted from them. We hold it to a higher standard than anything else.
Consult audio is captured and transcribed in Australia, and the documents drafted from it are stored and encrypted here. Drafting is the one step that crosses the border: the transcript goes to our AI processor overseas and the draft comes back to Australia for a clinician to check. Data residency, below, sets that out in full.
Audio serves only to draft your documentation, and its retention follows the configuration agreed with your hospital. Every draft is created for a clinician to check.
aurii drafts. The specialist decides. No clinical output is final, sent, or billed until a doctor has reviewed and signed it. aurii does not make autonomous clinical decisions, and it is not a substitute for a clinician’s judgement.
How we use it.
We use that information for defined, clinically necessary purposes:
- Provide To provide the service To transcribe the consult, draft the note, letters and discharge summary, and record the private health fund billing for your review and signature.
- Protect To keep it safe & accountable To authenticate users, prevent misuse, and maintain the tamper-evident record of who did what and when.
- Improve To support and improve reliability To diagnose faults and keep aurii available and accurate. We do not use your patients’ clinical information to train general-purpose AI models for unrelated use.
We do not use clinical information for marketing, and we do not sell personal or health information to anyone, ever.
Data residency, and the one step that leaves.
Your data is stored in Australia. The primary region is Sydney, replicated to a backup region in Melbourne. Consult audio, transcripts and the documents drafted from them are transcribed, stored, backed up and encrypted within Australian borders.
One step crosses the border. To draft the note, the letters and the discharge summary, the consult transcript is disclosed to Anthropic, the provider of the Claude models aurii uses, and processed on Anthropic infrastructure outside Australia, including in the United States. That is a cross-border disclosure under Australian Privacy Principle 8, and it is the only one we make.
Anthropic handles that content under commercial terms and a data processing agreement that incorporate the Standard Contractual Clauses, which bind it to protect the information in a way substantially consistent with the Australian Privacy Principles. It does not train its models on your content. The draft returns to Australia, where it is stored, and nothing clinical is final until a specialist has signed it.
Every other sub-processor listed below holds your data in Australia, under the residency and confidentiality terms described there.
Encrypted, in transit and at rest.
Clinical information is encrypted on every hop in transit, and encrypted at rest with AES-256 in the Australian regions of Microsoft Azure. Those storage keys are managed by the platform today. Customer-managed keys, where a separate key for each class of data is held and rotated by us in Azure Key Vault, are planned and not yet in effect, so we do not claim them here.
The highest-risk fields, among them Medicare numbers, prescriber credentials and multi-factor secrets, carry a second layer of encryption applied by the application itself, with keys held in Azure Key Vault in Australia. Every value is stamped with the key version it was written under, so rotation stays auditable.
Each practice’s data is isolated from every other tenant. Ask us to purge your data and it is destroyed, not just hidden: removed from live systems, with encrypted backups ageing out on a defined cycle.
Sharing, a short list.
Only a short list of parties can access your data, each under contract and only to run aurii. We use sub-processors in three areas:
- Cloud In-region cloud infrastructure An Australian cloud region (Sydney primary, Melbourne backup) hosts the platform and your data, stored and backed up in Australia.
- Transcription In-region transcription Speech-to-text that converts the spoken consult into a transcript, performed in Australia under contract and bound to the same residency and confidentiality terms.
- Drafting AI drafting, overseas Anthropic turns the transcript into the draft note, letters and discharge summary using its Claude models, processed outside Australia, including in the United States, under the cross-border terms set out in Data residency above. It is bound by contract to confidentiality terms, it does not train its models on your content, and every draft returns to a clinician for review and signature.
We share clinical information beyond these sub-processors only where you direct it (for example, a letter you sign and send to a GP), or where we are required to by Australian law. AI drafting is the only disclosure of your data to a recipient outside Australia, and we do not disclose it overseas for any other purpose.
Retention & the seven-year audit.
Clinical records carry legal retention obligations. Every document and action is written to an append-only, tamper-evident audit, a record that can be added to but not silently altered or deleted, and kept for seven years.
We retain clinical information for as long as your hospital’s record-keeping obligations require, under the agreement we hold with your organisation. Account information is kept while your account is active, then for the period needed to meet legal and audit obligations, and disposed of securely.
Your rights, under the APPs.
Under the APPs you have real rights over your personal information. Whether you are a clinician using aurii or a patient whose information passes through it, these include:
- Access Ask what personal information we hold about you and request a copy.
- Correction Ask us to correct information that is inaccurate, out of date or incomplete.
- Complaint Raise a privacy concern with us at [email protected] and we will respond. If you are not satisfied with how we handle it, escalate to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au or on 1300 363 992.
Because aurii holds patient information on behalf of hospitals and specialists, a patient request usually flows through the treating clinician or hospital that controls the record. Where that applies, we will help your hospital respond. To make any request, email [email protected].
Security, in brief.
Clinical information is encrypted in transit and at rest, with the highest-risk fields carrying the second application-level layer described above, keyed from Australian Key Vault. Access is authenticated and least-privilege, and each practice’s data is isolated from every other tenant. Every action is written to the tamper-evident audit above.
We keep the service patched and monitored, and nothing clinical is final until a doctor has signed it. No system is perfectly secure. But your records are stored in Australia, encrypted and isolated to your practice, with a permanent record of everything, and AI drafting is the only step that leaves the country. Ask us to purge them and they are destroyed for good.
Questions, answered personally.
For any privacy question, whether access, correction, a concern, or how aurii would handle data in your hospital, reach the team directly. We answer privacy enquiries personally.
Prefer to talk it through? Talk to the team, or read how aurii protects clinical data on the security page.
Email us about privacyThis policy sits alongside our terms. If anything here is unclear, email [email protected] and we will explain it.