Skip to main content

Autonomy Care is taking reviewed applications from NDIS providers. How applying works

Autonomy Care
Menu

Last updated 12 Oct 2026

What we do with your information, in plain words

Security, privacy, AI and accessibility in one place, including what isn't decided yet.

This page brings together how Autonomy Care handles security, privacy, AI and accessibility. Sensitive fields are encrypted, activity logs can't be edited, and two-step sign-in can be required. The worker app reads location only at set moments. Our checks follow fixed, written rules and use no AI. Where something isn't decided yet, such as hosting, we say so.

What's on this page?

  • Security

    Encryption, activity logs, sign-in, roles and how long records are kept.

  • Privacy

    What the worker app reads and when, who sees what, and our website.

  • AI and data use

    Which checks are rule-based, and the one AI add-on that is off.

  • Accessibility

    The standard we build to, how we test, and how to report a problem.

  • Not decided yet

    Hosting, backups, certifications and other open items.

How is sensitive information protected?

Sensitive fields are encrypted in the database with AES-256-GCM, using a key kept separate from the application key. They include NDIS numbers, dates of birth, medication and MAR details, progress note text and corrections, incident narratives and reviews, and complaint text. Exact NDIS number searches use a keyed index, so the number itself isn't stored in plain text.

Not every field is covered yet: form record contents, email addresses and log entries aren't field-encrypted. Stored files are private, and download links are signed and expire, by default after 60 minutes. Scheduled reports with personal details are sent as a link for each recipient that expires after 7 days or 10 downloads.

Can anyone change the activity log?

No. Each organisation has activity and sign-in logs, and the database refuses any change or deletion of audit rows, apart from the 7-year purge described below. Activity logs are hash-chained for each organisation, so a changed or missing row breaks the chain, and the chain is checked every day. Document records log every view and export, and signed documents keep a content hash and a certificate page. You can export the logs.

How do people sign in, and who can see what?

Two-step sign-in uses an authenticator app with recovery codes. Your organisation chooses whether it is off, optional (the default), required for admins or required for everyone, and an admin can reset it for a staff member. Staff can also sign in with Microsoft Entra ID or Google Workspace, required for admins or for all staff, while owners keep a separate password and two-step sign-in in case single sign-on fails. Single sign-on isn't available in the mobile app or for families, and SAML isn't supported.

Access is controlled by roles built from fine-grained permissions, and you can create your own roles. Each request is tied to one provider organisation, taken from the sign-in itself. Support workers see care information only, not plans or funding, and families see only what you allow for each contact.

How long are records kept?

Audit rows are kept for at least 7 years. Only a purge of rows older than that can remove them, and the 7-year cut-off is set in the database, so the app can't shorten it. Document Centre templates can't set a retention period under 7 years, and records destroyed at the end of retention are logged. Declined referrals are deleted after 90 days.

What does the worker app read on the phone, and when?

Location is read only at these moments:

  • once at clock-in and once at clock-out, when the organisation uses geofencing
  • once when a worker checks in or answers "Are you OK?", if they allow it
  • while a help request is open, for up to 30 minutes, only while the app is open, and the worker can stop it
  • when a worker taps "use my location" for an expense trip

There is no background or continuous tracking. The microphone is used only when a worker taps dictation, through the phone's own speech recognition; Autonomy Care doesn't record or keep audio, but Apple or Google may process it depending on the phone. Photos and files are read only when a worker chooses to attach them. Notifications on the lock screen don't show participant names.

Does this website track me?

No. The website uses no tracking cookies. Analytics, when switched on, is cookieless. Forms send what you type straight to our application, and the website itself stores nothing. We don't put personal details in web addresses. Read the cookie notice and privacy policy for the detail.

Can we get our information out?

Registers, the participant list, reports and many records export as CSV or PDF, and a participant's Document Centre file can be exported. An admin can also export everything held about one participant or staff member in a single download, to answer a request for access to personal information.

If your subscription ends, you keep read-only access for 30 days so you can export what you need, and if you ask during that time we'll send you a copy of your data in common formats, such as CSV and PDF. We then delete your organisation's data within 90 days, unless the law requires us to keep something longer. There's no fee to leave or to take your data with you.

You stay responsible for keeping your own NDIS records for as long as the rules require, such as 7 years for incident and complaint records, so export them before you go. Our terms of use summarise these terms, and your customer agreement with us governs.

Does Autonomy Care use AI on participant information?

Not unless you turn it on. The note coach, Signals, worker matching, incident triage, medication checks and the claim pre-check are rule-based. They follow written rules and use no AI model.

There is one optional add-on, AI note summaries. It is off in three ways: it isn't in the default modules, a platform switch keeps it off, and an organisation admin must also turn it on, which is written to the activity log. If all three allow it, a staff member can press "Summarise" on a progress note. The note's text is then sent to OpenAI, processed outside Australia, and a suggested summary comes back for the worker to check. Autonomy Care doesn't store the text sent, families can't use it, and each person can ask for 20 summaries an hour.

How accessible is Autonomy Care?

