Skip to main content
RecovrFlow

Privacy Policy

Last updated: June 2026

1. Introduction

Recovery VR PTY LTD trading as RecovrFlow (“RecovrFlow”, “we”, “us”, or “our”) is committed to protecting the privacy of our users, including Allied Health Professionals, their patients, and visitors to our website. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our platform and services.

We comply with the Australian Privacy Principles (APPs) contained in the Privacy Act 1988 (Cth), as amended by the Privacy and Other Legislation Amendment Act 2024 (which received Royal Assent on 10 December 2024), and all relevant guidance issued by the Office of the Australian Information Commissioner (OAIC), including the OAIC’s dual AI Privacy Guidance published 21 October 2024 and the updated APP Guidelines (November 2025).

RecovrFlow operates exclusively in Australia. We do not offer our services internationally and do not collect or process personal information from individuals located outside Australia.

The Privacy and Other Legislation Amendment Act 2024 introduced a statutory tort for serious invasions of privacy, effective 10 June 2025. We acknowledge that individuals whose privacy is seriously invaded — including through misuse of health information — may bring a direct civil claim in the courts without requiring OAIC involvement. We take this right seriously, and our practices are designed to prevent any circumstances that could give rise to such a claim.

2. Anonymity and Pseudonymity (APP 2)

Under APP 2, we are required to give individuals the option of not identifying themselves, or of using a pseudonym, when dealing with us — where this is lawful and practicable.

Clinical records — anonymity impractical

It is not practicable for individuals to interact with the RecovrFlow platform anonymously or pseudonymously in connection with the creation, storage, or management of clinical records. Clinical documentation generated through the platform is required by law to accurately identify the treating practitioner and the patient. Identified records are also a prerequisite for submission to NDIS, DVA, Medicare, and private health insurers. Accordingly, anonymity or pseudonymity for clinical use is not available and would be inconsistent with the primary purpose of the platform.

Website browsing and enquiries — anonymity available

Individuals who visit our marketing website or submit a general enquiry through our contact or waitlist forms may do so without providing their full legal name, to the extent they choose. We do collect usage data (such as IP address and browser information) automatically for analytics purposes, but this does not require you to identify yourself. If you submit an enquiry using a pseudonym or without a full name, we will respond to the contact details provided and will not attempt to identify you further.

3. Information We Collect (APP 3)

We collect personal information only where it is reasonably necessary for one or more of our functions or activities, and in accordance with APP 3. Health information is sensitive information under the Privacy Act 1988 and can only be collected with express consent and where reasonably necessary for our platform’s clinical documentation functions.

In accordance with OAIC AI Privacy Guidance (October 2024), where our AI processes clinical information and generates outputs — such as structured clinical notes, NDIS reports, or patient summaries — those AI-generated outputs about identified individuals constitute a new “collection” of personal information, not merely a use of existing information. Such AI-generated outputs must comply with all applicable APPs, including accuracy obligations under APP 10.

Account Information

Name, email address, professional credentials (including AHPRA registration number), clinic or organisation name, and contact details provided during registration.

Clinical Data

Patient assessment data, clinical notes, session audio recordings (via Ambient Consult Mode — see Section 6 for full audio handling disclosure), treatment plans, and associated documentation entered or generated through the platform. This constitutes health information under the Privacy Act 1988 and is treated as sensitive information requiring a higher standard of protection.

Government Scheme Data

NDIS participant numbers, DVA file numbers, Medicare provider and patient numbers, and related funding scheme identifiers. See Section 7 for specific handling obligations under APP 9.

Usage Data

Log data, device information, browser type, IP address, pages visited, and interactions with the platform for analytics and improvement purposes.

Waitlist Information

Email addresses and any additional information submitted through our waitlist or contact forms.

4. Unsolicited Personal Information (APP 4)

Occasionally, RecovrFlow may receive personal information that we did not solicit — for example, where a clinician pastes third-party patient data into a platform field beyond what the system requested, where we receive an unsolicited email containing health information, or where incidental information about a third party is included in material submitted to the platform.

