Trust centre

How Qiri looks after patient records

Where records are stored, how they are protected, who can open them, and what we have not done yet. Written for pharmacy owners, and for whoever reviews our security on their behalf.

Last reviewed

Sydney Where patient records are stored, on Google Cloud
AES-256 Encryption for everything stored, under keys we control for clinical records
TLS 1.2+ The oldest protocol the console and patient app accept
Pharmacist Signs every clinical decision, with the reasoning recorded beside it

Clinical safety

Security starts with what the software is allowed to decide. Qiri recommends. A registered pharmacist decides.

A pharmacist signs every decision
A registered pharmacist reviews each recommendation, then approves, amends or overrides it and signs. Nothing is dispensed on a model's say-so.
Rules the model cannot override
Maximum dose ceilings, absolute contraindications and mandatory monitoring thresholds are encoded as rules. A proposal that breaks one is stopped, whatever the model says.
Regulatory pathway
In Australia, designed against the conditions of the TGA's clinical decision support exemption as amended from 1 November 2026. Qiri recommends and a registered pharmacist decides. Each recommendation shows the guidelines, rules and sources behind it while the pharmacist reviews it, so they can check it before signing. Clinical review is independent. Sources.
A record of every decision
Each decision keeps its inputs, the sources cited, the rules that fired, the model used and what the pharmacist did. When a regulator, an insurer or your lawyer asks what happened and why, the answer is in the record.

Where data lives

Every patient record is stored on Google Cloud in Sydney, whichever country the pharmacy is in. Reasoning runs on de-identified data.

DataAustralian pharmacyNew Zealand pharmacyUnited States pharmacy
Patient records Google Cloud, Sydney Google Cloud, Sydney, Australia Google Cloud, Sydney, Australia
Clinical reasoning Qiri's platform, part of which runs in the United States, after direct identifiers are removed in Australia New Zealand prescriptions are not sent outside Sydney. Reasoning for New Zealand pharmacies will run in Sydney or not at all, decided before the first one goes live Qiri's platform in the United States, after direct identifiers are removed
National services Australian services never serve a New Zealand site Data licensed for New Zealand serves New Zealand sites only Early access

Some supporting services run outside Australia, such as sign-in for pharmacy staff and email delivery. Each one is listed under subprocessors, with what it receives.

Protection

Data is encrypted in transit and at rest, and the databases aren't on the open internet.

In transit
Every connection to the console and the patient app uses TLS 1.2 or later, through a web application firewall. TLS 1.0 and 1.1 are refused.
At rest
Everything Qiri stores is encrypted with AES-256. Clinical records are encrypted under a key Qiri controls, rotated every 90 days, and patient files under keys Qiri controls.
Identity numbers
Patient identity numbers carry a second layer of encryption of their own, so a copy of the database alone does not reveal them.
Databases
Production databases accept no connections from outside networks. They are reached only through Google's authenticated connector.
Payments
Card payments are processed by Stripe, a PCI DSS Level 1 service provider. Card details go into Stripe's own payment fields, the patient app's Stripe payment sheet or Apple Pay, or a Stripe card reader at the counter, and never reach Qiri's servers. We keep only the card brand, last four digits and expiry, so a receipt can show which card was charged. Our payment pages run a strict script policy, so only scripts we have approved can run beside the card fields.

Access

Each pharmacy sees its own patients, and each person sees what their role allows.

Pharmacy by pharmacy
Row-level security in the database scopes every read to the user's own pharmacy sites, so one pharmacy's account sees only its own patients, scripts and files.
Roles
Every person signs in with their own account and a role, from pharmacist to assistant. The role decides what they can see, change and sign.
Controlled drugs
Each S8 register entry takes the signer's own PIN, and only a pharmacist can sign, reverse or resolve. See the controlled drug register.
Qiri staff
Access to production systems is limited to named Qiri staff, each with their own account.
Leaving Qiri
A pharmacy can export its records at any time. If it leaves, it has a 60-day wind-down and, on request, a complete export of its dispensing, consultation, services, point-of-sale, controlled drugs register and audit records. After that we keep records only for as long as the law requires, and if the pharmacy is sold they go to the buyer on the owner's instruction. See clauses 11.4 and 16.1 of the Software User Agreement.
Deleting a patient account
A patient can delete their account in the Qiri app, or by email, actioned within 30 days. Dispensing records stay with the pharmacy's health record, as health-records law requires. See deleting your account and section 7 of the privacy policy.

Resilience

Backed up continuously, restored for real, and reported openly when something goes wrong.

