Patient information stays under your control
Plain answers first, technical detail second. Here is where patient data lives, what is kept, who can see it, and what happens when it's deleted.
The questions clinicians actually ask
No jargon — the technical detail comes further down the page.
Where is patient data stored?
Patient data is processed and stored in Australia, on Microsoft Azure infrastructure in Sydney (Australia East). It is not transferred overseas for storage.
Is my data used to train AI models?
No. Customer and patient data is not used to train AI models — ours or anyone else's. Our agreements with AI providers prohibit using your data for training.
How does consent work?
Consent is recorded before a session is processed. Each consent event is logged, so you can show when consent was given and for what.
Who can access a patient record?
Access is controlled at the patient-record level. A clinician can only see the records they are authorised for, and that restriction is enforced in the database itself, not just the app.
Is there an audit trail?
Yes. Consent and documentation events are logged with an audit trail, so your practice can account for what was created, when, and under what consent.
What happens when data is deleted?
When you delete a record, it is removed from the live system, and temporary AI processing data is not kept once processing completes. Deletion requests are honoured in line with the Privacy Act.
The technical detail
For practice owners, IT reviewers and anyone doing due diligence.
Row-Level Security
Access control is enforced at the database tier with Row-Level Security (RLS). Every query is restricted to the patient records the signed-in clinician is authorised for, so application bugs cannot expose another practitioner's records.
Australian hosting
Infrastructure runs on Microsoft Azure Australia East (Sydney). Patient data is processed and stored in-region; there is no cross-border replication of patient records.
Encryption
Data is encrypted in transit (TLS) and at rest. Access to production systems is restricted and logged.
AI processing
Clinical content sent to AI services is used only to produce your requested output. Provider agreements prohibit retention for training, and temporary processing data is not kept once the request completes.
Privacy Act 1988 & APPs
RecovrFlow is designed to support your obligations under the Privacy Act 1988 and the Australian Privacy Principles, including collection, use and disclosure, and deletion. Details are in our Privacy Policy and DPA.
Product boundary
RecovrFlow provides documentation support: it organises information and prepares drafts. It does not diagnose, make treatment decisions, submit reports, or operate as a clinical decision-making tool.
RecovrFlow is designed to align with the Privacy Act 1988 and the Australian Privacy Principles. We describe our posture in plain terms rather than displaying certification badges we do not hold; formal terms are in our Privacy Policy, Data Processing Agreement and consent documentation. If your organisation needs specific assurances (for example a signed DPA or security questionnaire), talk to our team.
Start with your next piece of documentation
Starter is free — no credit card, no time limit. Your data handling terms are the same on every plan.