In accordance with APP 4, when we receive unsolicited personal information, we will promptly assess whether we could have collected that information under APP 3 (i.e., whether collection was reasonably necessary for our functions and, in the case of sensitive information, whether express consent was obtained). If we determine that we could lawfully have collected the information, we will handle it in accordance with this Privacy Policy. If we determine that we could not have collected the information under APP 3, we will, as soon as practicable, destroy the information or ensure it is de-identified, provided it is lawful to do so.

If you have any concerns about information you may have submitted to the platform in excess of what was requested, please contact us at hello@recovrflow.health so that we can take appropriate action.

5. Collection Notice and How We Use Your Information (APP 5 & APP 6)

In accordance with APP 5, at or before the time we collect personal information (or as soon as practicable after), we notify individuals of: the identity and contact details of RecovrFlow; the purposes for which the information is being collected; the consequences if the information is not provided; any third parties to whom we usually disclose the information (including overseas recipients and AI service providers); and rights to access and correction.

For Ambient Consult Mode, this notification must occur before any recording commences. Our in-platform AI Consent Module supports clinicians in recording patient consent and displaying a disclosure notice prior to activation. Consistent with OAIC guidance, the notification specifically discloses that clinical data will be transmitted to third-party AI providers for processing — this disclosure is made at or before the time of collection.

We use the information we collect to:

  • Provide, operate, and maintain the RecovrFlow platform and services
  • Generate clinical reports and documentation compliant with NDIS, DVA, Medicare, and private health insurance requirements (primary purpose)
  • Cross-reference your clinical documentation against published funding scheme criteria (such as NDIS section 34 Reasonable and Necessary requirements) to highlight which criteria your documentation already addresses and flag areas that may need attention
  • Improve and personalise the platform experience (using de-identified, aggregated data only)
  • Communicate with you, including sending product updates, security alerts, and support messages
  • Comply with legal obligations and enforce our Terms of Service

In accordance with APP 6, we will not use or disclose personal information for a secondary purpose unless you have consented, or an exception under the Privacy Act applies. We will never use patient data to train, fine-tune, or improve AI models (see Section 9).

We note that the transmission of clinical data to our third-party AI providers for inference is itself a “disclosure” under APP 6, even where those providers operate under zero data retention agreements. This transmission is justified as directly related to the primary purpose of collection (generating clinical documentation) and is a purpose that patients would reasonably expect. Our zero-retention agreements address storage and model training, but we acknowledge — consistent with OAIC guidance — that they do not eliminate the disclosure itself.

6. Ambient Scribe Data Handling

When a clinician activates Ambient Consult Mode, the following data lifecycle applies:

Audio capture

Audio is captured locally on the clinician’s device and transmitted over an encrypted TLS 1.3 connection to a transcription service operating solely within Australia (see Section 8 and Section 10 for infrastructure details). Audio is processed in real time for transcription.

Transcript and note generation

Once the consultation concludes, a transcript is used to generate a structured clinical note. The raw transcript is then deleted from RecovrFlow’s systems. The generated clinical note is retained within the practice’s RecovrFlow environment, subject to the practice’s own data retention policy and the clinician’s professional record-keeping obligations (see Section 11 for statutory retention periods).

Audio deletion

Raw audio recordings are never stored by RecovrFlow. Audio is processed in memory during the consultation and discarded immediately after transcription. No audio file is written to disk or retained in any storage system.

Patient notification

Patients must be informed by the treating clinician prior to any ambient AI recording. RecovrFlow provides in-app consent recording tools and an AI disclosure banner that clinicians can display to patients. This aligns with the Safer Care Victoria Ambient AI Scribes Advisory recommendation that patients are always informed and consenting.

State and Territory Surveillance Devices Act compliance

The legal requirements for consent to audio recording of health consultations vary by state and territory. Because the recording is initiated by or on behalf of the health service (service-led recording), patient consent is required in all Australian jurisdictions. The table below summarises the applicable laws. Clinicians are responsible for ensuring compliance with the law of the jurisdiction in which they practise.

