The Australian Privacy Principles

RequiresManage personal information openly, under a current privacy policy.

• The Privacy Policy is versioned and dated at each change.
• Privacy enquiries go to hello@aurii.com.au.

RequiresOffer anonymity where that is lawful and practicable.

• Patients are identified. The clinical and billing record requires it by law.
• General enquiries need no account, only the address you write from.

RequiresCollect only what is reasonably necessary, and sensitive information with consent.

• Collection covers the consult audio, the transcript, the drafts, patient identifiers, billing items, and documents a clinician uploads or photographs.
• Health information is handled as sensitive information.

RequiresAssess unsolicited personal information; destroy or de-identify what you could not have collected.

• Uploaded context files attach to the patient record they were provided for, and feed only the background sections of a draft.
• Deletion runs on request. What is deleted and what the practice keeps.

RequiresTell people what you collect, why, and who you share it with.

• What is collected, why, where it is held and every sub-processor are stated in the Privacy Policy.
• Patients are told through the clinician or hospital that controls the record.

RequiresUse or disclose information only for the purpose it was collected, or a directly related one.

• Clinical information is used to transcribe the consult, draft the documentation and record billing for the clinician to review and sign.
• Disclosure happens where the clinician directs it, such as a signed letter to a GP, and where Australian law requires it. Clinical information is not sold.

RequiresDo not use personal information for direct marketing without expectation and an opt-out.

• Patients' clinical information is not used for marketing.
• The clinical application carries no third-party advertising or tracking.

RequiresTake reasonable steps to ensure a recipient of disclosed information handles it consistently with the APPs.

• Every sub-processor is engaged under a data processing agreement and listed by function in the Privacy Policy.
• Your content is not used to train models.
• Clinical information is stored and backed up in Australia. The hosting arrangement.

RequiresDo not adopt or use a government identifier as your own identifier.

• Patients are identified by the hospital's own medical record number.
• A Medicare number recorded for billing is encrypted at the application layer and is not written back into documents.

RequiresKeep the information you hold accurate, up to date and complete.

• The treating clinician remains responsible for the clinical content. Clinical safety.

RequiresProtect information from misuse, interference, loss and unauthorised access.

• Clinical data is encrypted in transit and at rest with AES-256 in Australian Azure regions. The highest-risk fields carry a second application-layer encryption, with keys in Azure Key Vault in Australia.
• Access is least-privilege with multi-factor authentication. Each practice's data is isolated from every other tenant.
• Changes made from the fleet-wide support console are written to the practice's audit chain; console reads are not. Named accounts at aurii and at Black Shard hold fleet-wide access to production, and a practice cannot grant, extend or revoke that access. Vendor access.

RequiresGive people access to their personal information on request.

• A clinician can see the personal information held against their account.
• Patient information is held on behalf of the hospital or specialist who controls the record, so a patient access request runs through them.

RequiresCorrect personal information that is inaccurate, out of date, incomplete or misleading.

• A signed document can be amended, and the amendment is written to the hash-chained audit log.
• Account corrections run on request; patient corrections run through the hospital that controls the record.