NDIS Provider Privacy and Security: Data, Compliance and Cyber Basics
NDIS provider privacy security explained: which laws apply, the data you must protect, breach-reporting duties and practical cyber steps to stay compliant.
What NDIS provider privacy and security actually covers
Privacy is about what you collect, why, who sees it and how long you keep it. Security is about protecting that information from loss, theft, unauthorised access or accidental disclosure. For an NDIS provider the two overlap because almost everything you hold about a participant is sensitive: their disability, supports, funding, home address, sometimes…
Which privacy laws apply to you
Many small operators assume the Privacy Act's small business exemption (for businesses under $3 million annual turnover) lets them off. It usually does not. The Act treats organisations that provide a health service and hold health information as covered regardless of turnover, and disability support services generally fall inside that definition. In…
The data you hold — and why it is high-risk
Map what you actually store before you can protect it. A typical provider holds: participant name, date of birth, address and contact details; NDIS number and plan details; disability and diagnosis information; support notes and progress records; behaviour support or restrictive practice records; incident reports; bank or plan-manager details for invoicing;…
Consent, collection notices and your service agreement
You must tell participants what you collect and why at or before the point of collection — this is your collection notice or privacy notice. You need genuine consent to collect sensitive information and to share it with third parties such as plan managers, support coordinators, allied health professionals or the NDIA. Consent must be specific, current and…
Cyber security controls that actually reduce risk
You do not need an enterprise security team. A handful of controls prevent the large majority of small-provider breaches. Prioritise them in this order rather than buying tools you will not configure. If you outsource IT or use a managed provider, make these six the minimum you require in writing. Document who is responsible for each — that documentation is…
'Prove and pay' and the coming record-keeping shift
Digital payment reform changes how your data flows. The 'prove and pay' model, beginning July 2026 and rolling out to 2030, moves claiming from 'pay and check later' to real-time digital claiming with supporting evidence captured on every claim. That means more participant data moving through your systems more often, and stronger expectations that the…
When something goes wrong: breaches and reportable incidents
A data breach is unauthorised access to, disclosure of, or loss of information you hold — a hacked email account, a misdirected email, a lost phone, a spreadsheet sent to the wrong person. Under the Notifiable Data Breaches scheme, if a breach is likely to result in serious harm to any individual and you cannot prevent that harm, you must notify the OAIC and…
Choosing secure systems and vendors
Your privacy posture is only as strong as the software you run it on. When choosing your systems stack — CRM, case management, rostering, plan management — treat security as a selection criterion, not a nice-to-have. Ask each vendor where participant data is physically stored (Australian data residency avoids some complications), whether data is encrypted in…
Frequently asked questions
Does the Privacy Act apply to small NDIS providers under $3 million turnover?
Usually yes. The small-business turnover exemption generally does not apply to organisations that provide a health service and hold health information, and disability supports typically fall inside that category. Assume the Australian Privacy Principles apply to you and confirm the current threshold…
What is the difference between a data breach and an NDIS reportable incident?
A data breach concerns information — unauthorised access, disclosure or loss of data you hold — and is notified to the OAIC and affected individuals under the Notifiable Data Breaches scheme when serious harm is likely. An NDIS reportable incident concerns harm to a participant, such as abuse,…
How long do NDIS providers have to keep records?
Registered providers already have retention obligations under the Practice Standards, and the 'Securing the NDIS for Future Generations' Bill 2026 proposes a seven-year record-retention duty. That seven-year duty is Bill-dependent and not yet settled law, so confirm it against…
What security controls does an NDIS provider actually need?
Start with multi-factor authentication on every system, unique logins with access limited to the participants each worker supports, tested backups, device encryption and screen locks, automatic software updates, and basic phishing awareness. These six prevent most small-provider breaches. Document…
Do I need participant consent to share information with plan managers or the NDIA?
Yes. You need specific, current and freely given consent to disclose sensitive information to third parties such as plan managers, support coordinators, allied health professionals or the NDIA. Capture it in your service agreement and intake process, date it, keep it with the participant file, and…
Related guides
- NDIS Provider Software: Choosing Your Systems Stack
- NDIS Service Agreements: How to Write Them Right (With Template)
- NDIS Rostering Software: Building SCHADS-Compliant Rosters That Protect Your Margin
- Building an NDIS Roster of Care for SIL (Digital Submission)
- CRM & Case Management for NDIS Providers: What Your System Must Do
- The NDIS Client Intake Process: A Workflow That Protects Cash Flow and Compliance