JurisdictionConsent requirementRelevant law
VICOne-party permitted; service-led recording requires patient consentSurveillance Devices Act 1999 (Vic)
NSWAll-party consent required (subject to exceptions)Surveillance Devices Act 2007 (NSW)
QLDOne-party; processing and sharing requires consentInvasion of Privacy Act 1971 (Qld)
SAAll-party (two-party) consent requiredSurveillance Devices Act 2016 (SA)
WAAll-party (two-party) consent requiredSurveillance Devices Act 1998 (WA)
ACTAll-party consent for service-led recordingListening Devices Act 1992 (ACT)
TASAll-party consent for service-led recordingListening Devices Act 1991 (Tas)
NTOne-party consentSurveillance Devices Act 2007 (NT)

In South Australia and Western Australia, all parties to the conversation (including the clinician) must consent before recording commences. Recording must be immediately stopped and any captured data deleted if consent is withdrawn during a consultation.

7. NDIS, DVA and Medicare Data (APP 9)

APP 9 restricts the adoption, use, and disclosure of government-related identifiers. RecovrFlow collects the following government-related identifiers solely for the purposes described below:

NDIS Participant Numbers

Purpose: To match patient records to NDIS participant accounts for the generation of Service Agreements, Support Plans, Progress Reports, and other NDIS documentation required to support funding claims and plan reviews. Restrictions: NDIS participant numbers are not adopted as RecovrFlow’s own identifier. They are not disclosed to any third party other than the NDIS (via the clinician) in the course of submitting NDIS documentation. All handling is in accordance with the National Disability Insurance Scheme Act 2013 (Cth) and associated Privacy Rules.

DVA File Numbers

Purpose: To identify veteran patients for the generation of DVA-compliant clinical reports and claims documentation submitted under the Veterans’ Entitlements Act 1986 (Cth) and the Military Rehabilitation and Compensation Act 2004 (Cth). Restrictions: DVA file numbers are not adopted as RecovrFlow’s own identifier and are not used for any purpose unrelated to DVA report generation and submission. They are handled in accordance with DVA’s information management requirements.

Medicare Numbers (Provider and Patient)

Purpose: Medicare Individual Reference Numbers and Medicare Provider Numbers are used exclusively for generating Medicare-compliant clinical documentation, preparing Mental Health Treatment Plans, and supporting item number validation for Medicare Benefits Schedule claims. Restrictions: Medicare numbers are not adopted as RecovrFlow’s own identifier. They are not disclosed to third parties other than as necessary for the direct purpose for which they were collected. They are not used to link records across unrelated patients or to build profiles beyond the immediate clinical documentation purpose.

All government scheme identifiers are stored exclusively at Microsoft Azure (Australia East — Sydney) and are never transferred overseas (APP 8). Access is restricted to the treating clinician and their organisation via role-based access controls and Row Level Security at the database level. We do not use government-related identifiers as RecovrFlow’s own internal identifiers for any purpose.

8. AI and Automated Processing (APP 10 & Automated Decision-Making)

RecovrFlow uses artificial intelligence and automated processing to assist clinicians in generating clinical documentation. In accordance with OAIC AI Privacy Guidance (October 2024) and the Privacy and Other Legislation Amendment Act 2024, we disclose the following:

What our AI does

Our AI transcribes real-time audio from clinical consultations and generates structured clinical notes, NDIS reports, DVA reports, and Medicare documentation. AI outputs are always presented to the treating clinician for review and approval before any clinical or administrative use.

Zero data retention — AI model training

Patient data is never used to train, evaluate, or improve AI models. This is a foundational commitment of RecovrFlow. Our AI providers operate under zero-retention data processing agreements — no patient audio, transcripts, or clinical content is retained by any third-party AI provider beyond the immediate inference request. See Section 10 for sub-processor details.

Accuracy obligations for AI-generated content (APP 10)

