ChatGPT and NDIS data: a practical privacy checklist for providers

A business account is helpful, but it is not the whole privacy assessment

OpenAI states that it does not train its models on business data from ChatGPT Enterprise, ChatGPT Business or its API by default. That is an important control. It does not, by itself, answer every Australian privacy, security, retention, access or data-residency question for an NDIS provider.

Before staff use any AI service with real organisational data, the provider should understand what information will be sent, why it is necessary, where it may be processed, who can access it, how long it is retained and how errors will be handled. Overseas processing is particularly relevant under Australian Privacy Principle 8.

The pre-use checklist

1. Purpose: Document the specific task and why AI is needed. Avoid open-ended ‘use it for anything’ access.
2. Data: Classify the fields involved. Start with general business information and synthetic or de-identified test cases.
3. Vendor: Review the exact product tier, contract, training policy, retention controls, subprocessors and available processing regions.
4. Access: Use organisation-managed accounts, single sign-on where available, least-privilege connectors and prompt staff offboarding.
5. Human review: Name who checks the output before it becomes a record, message, claim or action.
6. Logging: Record the workflow version, approvals, failures and material changes without creating a new uncontrolled copy of sensitive data.
7. Response: Add the AI workflow to the organisation’s incident and data-breach response process.

What staff guidance should say

A short acceptable-use rule is easier to follow than a dense policy. It should identify approved accounts and workflows, prohibit unapproved connectors, explain what data is excluded, require fact-checking and make clear that staff remain accountable for final actions.

• Do not paste participant names, NDIS numbers, health information, clinical details, behaviour-support content or incident details into an unapproved AI workflow.
• Do not assume an enterprise label means Australian-only processing.
• Do not rely on an output just because it sounds confident; compare it with the authoritative source.
• Report unexpected disclosure, incorrect actions or suspicious access through the normal incident channel.

Data residency is a separate question

Security, privacy, model-training policy and data residency overlap, but they are not identical. A service can have strong enterprise security and a no-training commitment while still processing some data outside Australia. If an organisation requires Australian-only processing, confirm that requirement contractually for the exact product and architecture before deployment.

The practical takeaway

Begin with managed business accounts and low-risk data. Treat sensitive-data access as a later governance decision, not a default feature. The organisation—not the software label—must decide whether the proposed use fits its privacy obligations and risk appetite. Obtain legal or privacy advice for higher-risk deployments.