Inclusi

Privacy policy

Draft for review, 12 November 2026. Inclusi is a product of All Access Studio Pty Ltd (ABN 22 698 543 109, ACN 698 543 109). Registered office: 240 Iodide Street, Broken Hill NSW 2880.

This policy explains how All Access Studio Pty Ltd (ABN 22 698 543 109, ACN 698 543 109; "we"), the company that makes Inclusi, handles personal information under the Privacy Act 1988 (Cth) and the Australian Privacy Principles. Inclusi serves organisations in Australia only.

Two kinds of information

Our customers' records. Providers (NDIS providers, aged care and home support providers, allied health practices and plan managers) use Inclusi to keep records about participants, clients and workers. These records include health and disability information, information about children, and worker screening outcomes. We handle this information on behalf of the provider, only to provide Inclusi to them and as our agreement with them says. We do not use it for our own purposes, except to count usage for billing and to run, secure and improve Inclusi using information about how features are used, which never includes the content of records. We do not sell it or use it to train AI models. The provider decides what is collected and why and is responsible for telling people about it; we keep it secure and help the provider meet its obligations. If you are a participant, client or worker, contact your provider first about your records. If you contact us, we pass your request to the provider within 2 business days and tell you we have done so.

Information about our own users and enquirers. Names, emails and details you give us when you enquire, book a demo, start a trial or use Inclusi. We are responsible for this information.

What we collect about our own users and enquirers, and why

  • When you enquire, book a demo or start a trial: your name, work email, phone number, organisation, and for a trial its ABN and Australian business address, the programs you deliver and your message. We check the ABN on the Australian Business Register (ABN Lookup). We use it to reply, set up your workspace and, only if you ticked the box, send product news.
  • When you use Inclusi: your name, email, sign-in and two-factor details, the roles you hold, and the IP address and browser of each sign-in and of the actions recorded in the audit log. We use it to run the service, keep it secure and show your organisation what was done and by whom.
  • When your organisation pays: billing contact and plan details. Card details are handled by our payment processor, Pin Payments, an Australian company; we do not see or store full card numbers. Pin's privacy policy allows it to send information to the United Kingdom, New Zealand and the United States, so your billing contact details may go there.
  • If you turn on error reports in the Inclusi app: technical details of the error, with names, emails, numbers and quoted text removed.
  • On our website: page view counts without cookies or personal data. Signing in uses a cookie that keeps you signed in (cookies and analytics).

We do not ask our own users or enquirers for sensitive information. If you do not give us a contact email we cannot reply to you or open a workspace. You can enquire without giving your name, but we may not be able to help as well.

Collection notice

All Access Studio Pty Ltd, the company that makes Inclusi (privacy@inclusi.com.au), collects your name, work email, password, phone, your organisation's name, ABN and Australian address and the programs it delivers, to open and run your workspace, check you are an Australian business, bill your organisation and, only if you tick the box, send product news. We check the ABN on the Australian Business Register, which tells us the business name and status. No law requires you to give us this, but without it we cannot open a workspace. We disclose it only to the services that run Inclusi (listed in our privacy policy) and as the law requires. Some of it may be handled outside Australia by: Pin Payments (Australian company. Pin does not publish where it hosts data, and its privacy policy allows disclosure to the United Kingdom, New Zealand and the United States, so billing contact details may go there). Our privacy policy explains how to see or correct your information and how to complain.

What we do not do

  • We do not sell personal information.
  • We do not use customers' care records to train AI models, and the AI services we use may not either.
  • Our website does not use advertising trackers. We count page views without cookies or personal data.
  • Inclusi is not connected to My Health Record and does not access or store My Health Record information.

Where it is stored and who else handles it

Customer records, documents and backups are held in Australia. We do not send personal information overseas. The services we use to run Inclusi process it in Australia. An email you receive can still pass through your own mail provider's servers, wherever they are. We use these services only to provide Inclusi, under written terms that require them to keep the information secure. Before we add or replace a service that handles customer records, we give our customers 30 days' notice.