Under APP 10, we must take reasonable steps to ensure that personal information we hold is accurate, up-to-date, complete, and not misleading. The OAIC’s October 2024 AI guidance imposes a heightened accuracy standard for AI-generated personal information, recognising the particular risk of hallucinations and errors. To discharge this obligation, RecovrFlow: (a) flags all AI-generated content as AI-assisted within the platform; (b) requires clinician review and approval before any AI-generated note or report is finalised; (c) maintains audit trails of review and approval events; and (d) regularly tests and monitors AI output quality. Clinicians must not finalise or submit AI-generated content that has not been independently reviewed for accuracy.

Automated decision-making formal disclosure

The Privacy and Other Legislation Amendment Act 2024 introduces a new obligation (effective December 2026) requiring APP entities to disclose in their privacy policy when personal information is used in automated decision-making with a significant effect on individuals. RecovrFlow proactively makes this disclosure now.

Automated decision-making activities: RecovrFlow’s AI-assisted report generation processes personal information through automated systems to produce clinical documentation drafts. The Service also cross-references your documentation against published funding scheme criteria—including NDIS section 34 “Reasonable and Necessary” requirements, DVA entitlement criteria, and Medicare Benefits Schedule requirements—to provide a contextual overlay highlighting which published criteria your documentation addresses. No new clinical information is generated by this process; the Service maps your own input against publicly available legislative and regulatory frameworks. These processes may have a significant effect on patients because the resulting documentation influences government funding decisions.

Human oversight requirement: No fully automated decision with legal or significant effect is made without human review. All AI-generated content must be reviewed and approved by a qualified, registered clinician before submission. The clinician bears full professional and legal responsibility for the content of any submitted documentation.

Types of systems involved: Large language model (LLM) inference services accessed via Microsoft Azure AI endpoints; speech-to-text transcription services processing audio in real time.

Patient consent for AI processing

Consistent with AHPRA’s AI in Healthcare guidance (August 2024) and Principle 4 on informed consent, RecovrFlow provides an in-platform AI Consent Module that enables clinicians to record patient consent (verbal, written, or digital) prior to activating ambient AI recording for any consultation. Recording cannot commence without documented consent.

Professional indemnity insurance

In accordance with AHPRA’s AI in Healthcare guidance (Principle 5), practitioners should confirm with their professional indemnity insurer that their policy covers AI-assisted clinical documentation. Many professional indemnity policies were written before AI scribes were commonplace and may require an endorsement or notification to the insurer. RecovrFlow strongly recommends that all clinician customers take this step before using the platform with patients. RecovrFlow’s own professional indemnity insurance does not extend to clinical decisions made by practitioners.

9. Disclosure of Information (APP 6)

We do not sell, rent, or trade your personal or clinical information. We may share information only in the following circumstances:

  • Service Providers: Trusted sub-processors who assist in operating the platform (as listed in Section 10), bound by strict confidentiality and data processing obligations
  • Third-party AI providers: Clinical data is transmitted to AI inference services for the sole purpose of generating clinical documentation (the primary purpose of collection). This transmission is itself a “disclosure” under APP 6, justified as directly related to the primary purpose and within the reasonable expectation of patients who have provided informed consent. All AI providers operate under zero-retention agreements (no storage or model training). See Section 10 for provider details and countries of processing.
  • Legal Requirements: When required by Australian law, regulation, or legal process (e.g. court order, regulatory demand)
  • Safety: To protect the rights, property, or safety of RecovrFlow, our users, or the public
  • Consent: With your explicit consent for any purpose not listed above

10. Sub-processors and Third Parties (APP 8 — Cross-Border Disclosure)

In accordance with APP 8, before disclosing personal information to an overseas recipient, we must take reasonable steps to ensure the overseas recipient will handle the information in a manner consistent with the APPs. If an overseas recipient breaches the APPs, RecovrFlow is taken to have breached the APPs. We disclose the following sub-processors and their countries of processing.