Backups
Point-in-time backups of every database, with an alert if a backup fails.
Tested restores
We restore from backup to prove it works. The test on 12 October 2026 brought back every table in 11 minutes.
Status
Live service status, incidents and maintenance at status.qiri.ai, updated as things happen.

AI and your data

Names and identifiers are removed before a model sees a script, and a pharmacist signs every decision.

De-identified first
Direct identifiers are removed before a prescription reaches a reasoning model.
No training on your data
We do not train on customer data without explicit, separate opt-in.
Never the last word
A model proposes. The safety rules check the proposal, and a pharmacist decides. See clinical safety.

Assurance

What we hold, what we inherit from our hosting, and what comes next. We would rather tell you what is missing than have you find it.

Ours
Security policies
Written information security policies covering access, change, incidents, recovery, suppliers and people, mapped to Health New Zealand's Health Information Security Framework (HISO 10029.4).
Inherited
Google Cloud
Qiri runs on Google Cloud services named in Google's IRAP assessment at PROTECTED level, the Australian Government's security assessment for cloud services. Google Cloud also holds ISO/IEC 27001 certification and SOC 2 reports for those services.
Next
Penetration test
An independent penetration test before our first New Zealand pharmacy goes live, then every year.
Not yet
Certification
Qiri does not hold its own SOC 2 report or ISO 27001 certificate today. When that changes, it will be here.

Subprocessors

The suppliers that handle data for Qiri, where they run, and what each one receives.

SupplierUsed forWhereReceives
Google CloudHosting, databases, file storage, de-identification, and sign-in for pharmacy staff and the patient appPatient records in Sydney, Australia. Sign-in runs in the United States, and service logs are held globallyEverything Qiri stores. Sign-in holds user names and email addresses and a patient's sign-in details, no patient records
Google Gemini and Jina AI, through Qiri's platformClinical reasoning modelsUnited StatesDe-identified prescription details from Australian and United States pharmacies. Never New Zealand prescriptions
ResendEmail deliveryUnited StatesPatient and pharmacy names, and the address for a home visit
Expo, Apple and GooglePush notificationsOverseasThe text of a notification
StripePaymentsGlobalBilling contacts. Card details are handled by Stripe alone
GitHubSource codeUnited StatesCode only, no patient data

Questions we are asked

Where is Qiri patient data stored?

Every patient record is stored on Google Cloud in Sydney, Australia, whichever country the pharmacy is in. For Australian and United States pharmacies, clinical reasoning runs on Qiri's platform, part of which operates in the United States, after direct identifiers are removed. New Zealand prescriptions are not sent outside Sydney.

Is Qiri SOC 2 or ISO 27001 certified?

Not today. Qiri runs on Google Cloud services named in Google's IRAP assessment at PROTECTED level, and Google Cloud holds ISO/IEC 27001 certification and SOC 2 reports for them. Our own security policies are mapped to Health New Zealand's Health Information Security Framework, and an independent penetration test comes before our first New Zealand pharmacy goes live.

Is patient data used to train AI models?

We do not train on customer data without explicit, separate opt-in. Direct identifiers are removed before a prescription reaches a reasoning model.

Can one pharmacy see another pharmacy's patients?

Row-level security in the database scopes every read to the user's own pharmacy sites, so one pharmacy's account sees only its own patients, scripts and files.

Does Qiri store card details?

No. Card payments are processed by Stripe, a PCI DSS Level 1 service provider, and card details never reach Qiri's servers. We keep only the card brand, last four digits and expiry, so a receipt can show which card was charged.

What happens to our records if we leave Qiri?

You can export your records at any time. When a pharmacy leaves, it has a 60-day wind-down and, on request, a complete export of its dispensing, consultation, services, point-of-sale, controlled drugs register and audit records in a documented format. After that Qiri keeps the records only for as long as the law requires, and if the pharmacy is sold they go to the buyer on the owner's written instruction.

Does the AI make dispensing decisions?

No. Qiri recommends, hard safety rules check the recommendation, and a registered pharmacist approves, amends or overrides it and signs. Every decision keeps a record of its inputs, sources, rules and the pharmacist's action.

Will Qiri complete our security questionnaire?

Yes. Send it to support@qiri.ai. We answer from our written policies, and say plainly where a control is not in place yet.

Contact

Security review or questionnaire

Send it to support@qiri.ai. We answer from our written policies, and say plainly where a control is not in place yet.

Report a security issue

Email hello@qiri.ai with SECURITY in the subject. Tell us what you found and how to see it for ourselves. Please do not open, change or keep anyone's data while you test, and give us the chance to fix it before you share it. The same contact is in our security.txt.

How we handle personal information is in our privacy policy for Australia.