Acceptable Use
Effective 14 November 2026 · Version 1.6
This Acceptable Use Policy ("AUP") describes what is and is not permitted on Accorda (the "Service"). It supplements the Terms of Service. Violation of this AUP may result in suspension or termination of your account and, where appropriate, referral to law enforcement.
In this policy, "you" means any user of the Service, whether an administrator, end-user, or other authorised person from a Customer Organisation that has subscribed to the Service.
You must use the Service only for lawful purposes and in compliance with all applicable laws, including (without limitation) Australian privacy law, anti-spam law, intellectual property law, and the laws of any other jurisdiction relevant to your use.
You may use the Service only if you are an authorised representative of a Customer Organisation, or have been invited to the Service by such a representative. You must not:
Each individual user must have their own account.
The Service is designed for storing your organisation's compliance documentation, including (without limitation):
Accorda is not designed as a system of record for personal information about your end-customers, clients, patients, service recipients, or other third parties, *except* as necessary for incident and corrective action records, and within the Funding planner and Service agreements module as described below. You must not upload to the Service:
Incident records and attachments: The Service includes an incident management feature for recording and tracking incidents and corrective actions. Incident records are permitted and are considered part of your compliance documentation. However, incident records may involve or reference events affecting your clients, patients, service recipients, or other vulnerable individuals. When recording such incidents, you must ensure: (1) you have a documented lawful basis for collecting and recording the incident information under Australian privacy law and any other applicable law, (2) where required by law, you have obtained appropriate consent from the affected individual or their guardian/representative, (3) the incident information is necessary for the stated compliance, incident management, or safeguarding purpose, and (4) any attachments to incidents (such as photographs, video, or documents) do not contain identifiable information about vulnerable individuals unless absolutely necessary and you have explicit lawful basis and consent. If your incident records frequently contain sensitive information about vulnerable individuals, consider whether a more specialised system (such as a clinical incident management system, safeguarding management system, or case management platform) is more appropriate than a general compliance platform.
If a compliance document must reference an individual as an example (for example, an incident response procedure that includes a worked example), de-identify or anonymise the example before uploading. This is distinct from operational incident records, which are permitted if you have lawful basis.
This restriction protects both your end-customers and your organisation. The Service is not certified as a clinical record-keeping system, safeguarding management platform, NDIS participant case management or records system, or similar regulated data system, and should not be used as a substitute for them. This stays true when you use the Funding planner and Service agreements module: that module supports funding planning, service agreements, and their signing only, and is not your participant record.
Funding planner and Service agreements: This optional module is available only to NDIS registered providers and is off until one of your administrators switches it on. While it is on, and only inside the module, you may record the personal information of NDIS participants and their representatives (such as parents, plan nominees, and guardians) that is needed to plan a participant's NDIS funding, to prepare and manage a service agreement with them, and to collect electronic signatures on that agreement. This is a limited exception to the restriction above. It does not allow you to use any part of the Service, including this module, as a participant case file, progress-note, care-planning, or clinical system. When using the module, you must:
You remain responsible for the content of your service agreements and for keeping any records you are required to keep (see the Terms of Service).
Worker screening and credential records: The Service includes features for recording the screening and credential status of your own workers, contractors, and volunteers (for example, national police checks, Working with Children Checks, NDIS Worker Screening, and professional qualifications). These records are permitted and form part of your compliance documentation. When using them, you must have a lawful basis to collect and record the information, obtain any consent required by law, and record only what is necessary for the compliance purpose, such as the type, status, and expiry of a check and any certificate you are required to retain. Do not upload underlying criminal-history material beyond what is necessary to evidence the clearance.
CPD records: Where your organisation has switched on CPD (continuing professional development), each person keeps a record of their own learning, with reflections and evidence. These records are permitted. They are about your own learning, not about the people you support. You must not put the names, personal information, or health information of clients, patients, or participants into a CPD entry, reflection, or upload. If you write about a case, de-identify it first: leave out names, dates of birth, addresses, and any other detail that could identify the person, and check certificates and other files before you upload them. If client details go in by mistake, edit them out straight away and tell your administrator. Earlier versions, removed entries, and removed files are kept, so your administrator should ask us to delete them. Administrators and managers who add CPD for someone else must record only CPD that person actually did. If your organisation leaves the CPD AI helpers on: check every suggestion before you save it, because your CPD record is your own statement of what you did; never use a helper on a certificate, note, or recording that shows a client's, patient's, or participant's details; and do not say their names when you dictate.
You must not use the Service to:
Accorda includes features that use artificial intelligence to analyse content (such as the AI assistant and policy-analysis features). When using these features:
The Service generates compliance evidence (sign-off records, audit logs, certificates) using tamper-evident mechanisms. You must not:
You are responsible for the accuracy of the underlying business decisions and processes the Service records. The Service is a record-keeping tool, not a substitute for actual compliance.
You must:
If you become aware of any actual or suspected violation of this AUP (by another user of your organisation, by a member of another organisation, or by anyone else), please notify us at info@accorda.com.au. We will investigate and take appropriate action.
We may, at our sole discretion and without prior notice:
We will generally attempt to notify the affected user or Customer Organisation before taking action, but reserve the right to act without notice where we consider it necessary to protect the Service, other users, or third parties.
We may update this AUP from time to time. When we make material changes, we will notify Customer Organisation administrators by email and update the version and effective date at the top of this page. Continued use of the Service after the effective date of an updated AUP constitutes acceptance of the changes.
Questions about this policy or to report a violation:
True North Analytics ABN 24 726 502 584 Email: info@accorda.com.au