We note that zero-retention agreements address storage and model training but do not, of themselves, fully satisfy APP 8. Consistent with OAIC guidance, we maintain genuine due diligence obligations over all overseas AI providers, including requiring SOC 2 Type II certification, ISO 27001 certification, documented data processing agreements, and breach notification timelines of 24 hours or less to RecovrFlow.

Supabase (on Microsoft Azure — Australia East, Sydney)

Database and backend infrastructure. All clinical data, patient records, and generated reports are stored in Sydney, Australia (Microsoft Azure Australia East). Supabase operates as a data processor under our agreement; data does not leave the Australia East region. No cross-border disclosure occurs for data stored in this infrastructure.

AI Transcription and Generation Providers — Microsoft Azure AI

We use Microsoft Azure AI services for speech-to-text transcription and clinical note generation. Our Azure AI inference endpoints are configured to process data within Australia (Australia East — Sydney) where Microsoft offers Australian-region AI services. For any Azure AI capability not yet available in the Australia East region, processing may occur in Microsoft’s nearest compliant region; we disclose this as a potential cross-border disclosure and maintain a data processing agreement with Microsoft requiring APP-consistent handling. We will update this policy if endpoint configurations change.

All Azure AI providers operate under zero data retention agreements: they do not store, log, or use submitted data for model training. API calls contain only the minimum data necessary for inference. A current list of AI sub-processors, including processing locations, is available on request at hello@recovrflow.health.

Vercel (Frontend Hosting)

Application delivery and hosting. Vercel may process request metadata (IP address, browser information) for the purpose of serving the application. Clinical data is not processed by Vercel.

Stripe (Billing)

Payment processing for subscription billing. Stripe processes payment card information under their own PCI-DSS compliance framework. RecovrFlow does not store payment card details. Billing data is processed in Stripe’s infrastructure; payment information does not include clinical or patient data.

We review our sub-processors regularly and update this register as our technology stack evolves. You may request a current list of sub-processors, including their processing locations and applicable safeguards, at any time by contacting us (see Section 17).

11. Data Storage, Sovereign Data Residency & Retention Periods

RecovrFlow employs a Sovereign Data Residency architecture. All clinical and patient data is stored exclusively in Australia:

  • Australia: Microsoft Azure (Australia East — Sydney) — all clinical data, patient records, and generated reports

Patient data is never transferred outside Australia for storage purposes. We do not operate data storage in the United States, Europe, or any other jurisdiction. This is a deliberate design decision consistent with the Safer Care Victoria Ambient AI Scribes Advisory requirement that health services use AI scribes that store and process data in Australia.

All data is encrypted at rest (AES-256) and in transit (TLS 1.3).

Statutory retention periods for clinical records

The retention of clinical records held on the RecovrFlow platform is subject to the following minimum periods under applicable health records legislation:

Patient typeMinimum retention periodAuthority
Adult patients (NSW, VIC, ACT)7 years from last serviceState health records legislation
Minor patients (NSW, VIC, ACT)Until the patient turns 25 years of ageState health records legislation
Patients in other states/territoriesMinimum 7 years recommendedAPP 11 / NDIS Code of Conduct
NDIS participant records7 years (recommended)NDIS Code of Conduct & Privacy Act

Clinicians and practices bear primary responsibility for meeting record-keeping obligations under applicable law. AI scribe artefacts that do not form part of the medical record (such as raw transcripts and interim audio) are destroyed as soon as practicable after the final clinical note is approved, consistent with the Safer Care Victoria Advisory.

12. Notifiable Data Breaches

RecovrFlow is an APP entity subject to the Notifiable Data Breaches (NDB) scheme under Part IIIC of the Privacy Act 1988 (Cth). In the event of a suspected eligible data breach:

  • We will conduct an assessment within 30 days of becoming aware of the suspected breach (APP 11 / s 26WH obligation)
  • If the assessment concludes there are reasonable grounds to believe an eligible data breach has occurred, we will notify the OAIC and affected individuals as soon as practicable
  • Where a breach originates from or is discovered by a sub-processor (including an AI provider), we require that sub-processor to notify RecovrFlow within 24–48 hours of discovery. We will relay this notification to affected clinician customers as soon as practicable to enable them to meet their own NDB obligations. Our contractual terms with sub-processors specify this 24–48 hour vendor-to-customer notification timeline.
  • Notifications will include: the nature of the breach, the kinds of information involved, the steps we have taken in response, and recommendations for affected individuals
  • Given that our platform handles health information (a sensitive information category), we treat potential breaches with the highest level of urgency

