Is ChatGPT Safe for NDIS Participant Data? What Providers Need to Know
Whether NDIS providers can use AI tools without breaching privacy obligations, and the de-identification rule that makes it safe.
On this page
Somewhere in your organisation right now, someone is probably pasting something into ChatGPT. A support worker drafting a progress note. A coordinator summarising a report. You, tidying up an email to a plan manager. AI tools are too useful for busy people to ignore, and pretending your team isn't using them doesn't make it true.
So the real question is whether the way you're using AI would survive scrutiny from a participant's family, the NDIS Quality and Safeguards Commission, or an auditor. Here's the honest picture.
The short answer
AI tools like ChatGPT and Claude are safe for NDIS work under one condition: no participant-identifiable information ever goes into them. No names, no addresses, no NDIS numbers, no dates of birth, no photos, no combination of details that could identify a person.
That one rule is what makes it safe. "Write a progress note about Jane Nguyen's shift at 14 Smith Street" is a privacy problem. "Draft a progress note for a participant who attended a community access shift, engaged well for the first hour, then became fatigued" is not. The AI writes the same quality note either way. The identifying details get added afterwards, inside your own systems, by your own people.
Providers who work this way get the benefit of AI without the exposure. Providers who don't are making disclosures they can't take back.
Why this matters legally
NDIS providers sit under two overlapping frameworks here:
- The Privacy Act 1988 and the Australian Privacy Principles. Participant information is personal information, and health and disability information is generally treated as sensitive information, which attracts stricter handling requirements under the APPs. Typing it into a third-party AI tool is a disclosure. If that tool stores data overseas, the cross-border disclosure rules apply on top. "I was just drafting a note" is not a defence.
- The NDIS Practice Standards. Registered providers must protect participant privacy and dignity, and manage information properly. An auditor who asks "how do you control what goes into AI tools?" is asking a Practice Standards question, and "we don't really know" is the wrong answer to give during a recertification audit.
One important nuance: no AI tool is "compliant" or "non-compliant" on its own. Compliance lives in how your organisation uses the tool. The same ChatGPT account can be used perfectly safely or recklessly on the same afternoon.
What actually happens to what you type
Where does your text go once you hit enter? It depends heavily on which plan you're on:
- Consumer plans (the free and personal paid tiers most people use) may use your conversations to train future models unless you find the setting and opt out. Treat the default as "assume it may be kept and used".
- Business and enterprise tiers generally do not train on your data by default and offer stronger contractual protections. This is why "which plan are we on" is a genuine compliance question, not an IT detail.
- Where the data lives matters too. Most major AI tools store data overseas. That's manageable, but it's exactly the kind of thing you should know and be able to say out loud before an auditor asks.
The practical conclusion: even on a well-configured business plan, the de-identification rule stays. It's the difference between a system that depends on vendor settings staying favourable and one that's safe regardless.
Safe vs not safe: the practical list
Safe with de-identified content
- Drafting progress notes, shift notes and incident report narratives ("the participant", "P1", "the worker")
- Summarising your own policies, or drafting new ones
- Writing emails, letters and service communications before names are added
- Preparing audit evidence descriptions and continuous improvement notes
- Building templates: intake checklists, onboarding packs, meeting agendas
Never, on any plan
- Pasting anything containing participant names, addresses, NDIS numbers or dates of birth
- Uploading participant files, plans, medical reports or photos
- Entering worker screening details or HR records
- Letting AI make care decisions, risk assessments or anything touching mandatory reporting: those are human judgement, full stop
How to make this stick: the four-part setup
A rule that lives in your head isn't a system. Here's the minimum that makes AI use defensible:
- A written AI-use policy. One page is enough: the de-identification rule, the approved tools list, human review before anything is sent or filed, and what to do if identifiable data goes in by mistake (stop, tell the manager, record it). Our free AI policy template is a plain one you can copy and adapt.
- Worker sign-on. Every worker and subcontractor signs the policy. This is what turns "we have a rule" into evidence.
- An automation register. A simple list of every AI tool and automation in use, who owns it, what data it touches, and how to switch it off. Auditors respond well to this because almost nobody has one. If any of those tools recommend or make decisions about participants, our automated decision making privacy policy checklist shows what else to record before 10 December 2026.
- Human review, always. AI output is a draft. A person checks every note, letter and report before it becomes a record. This is both good practice and your protection against AI's habit of confidently making things up.
If you want the deadline side of compliance handled with the same discipline, see our guide to how NDIS providers stop missing compliance deadlines: it covers the obligations register method and includes a free template.
The upside once the rules are in place
None of this is a reason to avoid AI. Once the rules are in place, providers can use AI with confidence for the jobs it does well: drafting, summarising, template building and audit preparation. The admin load in NDIS work is real, and those jobs are a big part of it. The full picture of what's worth automating is in our complete guide to AI and automation for NDIS providers.
At Workvolve we build this properly for NDIS providers: the AI-use policy, AI assistants that use participant codes instead of names, and the automations around them. For one NDIS provider we set up four of these Claude assistants: one for shift notes, one to keep the obligations register current, one for regulator replies and one for an "are we audit ready?" check. Each one only ever produced drafts for a person to review. You deal with Ben, the founder, from the first call to handover. The price is fixed in writing before work starts, everything runs in your own accounts, and you own all of it. If you want a clear starting point, our free 30-minute call will tell you what's safe to do first in your setup.
Common questions
How do you price a build?
Every build gets one fixed price in writing, after the free call or the audit and before any work starts. The number depends on how many systems are involved and how much logic sits between them, and there is no hourly meter or revised estimate halfway through. For NDIS providers, the common starting point is one painful process rather than everything at once.
How long does a build take?
It depends on the scope, and you get a firm date in writing before you commit. We would rather give you an honest date than a fast one we miss.
What problem does this actually solve?
The usual trigger is staff pasting participant details into public AI tools. We write the AI-use policy, set up AI tools that work from de-identified details, test them with the people who will use them, then hand it all over with documentation and walkthroughs.
Do we own the automation once it is built?
Yes, once it is paid for. It is built in your own accounts under your own credentials from day one, and the code, workflows, documentation and credentials are all handed over at completion. There are no licence fees, no lock-in, and nothing stops working if we stop working together.
What tools do you build with?
Mostly n8n for workflow automation, the Claude and OpenAI APIs for anything with AI in it, and Next.js with Supabase when a build needs a real interface. We connect to whatever you already run: CRMs, accounting, job management, Microsoft 365 and Google Workspace.
Do you work with businesses outside Brisbane?
Workvolve is based in Brisbane and works with businesses across Australia. All delivery happens remotely, over video calls and in your own accounts, so being interstate makes no difference to the build.
