All patient and clinical data stored by Qliva is hosted within Australia, with clear disclosure of every third-party service that touches your clinic's data.
Australia-first hosting
Qliva runs on AWS ap-southeast-2 (Sydney). This means all patient records, clinical notes, pathology results, prescriptions, invoices, forms, consents, and communications are stored in Australia.
This applies to:
- Patient demographics and health records
- Clinical notes and consult summaries
- Pathology results and clinical mail
- Signed prescriptions and eRx tokens
- Invoices and payment records
- Form responses and consent documents
- Communications (SMS and email logs)
- Wearable data synced from connected devices (coming soon)
Encryption
| Layer | Standard |
|---|---|
| Data at rest | AES-256 |
| Data in transit | TLS 1.2+ |
All data is encrypted both when stored on disk and when transmitted between services.
Tenant isolation and row-level security
Every database row in Qliva is protected by Row Level Security (RLS) policies enforced at the database level. Your clinic's data is completely isolated from all other clinics — there is no shared table or shared query that could return another clinic's records.
All database queries are scoped by tenant_id, and this is enforced by the database engine — not just application logic. A misconfigured query cannot accidentally return another clinic's data.
Third-party services
Qliva uses a small number of trusted third-party services for specific functions. Here's what each one touches and where it operates:
| Service | What data it touches | Region |
|---|---|---|
| Supabase | Database, auth, file storage | AWS ap-southeast-2 (Sydney) |
| Vercel | Application hosting, serverless compute | Multi-region edge + AU |
| Resend | Email delivery (content, recipient address) | US (SOC 2 Type II) |
| ClickSend | SMS delivery (phone number, message body) | AU |
| Deepgram | AI Scribe — audio transcription (real-time; audio discarded) | US |
| Parchment Health | eRx tokens | AU |
| Terra API | Wearable data aggregation (coming soon) | US |
| Stripe | Payment processing (card data never touches Qliva servers) | US (PCI DSS Level 1) |
| Xero | Invoice and payment data (if connected) | AU/NZ |
AI Scribe and audio data
The AI Scribe feature transcribes in-consultation audio in real time via Deepgram. Raw audio is never stored by Qliva or Deepgram. Only the text transcript is retained, attached to the clinical note.
Deepgram processes audio in real time and does not retain audio beyond the active session. Once transcription is complete, the audio is discarded.
Wearable data and patient consent (coming soon)
Wearable and device integration is a planned feature and is not yet available on the platform. When launched, patients will explicitly connect their wearable devices through the patient portal, and no data will be collected without consent.
Backup and data retention
- Backups: daily automated backups of all clinic data
- Retention: clinical data is retained indefinitely
- Soft deletion: records that are deleted within the app are soft-deleted — they are preserved in the database for regulatory compliance and can be recovered if needed
Qliva is designed for Australian healthcare providers and is built to comply with the Privacy Act 1988 and the Australian Privacy Principles (APPs).
If your clinic is subject to specific regulatory requirements — for example, government contracts requiring IRAP-assessed infrastructure, or jurisdictional data localisation requirements beyond standard APPs — contact Qliva support before going live. We can discuss your compliance needs and whether additional configuration is required.