To report a suspected data breach or security incident, please contact hello@recovrflow.health immediately.

13. Direct Marketing (APP 7)

RecovrFlow may use the contact details of clinician customers and prospects for direct marketing communications, including product updates, feature announcements, educational content, and promotional offers relating to the RecovrFlow platform. We only use personal information for direct marketing where we have obtained consent or where an individual is an existing customer and the marketing relates to our own similar services, consistent with the Spam Act 2003 (Cth) and APP 7.

Opt-out: Clinician customers may opt out of marketing communications at any time by: (a) clicking the “unsubscribe” link in any marketing email; (b) updating communication preferences in the platform account settings; or (c) contacting us at hello@recovrflow.health. We will process opt-out requests promptly and within five business days. Opting out of marketing communications does not affect the receipt of essential service communications (such as security alerts, billing notices, and policy updates).

We do not use patient health information for direct marketing purposes. We do not sell or share customer contact details with third parties for their marketing purposes.

14. Security (APP 11)

We implement robust technical and organisational measures to protect your data, consistent with the objective standard affirmed in Australian Information Commissioner v Australian Clinical Labs Limited [2025] FCA 1224, including:

  • AES-256 encryption at rest and TLS 1.3 encryption in transit
  • Role-based access controls and multi-factor authentication
  • Row Level Security (RLS) policies at the database layer ensuring strict organisational data isolation
  • Regular security audits, penetration testing, and vulnerability assessments
  • Comprehensive audit logging for all data access and modifications
  • Documented incident response procedures

15. Your Rights (APP 12 & APP 13)

Under the Australian Privacy Principles, you have the following rights regarding your personal information:

  • Access (APP 12): Request a copy of the personal information we hold about you. We will respond within 30 days. We may charge a reasonable fee for access requests that require significant effort.
  • Correction (APP 13): Request correction of inaccurate, out-of-date, incomplete, irrelevant, or misleading personal information, including AI-generated content. If we correct your information, we will take reasonable steps to notify any third parties to whom we have disclosed the information. If we decline to correct, we will provide written reasons and information on how to escalate to the OAIC.
  • Deletion: Request deletion of your personal information, subject to legal and professional record-keeping retention obligations (see Section 11 for statutory retention periods).
  • Portability: Request a copy of your data in a structured, machine-readable format.
  • Objection to AI processing: Request that your records not be processed by our AI features. Clinicians may disable Ambient Consult Mode on a per-patient basis through the platform settings.
  • Serious privacy invasion tort: Where a serious invasion of privacy has occurred involving your personal information, you may have the right to bring a direct civil claim under the statutory tort introduced by the Privacy and Other Legislation Amendment Act 2024, effective 10 June 2025. This right exists independently of the OAIC complaints process.

To exercise any of these rights, please contact us at the details provided in Section 17.

16. Cookies and Tracking Technologies

We use essential cookies to maintain your session and ensure the platform functions correctly. We may also use analytics cookies (such as Vercel Analytics) to understand how the platform is used and to improve the experience. We do not use cookies for advertising purposes.

17. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices or applicable Australian laws. We will notify you of any material changes by posting the updated policy on our website with a revised “Last updated” date. We encourage you to review this policy periodically.

18. Contact Us

If you have any questions, concerns, or complaints about this Privacy Policy or our data practices, please contact us:

Recovery VR PTY LTD trading as RecovrFlow

Email: hello@recovrflow.health

If you are not satisfied with our response, you may lodge a complaint with the Office of the Australian Information Commissioner (OAIC) at www.oaic.gov.au.