We build the website and the product to WCAG 2.2 level AA. We don't claim certification or an independent audit. Here is how we test:

  • the website's colour pairs are checked automatically on every build
  • the mobile app's colours are tested against WCAG 2.2 AA contrast, and its screens are tested at 200% text size
  • touch targets in the app are at least 48dp, and the app follows the phone's dark mode and reduce motion settings
  • app controls have screen-reader labels, including a "Send a silent alert" action
  • the Family portal has larger text sizes and Easy Read with illustrations

On 13/10/2026 we checked the web app's main screens with automated accessibility tests (axe, against WCAG 2.1 A and AA) at four screen widths, from phone to desktop, and worked through the six core lists using only a keyboard. We fixed what those checks found, such as pickers that needed a mouse and focus that was lost after closing a panel. A full run with screen readers (NVDA, VoiceOver and TalkBack) is still to be done.

How do I report an accessibility problem?

Tell us through the accessibility statement or the contact page. It helps to say which page or screen, what you were trying to do, and any assistive technology you use.

What isn't decided yet?

Some things aren't in place yet, and we won't claim them until they are:

  • Hosting provider and region.
  • Backups. The design is encrypted nightly backups kept daily for 35 days, monthly for 13 months and yearly for 7 years, but none are running until hosting is in place.
  • Sign-in time-outs. Idle sign-out times for the web app haven't been set yet.
  • Data breach response.
  • Sub-processors.
  • Certifications. We don't hold security certifications such as ISO 27001 or SOC 2.

What we do and don't claim

It does

  • Encrypts sensitive fields with AES-256-GCM
  • Keeps hash-chained activity logs that can't be edited, checked every day
  • Lets your organisation require two-step sign-in or single sign-on
  • Reads a worker's location only at set moments, never in the background
  • Uses rule-based checks, not AI, for the note coach, Signals and the claim pre-check
  • Builds to WCAG 2.2 AA

It doesn't

  • Doesn't yet state where data is hosted
  • Doesn't hold security or accessibility certifications
  • Doesn't send information to an AI service unless your organisation turns on the AI add-on
  • Doesn't field-encrypt form record contents or email addresses yet
  • Doesn't use tracking cookies on this website

Frequently asked questions

Where is our data stored?

Don't publish a location until it is in place.

Can we see who accessed or changed a record?

Yes. Activity logs record who did what and when, and can be exported. Document records also log every view and export. Logs can't be edited or deleted, and are hash-chained so tampering can be detected.

Do you support two-step sign-in?

Yes. Staff can use an authenticator app with one-time recovery codes. Your organisation can make it optional, required for admins, or required for everyone.

Can staff sign in with Microsoft or Google?

Yes. Single sign-on works with Microsoft Entra ID and Google Workspace using OpenID Connect. Your organisation can require it for admins or for all staff. The mobile app doesn't support single sign-on; workers sign in with a password, plus two-step sign-in if your organisation requires it or the worker turns it on.

Does any feature send our information to an AI service?

Only one, and it is off. The note coach, Signals, worker matching, incident triage and claim checks are rule-based and use no AI model. An optional AI note summary add-on sends a progress note's text to OpenAI, outside Australia. It is off by default and runs only if your organisation turns it on.

When does the app read a worker's location?

Only at set moments: once at clock-in and once at clock-out when your organisation uses geofencing, once when a worker checks in or answers "Are you OK?" (if allowed), while a help request is open (up to 30 minutes, and they can stop it), and for an expense trip if they tap "use my location". Never in the background.

Is a worker's voice recorded when they dictate a note?

Autonomy Care doesn't record or keep any audio. Dictation uses the phone's own speech recognition, set to Australian English, and only the words go into the note. Depending on the phone, Apple or Google may process the audio to turn it into text. Workers who'd rather not can type instead.

What participant information can support workers see?

Workers see the care information they need on shift: support needs, goals, medicines, alerts, contacts and handovers for the participants they support. They don't see plans, funding or plan managers. The NDIS number stays hidden until they tap Show, and search previews never show note or message text.

Is Autonomy Care accessible?

We design to the Web Content Accessibility Guidelines (WCAG) 2.2 AA and test with keyboard navigation. Read our accessibility statement and tell us about any barrier you find. On 13/10/2026 we ran automated accessibility checks (WCAG 2.1 A and AA) on the web app's main screens at four screen widths, and worked through the core lists using only a keyboard, then fixed what we found. A full check with screen readers is still to be done.

Can we get our data out if we leave?

Yes. Most registers and records can be exported as CSV or PDF while you are a customer, and an admin can export everything held about one participant or staff member in a single download. Form records are kept for at least 7 years while you use Autonomy Care.

If your subscription ends, you keep read-only access for 30 days so you can export what you need, and if you ask during that time we'll send you a copy of your data in common formats, such as CSV and PDF. We then delete your organisation's data within 90 days, unless the law requires us to keep something longer. There's no fee to leave or to take your data with you.

You stay responsible for keeping your own NDIS records for as long as the rules require, such as 7 years for incident and complaint records, so export them before you go. Our terms of use summarise these terms, and your customer agreement with us governs.

Got a question we haven't answered?

Ask us. If something isn't decided yet, we'll tell you that too.