ServiceWhat it doesHealth informationWhere
Amazon Web Services (application and database hosting)Runs the Inclusi application and its Postgres database.YesAustralia: AWS Sydney (ap-southeast-2), with backups kept in Australia.
Amazon Web Services (S3, Sydney)Stores uploaded documents.YesAustralia, on the application server's own disk.
Amazon Web Services (Amazon SES, Sydney)Sends sign-in, invitation, notification and reply emails.NoNot configured.
Amazon Web Services (Amazon Bedrock, Sydney), running Anthropic's Claude modelsDrafts progress reports, summaries and notes when an organisation switches the AI assistant on, turns staff questions into report queries (Ask Inclusi), and transcribes scanned invoices for plan managers who turn that on.YesAustralia: Sydney and Melbourne (an "au." inference profile; profiles that can leave Australia are refused).
A speech-to-text server Inclusi runs in AustraliaTurns worker voice notes into text when the phone cannot, if the organisation turns server transcription on.YesAustralia (Sydney).
An OCR server Inclusi runs in AustraliaReads text from scanned or photographed provider invoices when a plan manager turns it on.YesAustralia (Sydney).
Amazon Web Services (Amazon SES email receiving, Sydney)Receives provider invoices emailed to an organisation's Inclusi address and passes them to Inclusi.YesAustralia (Sydney).
Pin Payments (Southern Payment Systems Pty Ltd, Melbourne; a Fat Zebra company)Takes subscription payments from organisations.NoAustralian company. Pin does not publish where it hosts data, and its privacy policy allows disclosure to the United Kingdom, New Zealand and the United States, so billing contact details may go there.
Mobile Message Pty LtdSends shift and appointment reminders, open shift offers and replies by text, when an organisation turns SMS on.NoAustralia: Mobile Message states its platform and backups are in Sydney (DigitalOcean Sydney) and texts go straight to Australian carriers.
Google Firebase Cloud Messaging, and Apple Push Notification service for iPhonesDelivers push notifications to the Inclusi and Inclusi Family apps, for organisations that turn push on.NoUnited States (unavoidable: phones receive notifications only through Apple and Google).
MYOB Australia Pty Ltd (the organisation's own MYOB)Sends invoices and reads payments when an organisation connects MYOB.NoAustralia (MYOB states its online files are on Microsoft Azure in Australia; confirm in MYOB's terms).
Employment Hero Pty Ltd (the organisation's own Employment Hero Payroll)Sends approved timesheets and reads pay runs and leave balances when an organisation connects it.NoAustralia (Employment Hero states its data and backups are on servers in Australia).
Tyro Health Pty Ltd (formerly Medipass)Medicare, DVA and health fund claims for allied health practices that connect it.YesAustralia (Australian company; its API is the Australian region, api-au.medipass.io; confirm hosting in the partner agreement).

How we keep it secure

Each organisation's records are separated in the database, access inside an organisation is limited by role, health and clinical information needs extra permissions, and every action is recorded in an audit log that cannot be quietly changed. Every opening of a person's record is logged, and providers can see who opened records of people they had no shift, caseload or team link to, and can require staff to give a reason first. Our support staff can see a customer's records only when the customer approves, read-only, for up to 72 hours. The security page has more detail.

How long we keep information

  • Enquiries and demo requests: 2 years after you contact us, then we remove your details. We keep them longer only while your organisation is a customer or you are still subscribed to product news. If you unsubscribe we keep your email address on a do-not-send list so we never email you again.
  • User accounts: while your organisation uses Inclusi. The audit log of what you did stays with your organisation's records.
  • Billing records: 5 years, as tax law requires.
  • Customers' records: as the provider instructs. Health records laws generally require providers to keep health information for 7 years after the last service, or until a person is 25 if it was collected while they were under 18 (Health Records and Information Privacy Act 2002 (NSW) s 25; Health Records Act 2001 (Vic), Health Privacy Principle 4; Health Records (Privacy and Access) Act 1997 (ACT)). NDIS incident, complaint and worker screening records are kept for 7 years, and aged care records for 7 years after a provider stops being registered. Inclusi's retention tools work out these dates and never delete health records on their own: a person approves and a second person de-identifies, and a record of the disposal is kept.
  • When a customer asks us to close its account: an owner asks in Inclusi (Settings) and can cancel at any time in the next 90 days. Its records stay available, read-only, for those 90 days so it can export them; we then delete them within 30 days unless the customer asks us to return them another way or the law requires us to keep them, and email its owners a deletion certificate. We keep our own billing records about the customer (tax invoices, for 5 years). Copies in our encrypted backups are deleted as the backups expire, within 35 days. Backups are only ever used to restore the service, and we keep a record of every deletion and de-identification outside the database: if we ever restore a backup, we apply them again before the restored records are used.
  • Documents: when a provider de-identifies a person's records at the end of their retention period, the files stored with them are deleted too, unless they are on legal hold.
  • Questions typed into Ask Inclusi: kept with the names and numbers removed, so the provider can see how the feature is used.

State health records laws

Providers in Victoria, New South Wales and the Australian Capital Territory also have duties under the Health Records Act 2001 (Vic), the Health Records and Information Privacy Act 2002 (NSW) and the Health Records (Privacy and Access) Act 1997 (ACT), including for access to and correction of health records, and for telling people and passing on their records when a practice closes or is sold. Inclusi's privacy tools follow the shorter of the time limits these laws and the Privacy Act set, and prepare the notice letters and the transfer of records to another provider. You can complain about the handling of health information to the Health Complaints Commissioner (Victoria), the Information and Privacy Commission NSW or the ACT Human Rights Commission, as well as to the OAIC.

Automated decisions

From 10 December 2026 the Privacy Act requires us, and providers using Inclusi, to explain where a computer program makes, or does something substantially and directly related to, a decision that could significantly affect someone. A person checking the result does not take a feature outside these rules, so we list every feature that may be covered. Providers choose how they use these features and describe them in their own privacy policies; participants and workers can also see this list in the Inclusi app.

Made by the program alone

  • Rostering checks that stop an assignment. Prevents a worker being put on a shift when a mandatory credential, worker screening clearance or Working With Children Check is missing or expired, a screening check shows an interim bar, suspension or exclusion, a high intensity support competency is missing, the worker is not active, a restriction applies, or the shift would clash with another. It uses: Credential and screening records, worker status, restrictions, existing shifts and leave. People record and verify the credentials and restrictions the check relies on. The check itself cannot be overridden.
  • Removal from upcoming shifts after a screening exclusion. When a worker screening outcome recorded for a worker is an interim bar, suspension or exclusion, takes the worker off every shift that has not started, ends any open risk-assessed role, and tells schedulers and the worker (without the reason). Shifts already under way are listed for a person to act on. It uses: The worker screening outcome (which can be derived from criminal history), the worker's upcoming shifts and risk-assessed roles. A person with permission to verify credentials records the outcome from the screening unit. The removal then happens straight away, with no further review, because the law does not allow the worker to keep working in a risk-assessed role.
  • Plan-managed invoice checks. Checks a plan-managed invoice against the price guide, the participant's plan, dates, the NDIS 90-day claim time limit and the provider's ABN. Errors stop the invoice being submitted until fixed; a line past the claim time limit can go ahead only when a person records exceptional circumstances; warnings must be acknowledged. It uses: Participant plan and budget details, invoice lines, provider details. People correct the invoice or the records the check relies on; a person approves every invoice that passes.
  • Open shift offers and first-come claims. Offers a vacant shift to workers who pass the rostering checks. In first-come mode the first eligible claim with no warnings is assigned straight away; claims with warnings, and every claim in approval mode, wait for a coordinator. It uses: Worker status, credentials, availability, hours and existing shifts. A coordinator chooses the mode and who is offered the shift; first-come assignments can be reversed by a coordinator.
  • Waitlist offers for freed appointments. When an appointment is cancelled, offers the time to clients on the practice's waitlist who asked for that kind of appointment, in waitlist order, and books the first one who accepts. It uses: Waitlist entries (client, appointment type, practitioner and times wanted), contact details for the offer. This can include health information. The practice chooses whether the waitlist is on, how many people are offered each time and for how long. Staff can book or move anyone by hand.
  • Sign-in protection. Locks an account for 15 minutes after 5 failed sign-ins, and withholds privileged permissions when an organisation requires two-factor and it is not set up. It uses: Sign-in attempts, account security settings. An administrator can reset access.

A program helps a person decide

  • Suggested workers and rostering warnings. Lists workers who can take a shift and shows warnings (hours limits, travel distance, breaks between shifts, preferences, past shifts with the participant). It uses: Worker availability, skills, languages, gender, home postcode or location, hours, past shifts; participant preferences and restrictions. A scheduler chooses the worker. Accepting a warning needs roster override permission and a reason, which is audited.
  • Suggested order and times for a worker's day. Suggests an order and start times for one worker's shifts that cut travel, moving only shifts that have a window, and checks the suggestion against the rostering checks above. It uses: The worker's shifts, home location if recorded, participant locations, availability and leave. A scheduler reviews and accepts the suggestion; nothing changes until they do. Accepting a warning needs roster override permission and a reason.
  • Compliance signals and credential expiry alerts. Flags missing or expiring worker credentials, overdue reviews and open requirements, and can notify the worker and managers. It uses: Worker credentials and expiry dates; requirement status. Managers decide what to do. An expired mandatory credential also triggers the rostering block above.
  • Funding and plan alerts. Alerts staff when a participant's funding budget reaches a threshold or a plan or service agreement is ending. It uses: Funding plans, budgets, invoices and agreement dates. Staff review funding with the participant. Inclusi does not stop or change supports.
  • Reportable incident suggestions. From answers a person gives, suggests whether an incident may be reportable to the NDIS Commission or under the aged care SIRS, and the category and deadlines. A use of a restrictive practice logged as unauthorised opens an incident with the suggestion already filled in. It uses: Incident details about participants and workers, which can include health information. This can include health information. An authorised person decides and records why. Disagreeing with the suggestion is recorded, not blocked.
  • AI-drafted progress reports and incident summaries (uses AI). Drafts text from selected records using a large language model, citing the records it used. It uses: Shift notes, goals, incident records and other selected records, which can include health information. This can include health information. A qualified person reviews, edits and accepts the draft and takes responsibility for it. The assistant is barred from clinical, regulatory and employment decisions.
  • Reading provider invoices for plan managers (uses AI). Reads the fields of a provider invoice (from the PDF text, or from a scan by OCR or the AI assistant when turned on), matches the provider and participant, and gives each field a confidence. It uses: Invoice details: participant name and NDIS number, supports delivered, dates and amounts. This can include health information. A plan manager checks every field against the invoice and confirms before an invoice is created; approval and payment are separate human steps.
  • NDIS claiming and cancellation rules. Works out claimable amounts, including whether a short-notice cancellation can be charged, from the versioned NDIS pricing rules, and the last day each support can be claimed (90 days from 1 December 2026). A line past that day cannot be issued or claimed unless a person records exceptional circumstances. It uses: Bookings, cancellations and notice times, funding and agreement details. Staff review invoices and claim files before they are issued or uploaded.
  • Check that a line is an NDIS support. Reads the words a provider or plan manager typed for an invoice line and flags ones that look like supports the NDIS Act s 10 and the NDIS Supports Rules exclude (for example day-to-day living costs or holidays). Some can never be claimed and are errors; others are warnings a person checks. It uses: Invoice line descriptions about the participant's supports, the unit and any replacement support determination recorded. This can include health information. A person decides: they correct the line, record that it is an NDIS support with a reason, or record a replacement support determination. Each choice is recorded with who made it.
  • Registration check for supports that need a registered provider. Stops a provider claiming supported independent living (class 0138) or specialist behaviour support (class 0110) items unless its NDIS registration number, and any registration classes it recorded, cover them. It uses: The organisation's registration details and the invoice line's support item; the participant's invoice. A person fixes the organisation's registration details or removes the line; nothing is claimed without a person issuing the invoice.
  • Pay calculation from award rules. Calculates pay lines (penalties, overtime, allowances, leave) from timesheets and the organisation's award rule set, with a trace for every line. It uses: Timesheets, employment type, classification, pay rates and leave. A named payroll specialist validates each rule set; managers approve timesheets before export.
  • Fill unfilled shifts (proposal). Proposes a worker for each open shift from the rostering checks and the recommendation score (continuity with the participant, preferences, distance), with reasons. It uses: Worker availability, skills, home location, hours and past shifts; participant preferences. A scheduler accepts or changes each proposal. Workers with a hard stop are never proposed.
  • Clock-in location and time checks. Compares where and when a worker clocks in or out with the shift's address and times. A clock event outside the expected area, or early or late, is flagged, and the timesheet cannot be approved until a coordinator reviews it or the approver records why they are going ahead. It uses: The phone's location and its accuracy at the clock event, the time, the shift address and times. A coordinator accepts, queries or does not accept each flagged event and records a note. The worker can give a reason when clocking in or out.
  • Care signals found in shift notes (uses AI). Flags shift notes whose words may describe a risk (falls, hospital, injury, choking, a missing person, restraint with no recorded use, missed medication), by fixed rules and optionally an AI model, for a coordinator to decide. It uses: Shift note text, which can include health information, and (for the fixed rules only, never sent to an AI model) restrictive practice use records. This can include health information. A coordinator decides each flag: dismiss with a reason, follow up, or make an incident or corrective action. Every decision and dismissal is recorded.
  • Observation range alerts. Compares each recorded observation with the range a clinician set for the person and raises an alert when it is outside. It uses: Observations (vital signs, blood glucose, weight, bowel, fluids, seizures, sleep) and the person's ranges. This can include health information. A clinician sets the ranges; the clinical team decides what to do with an alert.
  • AI scribe for allied health consultations (uses AI). Turns a consultation transcript into a draft clinical note for the practitioner to edit and sign, after the client agrees. It uses: The consultation's words, which include health information. This can include health information. The practitioner edits and signs the note; the draft is never signed by itself. A clinical note is a key input to clinical decisions, so the practitioner checking it does not take it out of scope.

Drafting help

  • AI draft of a worker's own shift note (uses AI). Drafts a shift note from the worker's own notes and the shift's clock events. It uses: The note text. This can include health information. The worker accepts or rejects the text.
  • Ask Inclusi typed questions (uses AI). An AI model turns a staff member's typed question into one of Inclusi's defined measures, a period and filters; Inclusi checks it against the person's access and calculates the answer. The model sees the question only, never records or results. It uses: The question as typed (it can name a participant, worker or branch). The answer is calculated from records the person may already see. Management information only: the person sees exactly which measure and filters were used and decides what to do with the numbers.
  • Demand forecast. Estimates the organisation's total worker-hours needed by week, day and time band from its own roster history. It uses: Roster history, counted in total (no individual is assessed). Planners use the estimate; it changes nothing by itself.
  • Voice note transcription (uses AI). Turns a worker's spoken shift note into words, on the phone where possible and otherwise through a transcription service when the organisation turns it on. It uses: The recording, which can name participants and describe their health and support. This can include health information. The worker reads, edits and saves the note.
  • AI assistant connector (an assistant the provider chooses). Inclusi makes no decision. If a provider connects an AI assistant it has chosen, that assistant can read records through a key with limited permissions, and the provider decides what it uses the assistant for. It uses: Whatever the key allows the assistant to read, which can include health information. Restricted fields are never sent. This can include health information. The provider chooses the assistant and what it can read, and is responsible for any decision it uses the assistant for.
  • Shift note checklist and AI note coach (uses AI). Lists what a shift note looks to be missing against the organisation's checklist and the participant's own items; optionally an AI model asks questions about missing detail. It uses: The draft note, goal titles, whether the person has medication, the shift's tasks. This can include health information. The worker decides what to write.
  • Handover summary before a shift (uses AI). Builds a summary of recent notes, alerts, medication changes and plan reminders for the worker starting a shift; optionally an AI model writes a short version. It uses: Recent shift notes, alerts, medication changes and (in the fixed summary only, never sent to an AI model) behaviour support strategies, which include health information. This can include health information. The worker reads it with the records; it is not saved as a record.

Decisions we make about our own customers and users

These are decisions we make, using computer programs, about organisations that sign up and the people who use Inclusi. Most of our customers are organisations, but a sole trader is a person, so we list them.

  • Whether a new organisation can open a workspace (made by a program alone). A sign-up is refused straight away if the ABN is not on the Australian Business Register or is cancelled, or the address or phone number is not Australian. Anything the program cannot confirm waits for a person at Inclusi. It uses: The ABN, business name, address and phone number given at sign-up and what the Australian Business Register says about the ABN (for a sole trader, this is information about them). Email hello@inclusi.com.au and a person will check the refusal and the ABN record with you.
  • Moving an account to the Free plan or to read-only (made by a program alone). At the end of a trial the account moves to the Free plan if it fits, or becomes read-only. An account over the Free plan limit for longer than the grace period, or with a payment still unpaid 14 days after it first failed, becomes read-only. Nothing is deleted then. After 12 months read-only for non-payment or cancellation, owners are emailed 90 and 30 days ahead and the standard account closure starts (90 more days read-only, then deletion). It uses: The account's plan, trial dates, payment status, and the number of active participants and users (counts only). An owner can choose a plan at any time, or ask to keep the account in Settings, Subscription; email us and a person will look at it.
  • AI drafting allowance (made by a program alone). Drafts over the monthly fair use allowance are counted and charged at the published overage price per draft. It uses: The number of AI drafts the organisation has made this month and its plan. Email us and a person will check the count.
  • Locking an account after failed sign-ins (made by a program alone). An account is locked for 15 minutes after 5 failed sign-ins (wrong password or two-factor code) without a successful one. It uses: Sign-in attempts and the account's security settings. Wait 15 minutes, reset your password, or ask your organisation's administrator.
  • Checks on sign-ups that wait for a person (a program helps a person decide). The program lists why a sign-up could not be confirmed, so a person at Inclusi can decide. It uses: The same sign-up details and the ABN Lookup result. A person decides; email us to ask about the decision.

Each time a provider's staff member chooses differently from what one of these features suggested, Inclusi records it, so the provider can show that a person made the decision. Ask us or your provider if you want to know more about a decision. How Inclusi uses AI and automation explains each feature in plain English.

Access, correction and complaints

You can ask for the personal information we hold about you, and ask us to correct it. There is no charge for asking. We respond within 30 days. We check your identity first. If we refuse, we tell you why in writing and how to complain; if we do not correct information, you can ask us to keep a statement with it saying you think it is wrong, and we will. If you ask, we will tell anyone we gave the information to about a correction.

To ask, or to complain about how we handled your information, email privacy@inclusi.com.au. We will acknowledge your complaint within 5 business days, look into it and reply in writing within 30 days. If you are not satisfied with our response you can contact the Office of the Australian Information Commissioner (oaic.gov.au, 1300 363 992). Our complaints page lists other places you can go. You can write to us at our registered office: 240 Iodide Street, Broken Hill NSW 2880.

Who we disclose it to

The services listed above, only to provide Inclusi; your own organisation (its administrators can see what you did in Inclusi); and anyone the law requires or allows, such as a court order. We do not disclose it for anyone else's marketing.

Marketing

We only send product news if you asked for it, and every message has a link to unsubscribe. We act on unsubscribes straight away, and always within 5 working days.

Data breaches

How we respond to a data breach. If a breach involves our own users' information, we assess it within 30 days and notify affected people and the OAIC if it is an eligible data breach under the Notifiable Data Breaches scheme. If it involves a provider's records, we tell the provider within 48 hours of becoming aware of it, help them work out what happened and who is affected, and agree with them who notifies. Usually the provider notifies, because it has the relationship with the people affected; one notification covers both of us.

Changes to this policy

We update this policy when what we do changes, and show the date at the top. We tell customers by email before a change that affects how we handle their records.