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.
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.
Security starts with what the software is allowed to decide. Qiri recommends. A registered pharmacist decides.
Every patient record is stored on Google Cloud in Sydney, whichever country the pharmacy is in. Reasoning runs on de-identified data.
| Data | Australian pharmacy | New Zealand pharmacy | United 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.
Data is encrypted in transit and at rest, and the databases aren't on the open internet.
Each pharmacy sees its own patients, and each person sees what their role allows.
Backed up continuously, restored for real, and reported openly when something goes wrong.
Names and identifiers are removed before a model sees a script, and a pharmacist signs every decision.
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.
The suppliers that handle data for Qiri, where they run, and what each one receives.
| Supplier | Used for | Where | Receives |
|---|---|---|---|
| Google Cloud | Hosting, databases, file storage, de-identification, and sign-in for pharmacy staff and the patient app | Patient records in Sydney, Australia. Sign-in runs in the United States, and service logs are held globally | Everything 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 platform | Clinical reasoning models | United States | De-identified prescription details from Australian and United States pharmacies. Never New Zealand prescriptions |
| Resend | Email delivery | United States | Patient and pharmacy names, and the address for a home visit |
| Expo, Apple and Google | Push notifications | Overseas | The text of a notification |
| Stripe | Payments | Global | Billing contacts. Card details are handled by Stripe alone |
| GitHub | Source code | United States | Code only, no patient data |
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.
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.
We do not train on customer data without explicit, separate opt-in. Direct identifiers are removed before a prescription reaches a reasoning model.
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.
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.
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.
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.
Yes. Send it to support@qiri.ai. We answer from our written policies, and say plainly where a control is not in place yet.
Send it to support@qiri.ai. We answer from our written policies, and say plainly where a control is not in place yet.
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.