Skip to main content

AI Receptionist · Data Handling & Security

Patient information, handled like it matters.

Calls to a clinic contain health information, so we treat every recording, transcript and message as sensitive. The exact legal obligations depend on the clinic and approved architecture. Our job is to make the data flow and controls visible before launch, not to make a blanket compliance or hosting promise. This receptionist is part of our healthcare services for clinics.

What the agent collects

Only what a good receptionist would write on a message pad: the caller's name, contact number, reason for calling, and how urgent it is. She collects the minimum the clinic needs to call back, never probes for extra health detail, and never discloses information about any patient to any caller, including confirming whether someone is a patient at all.

Every caller knows what's happening

The approved call opening tells the caller they are speaking with an AI assistant and, where recording is enabled, that the call is recorded. The clinic approves the wording and any non-recording path before launch. The disclosure is not described as a universal legal guarantee because recording requirements and the clinic's circumstances still need to be considered.

Where recordings and transcripts live

Voice, telephony, automation and clinic systems can each process or retain part of a call. Before launch, the written scope identifies the approved providers, confirmed storage regions, transcript and message destinations, access roles, retention settings and deletion path. Australian residency is claimed only when every relevant layer has been verified. The review uses the OAIC's guidance for APP 8 cross-border disclosure and APP 11 security and retention. The clinic remains responsible for confirming that the final setup meets its obligations.

The website demo is not a patient channel

The live demo uses fictional clinic profiles and third-party voice infrastructure that creates call logs, transcripts and audio artefacts for quality review. Do not provide real patient, clinical or other confidential information during a demo call. The demo is not represented as Australian-hosted.

What the agent will never do

No diagnosis or medical advice. No outcome promises. No testimonials. No invented discounts. No comments on other practitioners or clinics. Emergency symptoms trigger an immediate call-000 script with an urgent flag to your nominated contact. Every one of these rules traces to a cited source in a versioned register we maintain, and when a regulation changes, we know exactly which rules and which agents are affected.

What the clinic receives before launch

Before launch, the clinic receives a data-flow summary covering the approved providers, recording disclosure, access, confirmed storage regions, retention and the destinations for transcripts or messages. Australian data residency is treated as a specific architecture requirement and is not assumed across third-party voice platforms. A single call can pass through telephony, voice, automation, storage, messaging and practice-management systems, and each layer may process or retain part of it, which is why the summary looks at the complete setup rather than one product.

Access, correction and deletion

Access roles and the deletion path are documented with each clinic before launch. Under the Australian Privacy Act, people can ask to access the personal information an organisation holds about them, ask for it to be corrected or deleted, and complain to the Office of the Australian Information Commissioner (OAIC). Our privacy policy sets out how we handle personal information, including that a client has 30 days to export their data when an engagement ends, after which we delete or de-identify what we hold, except records we are required to keep by law.

What the Australian Privacy Principles expect (general guidance)

This section is general information about the law, not a statement about any one setup. The OAIC notes that identifiable call recordings can be personal information and that health information receives additional protection. APP 8 asks an organisation to take reasonable steps before personal information is disclosed to an overseas recipient, which matters when a voice or transcription provider processes data outside Australia. APP 11 asks an organisation to take reasonable steps to protect personal information from misuse, interference, loss and unauthorised access, and to destroy or de-identify it when it is no longer needed.

If something goes wrong: Notifiable Data Breaches (general guidance)

Under the OAIC's Notifiable Data Breaches scheme, an organisation covered by the Privacy Act must notify affected individuals and the OAIC when a data breach is likely to result in serious harm. If a breach is only suspected, the organisation is expected to assess it promptly, within 30 days. Health information breaches are often treated as higher risk. Who does what in a breach is a point to settle in writing with any vendor, and the clinic remains responsible for its own notification duties.

Questions to ask any AI receptionist vendor

Which providers touch a call, from the phone line to the message that reaches your team? In which country is each recording and transcript stored, and has the provider confirmed that in writing? Who can access them, and how is that access logged? How long are they kept, and how are they deleted? What happens to the data if you end the engagement? What is the process and timeframe if the vendor suspects a breach? We are happy to answer these for our own setup as part of the pre-launch scope.

The clinic stays responsible

This page is not legal advice and is not a compliance certificate. The clinic remains responsible for its own privacy obligations and for confirming that the final setup meets them. Our readiness check is a planning aid for working through these decisions, and it keeps your answers in your browser.

Common questions

Does the AI receptionist record calls?

Only where the clinic enables recording. The approved call opening tells the caller they are speaking with an AI assistant and, where recording is enabled, that the call is recorded. The clinic approves the wording and any non-recording path before launch.

How long is call data kept?

Retention is a setting documented with each clinic before launch, covering every provider that holds part of the call. This page does not state a single retention period because it depends on the approved setup. The clinic should confirm the period in writing.

Who can access call recordings and transcripts?

Access roles are listed in the written scope agreed with the clinic before launch. The clinic should check that only the people who need the information can reach it.

How does a patient ask for their call data to be deleted?

A deletion path is documented with each clinic before launch. Under the Australian Privacy Act, people can request access to, correction of and deletion of their personal information, and can complain to the OAIC. Requests can be sent through our contact page, and the clinic stays responsible for its own privacy obligations.

Is the website demo safe to use with real patient details?

No. The live demo uses fictional clinic profiles and third-party voice infrastructure that creates call logs, transcripts and audio artefacts for quality review. Do not give real patient, clinical or other confidential information during a demo call.