Solutions Pricing Learn Contact

Security

Where your patients' data goes, and where it doesn't.

It's hosted in Sydney, it's encrypted, and it's never used to train an AI model. Below is the full list of what Avilo can see and change in Cliniko, written so you don't need a lawyer to read it.

Book a demo
  • Patient data hosted in Australia
  • Never used to train AI
  • Revoke access any time

Where your data lives

Patient data stays on Australian-hosted infrastructure.

  • Encrypted in transit and at rest
  • Database and application hosted in Sydney
  • Access limited to what the product needs to run
  • Every provider we use is listed in our Privacy Policy

The Cliniko connection

Avilo connects through Cliniko's official API, with a key you control.

  • Nothing installed in your browser or on your computers
  • Revoke the key from Cliniko at any time
  • No copy of your patient database kept anywhere else
  • Where to find your API key

AI, kept on a short leash

On Confirm, most of the work is plain rules. Where AI is used, it's constrained.

  • Models are never trained on your patient data
  • Clinical questions are never answered by AI
  • Anything unclear goes to a person
  • A staff reply pauses Avilo on that conversation

Your controls

It's your clinic's data, and it behaves that way.

  • Export or delete everything
  • Every conversation logged and reviewable
  • Avilo AI stays off until you switch it on
  • You set the rules: nudges, who gets alerts, what happens to a no

Plain list

What Avilo can see and change in Cliniko.

The short, complete list. If it isn't here, Avilo doesn't touch it.

What Avilo reads

  • Appointments and availability
  • Practitioners, appointment types and locations
  • Patient names and mobile numbers, to match replies
  • Replies to your Cliniko reminders

Avilo doesn't read clinical notes or treatment records.

What Avilo writes

  • Confirm: confirmation status on the appointment
  • Avilo AI, once switched on: bookings, reschedules and cancellations, within your rules

Nothing is written to Cliniko that a patient and your rules haven't agreed to.

Security questions.

Where is patient data stored?

In Australia. The database and application are hosted in Sydney, encrypted in transit and at rest.

Who can see patient messages?

The team members you invite to your clinic's Avilo account. Avilo staff only open a conversation when you ask us to for support.

Is my data used to train AI models?

No. Your patient data is never used to train models, ours or anyone else's.

Does Avilo record calls?

No call audio is kept. Avilo keeps the outcome of the call and a written summary in the conversation log, so your team can see what happened.

How do you handle health information and privacy?

We collect only what's needed to manage appointments and messages, and handle it under our Privacy Policy and the Australian Privacy Principles. Read the Privacy Policy →

What happens if there's a data breach?

We notify affected clinics within 72 hours and follow the Notifiable Data Breaches scheme with the OAIC. Details are in the Privacy Policy.

Questions about security, privacy or data handling? Email hello@avilo.com.au and you'll hear back from the founder, not a ticket queue.

This website only sets essential cookies until you choose otherwise. Calendly, ad measurement and analytics load only if you agree. Cookie settings.

Bring your hard questions to the call.

We'll show you what Avilo sees and does on a real diary, and you can grill us on the rest.

Book a demo

No commitment · No credit card · Built in Sydney for allied health