How we protect you
Security built into every layer
Security isn't a feature we added later — it's the foundation Qliva was built on.
Australian data hosting
Every byte of patient data stored in Qliva lives in Australia — specifically AWS ap-southeast-2 (Sydney) — and the application itself runs in Vercel's Sydney region. Storage is not the whole picture: some processing happens overseas. Clinical text sent to Anthropic for AI drafting, consultation audio sent to Deepgram for transcription, telehealth video carried by Daily.co, transactional email, payments and error monitoring are all handled by providers outside Australia. Our Privacy Policy lists every provider, what it does and where it operates.
Encryption everywhere
All data is encrypted in transit using TLS 1.2+ and encrypted at rest using AES-256. This applies to patient records, pathology results, prescriptions, clinical notes, and every other piece of sensitive information in the platform.
Strict clinic isolation
Qliva is a multi-tenant platform — multiple clinics share the same infrastructure but their data is completely isolated. Every database table enforces Row Level Security (RLS) policies at the database layer, so even a software bug cannot expose one clinic's data to another.
Role-based access control
Three distinct access levels — practitioners, clinic administrators, and patients — each see only what they need. Practitioners cannot access admin billing functions. Patients can only see their own records. All access is enforced server-side, not just hidden in the UI.
Audit logging
General-purpose audit logging does not work reliably today. Account and platform events — clinic sign-up, credential changes and administrative configuration changes — are written to an audit table, but those writes fail without raising an error, so most of these events are never recorded: the table held five records across the entire platform when last measured. Clinical activity is not covered at all — record access, prescribing, pathology requests and appointments produce no audit entries — and audit records are not write-protected at the database level. One workflow is the exception: the Blueprint and medical-practitioner-review process is logged reliably end to end, including AI generation, practitioner sign-off, approval and release. Repairing the rest is tracked engineering work rather than a shipped feature.
Rate limiting & abuse prevention
Rate limiting covers token-accessed pathology form links, storefront webhooks and clinic sign-up. It does not cover sign-in: credential checks are made directly between the browser and our authentication provider, so the only limit on repeated sign-in attempts is that provider's own, which we have not independently measured. Single-use pathology form links expire after 30 days and can only be opened once.
Continuous monitoring
Qliva uses Sentry for real-time error monitoring and UptimeRobot for external uptime monitoring. Any system error or downtime triggers an immediate alert. Our public status page is always available at stats.uptimerobot.com/4vBJSgJv7v.
Secure transactional email
All system emails — appointment reminders, pathology form links, password resets, and practitioner invitations — are sent via Resend using a verified Australian domain. This prevents spoofing and ensures reliable delivery.
Your data is stored in Australia
Qliva runs on infrastructure located in AWS Sydney (ap-southeast-2), with application compute in Vercel's Sydney region. Patient health records, clinical notes, prescriptions, and pathology results are stored in Australia, and so are our database backups.
Processing is a separate question, and some of it happens overseas: AI drafting, speech transcription, telehealth video, transactional email, SMS, payments, accounting, error monitoring and uptime monitoring are performed by third-party providers, several of them outside Australia. Our Privacy Policy names each provider, what it handles and where it operates. Data processing agreements are in place with some of these providers and are still being put in place with others.
Compliance
Built for Australian healthcare regulation
Qliva is designed around the specific compliance requirements of Australian healthcare — not adapted from a foreign product.
Privacy Act 1988
Qliva is designed to comply with the Australian Privacy Act 1988 and the Australian Privacy Principles (APPs). Sensitive health information is only collected with explicit patient consent, stored securely, and never shared with third parties without authorisation.
Notifiable Data Breaches (NDB)
In the event of an eligible data breach, Qliva supports clinic obligations under the Notifiable Data Breaches scheme — including breach identification, assessment, and notification procedures.
TGA Software as a Medical Device
Clinical decision support features in Qliva are designed to comply with TGA Software as a Medical Device (SaMD) guidelines. AI-generated content is always presented as a draft for practitioner review — it is never automatically applied to a patient record.
7-year health record retention
Patient records, clinical notes, prescriptions, and pathology results are retained for a minimum of 7 years in line with Australian health records legislation. All deletions in Qliva are soft deletes — records are marked as deleted but never permanently removed.
Transparent uptime
Qliva is monitored 24/7 by external uptime checks. You can view our live system status — including historical uptime and any past incidents — on our public status page.
View system status →Questions about security?
If you have specific security questions about how Qliva handles your clinic's data, or you'd like to discuss compliance requirements before signing up, we're happy to talk.
Get in touch