Dental Data Security in Australia: What Every Practice Owner Must Know
Scott Rotton
Founder & CEO, Zavy360
Founder, Zavy360 Dental Practice Management | Experience partnering with 50+ Australian dental practices
Dental practices handle sensitive information every day, including health records, medical histories, payment details and patient identifiers. Protecting it requires suitable software, secure equipment and clear procedures for staff.
Whether your practice uses an on-premises server or a cloud platform, establish who manages access, updates, backups and incident response. This guide covers the Australian privacy framework and practical questions to put to your software and IT providers.
Australian Privacy Law and Dental Practices
Australian dental practices are subject to the Privacy Act 1988 (Cth), which establishes the 13 Australian Privacy Principles (APPs). These principles govern how organisations collect, use, store, and disclose personal information. For dental practices, the requirements are stricter than for many other small businesses because health information is "sensitive information" under the Act, which attracts extra protections, and because health service providers are covered by the Act regardless of their turnover.
The Australian Privacy Principles That Matter Most
Several APPs have direct implications for how dental practices manage data:
APP 1 (Open and transparent management) requires practices to have a clearly expressed and up-to-date privacy policy that explains how patient information is handled. This includes the kinds of information you collect and hold, how you collect and hold it, the purposes for which you use it, how patients can access or correct it, how they can complain, and whether you are likely to disclose it overseas and to which countries.
APP 6 (Use or disclosure) limits how you use or disclose patient information beyond the purpose it was collected for, which is providing dental care. Other uses generally need the patient's consent or must fall within a listed exception. Direct marketing is covered separately by APP 7, and using health information for marketing requires the patient's consent.
APP 8 (Cross-border disclosure) is critical when evaluating cloud software providers. If your software sends or stores patient data outside Australia, APP 8 may apply, depending on whether the overseas provider can access and handle the data or simply stores it under your control. Where APP 8 applies, you generally remain accountable for how the overseas recipient handles it. Ask where records are stored and whether connected features or support processes involve overseas access or processing. Australian hosting alone does not establish compliance. See the OAIC guidance on APP 8.
APP 11 (Security of personal information) requires practices to take reasonable steps to protect personal information from misuse, interference, loss, unauthorised access, modification, or disclosure. This applies to both the practice's physical security and its digital systems, including the software platform chosen to manage patient records.
Record-Keeping and Retention Obligations
Beyond the Privacy Act, the Dental Board of Australia's Code of conduct requires practitioners to keep accurate, secure health records, and state laws set how long those records must be kept. In NSW, Victoria and the ACT, the law requires records to be kept for at least seven years after the last service for adults, and until age 25 for patients treated as children. Other states have no equivalent statute for private practices, so many practices apply the same periods as a minimum, and indemnity insurers often recommend keeping records longer.
Plan for record access throughout the required retention period, including when you replace a server or change software. Confirm how clinical notes, images and attachments can be exported, which formats are available and how archived records will remain readable. Record the agreed timeframes and any costs in your software and support arrangements.
The Notifiable Data Breaches Scheme
Since February 2018, the Notifiable Data Breaches (NDB) scheme under Part IIIC of the Privacy Act has required organisations to notify both the Office of the Australian Information Commissioner (OAIC) and affected individuals of an eligible data breach: one likely to result in serious harm, where remedial action has not removed that risk.
For dental practices, a notifiable breach could include:
- Unauthorised access to patient records (e.g., a staff member accessing records without a clinical reason)
- Ransomware attacks that encrypt or exfiltrate patient data
- Accidental disclosure of patient information (e.g., emailing records to the wrong recipient)
- Loss or theft of devices containing unencrypted patient data
Where there are reasonable grounds to suspect an eligible breach, carry out a reasonable and expeditious assessment and take all reasonable steps to complete it within 30 days. If there are reasonable grounds to believe an eligible breach has occurred, notify the OAIC and affected individuals as soon as practicable. Follow the OAIC's breach response guidance.
Agree how your practice, software provider and IT provider will work together to contain an incident, preserve relevant logs and assess the information affected.
Data Sovereignty: Why Where Your Data Lives Matters
Data sovereignty refers to the principle that data is subject to the laws and governance structures of the country where it is physically stored. For Australian dental practices, this is a practical concern with real legal implications.
Australian Data Centres and Jurisdiction
Your practice's Privacy Act and NDB obligations apply wherever your data is stored. What storage location mainly changes is which other countries' laws can also reach that data, and how practical it is to enforce your rights if something goes wrong. It is not the only factor: the laws that apply to the provider and its own suppliers can matter too, so ask about both.
For both on-premises and cloud systems, ask whether backups, remote support or connected services involve overseas access or processing. Document the locations and responsibilities rather than relying on the software provider's office address.
What "Cloud" Means for Data Location
Cloud services can store information in different countries. The location of the software provider's office does not establish where your practice's records, backups or support data are held.
When evaluating any cloud dental software, ask specifically:
- Where are the primary data centres located? (City and country)
- Where are the backup/disaster recovery data centres located?
- Is any patient data processed or temporarily stored outside Australia?
- Which features, if any, send patient data outside Australia, and to which countries?
Zavy360's security practices include storing practice records in Australian data centres, and our AI Scribe data page explains how AI Scribe audio and transcripts are processed by contracted providers in the United States.
Questions to Ask Your Provider
Alongside data location, clarify how records will be managed throughout your use of the system:
- What rights and responsibilities does the contract set out for use of patient records?
- Who can access records for support, and how is that access authorised and logged?
- What can the practice export, in which formats, within what timeframe and at what cost?
- How are records retained, returned or deleted when the agreement ends?
Security Controls for On-Premises and Cloud Systems
Review these controls with your software and IT providers. For an on-premises system, include the server, network and backup equipment. For a cloud system, include the hosted service, practice devices and any local integrations.
Encryption at Rest and in Transit
Ask how patient data is encrypted in transit and at rest, including backups and portable devices. Confirm who manages encryption keys, how updates are maintained and whether any part of the workflow falls outside those protections. Request technical documentation that your IT provider can review.
Access Controls and Audit Trails
Use individual staff accounts and assign permissions according to each person's duties. Review access when roles change and remove it promptly when staff leave. Check how administrator and remote support access are controlled.
Audit trails (automated logs of who accessed which records and when) are a key security control and help you show you have taken reasonable steps under APP 11. If a patient raises a concern about who has viewed their records, or you need to investigate a possible breach, you need a system that can show this quickly and accurately.
Backup and Disaster Recovery
For on-premises systems, agree who monitors backups and keep protected copies separate from the server. For cloud systems, confirm which backup and recovery tasks the provider manages. In either case, ask:
- How often are backups taken, and which records, images and attachments are included?
- Where are copies stored, and how are they protected from unauthorised access or deletion?
- How long are backups retained?
- When was restoration last tested, and what did the test cover?
- What is the recovery time objective (RTO): how quickly should the system be restored?
- What is the recovery point objective (RPO): how much recent work could be lost?
Document a practical plan for operating during an interruption. Check that backup retention and long-term clinical record retention are both addressed.
Regular Security Assessments and Certifications
Ask about independent security testing and the scope of any certifications or audit reports. Examples include ISO 27001 certification and SOC 2 Type II reports. Confirm which organisation, systems and services they cover and when they were assessed. A certificate or report does not replace secure configuration and daily practice procedures.
Staff Access Management
Your software should provide administrative controls for managing staff accounts, including:
- Individual user accounts (no shared logins)
- Role-based permission levels
- Automatic session timeouts
- Multi-factor authentication (MFA) for every user login
- Immediate account deactivation when a staff member leaves the practice
Shared logins (where multiple staff members use the same username and password) are a significant security risk and make audit trails meaningless. Every user action should be attributable to a specific individual.
Practical Security Checklist for Practice Owners
Use this checklist with your software and IT providers. Record the arrangements, supporting documentation and person responsible for each item.
-
Data location: Where are records and backups stored, and which features or support arrangements involve overseas access or processing?
-
Encryption: How are records protected in transit and at rest, including backups and staff devices?
-
Access controls: Can each person have an individual account, appropriate permissions and multi-factor authentication?
-
Audit trails: What access and changes are logged, how long are logs retained and how can they be reviewed?
-
Backup and recovery: Who checks backups, how often is restoration tested and what recovery objectives have been agreed?
-
Incident response: Who contacts the practice after an incident, and what assistance is available with assessment and notification?
-
Record access and exports: Which data and attachments can be exported, in what format, within what timeframe and at what cost?
-
Security assessments: What current independent testing or certification covers the service your practice will use?
-
Staff procedures: Who manages account changes, device security, training and updates?
-
Retention and data return: How will records remain readable for the required period, including after equipment replacement or the end of an agreement?
Protecting Your Practice and Your Patients
Protecting patient information is a shared operational task for practice management, staff, software providers and IT support. The practice still needs to meet its legal and professional obligations, whichever deployment model it chooses.
Keep a written record of responsibilities, review access regularly and test recovery arrangements. On-premises and cloud systems both need ongoing attention to configuration, maintenance and staff procedures.
For a broader evaluation of cloud-based dental software platforms, including features beyond security, our cloud dental software guide covers what Australian practices should consider when moving to the cloud.
Want to discuss Zavy360's data handling and security arrangements? Book a demo and bring your practice's security and record-access questions.