Privacy
Effective 19 November 2026 · Version 1.15
This Privacy Policy explains how True North Analytics ("we", "us", "our") handles personal information when you, your organisation, or your end-users use Accorda (the "Service"). True North Analytics operates as a sole trader from New South Wales, Australia (ABN 24 726 502 584).
This policy covers what we do as the operator of the Service. If you are an end-user accessing Accorda at the invitation of an organisation that has subscribed to the Service (your "Customer Organisation"), that organisation is the data controller for your personal information, and a separate notice applies inside the Service describing what they collect from you. This policy describes our role as their data processor.
True North Analytics is a sole-trader business operating Accorda from New South Wales, Australia. We hold an Australian Business Number (ABN 24 726 502 584). We are bound by the Australian Privacy Act 1988 (Cth) and the Australian Privacy Principles ("APPs").
For all privacy enquiries, contact us at privacy@accorda.com.au.
This policy covers:
It does not cover:
When you visit pages such as our marketing site or this policy, we may collect:
When an authorised representative of an organisation signs up for Accorda, we collect:
When end-users from a Customer Organisation use Accorda, the Service collects information *on behalf of the Customer Organisation* (who is the data controller). This typically includes:
We process this information solely on the instructions of the Customer Organisation, under our standard Data Processing Agreement.
We (True North Analytics) do not collect "sensitive information" as defined by the Privacy Act (such as health information, racial or ethnic origin, political opinions, religious beliefs, sexual orientation, or biometric data) for our own purposes. Except where a feature is specifically designed to record it (see below), end-users and administrators must not enter sensitive information into free-text fields in the Service, and Customer Organisations are responsible for instructing their personnel accordingly.
Some features are designed to record information that may be, or may border on, sensitive information. In particular, the worker screening and credentials features let a Customer Organisation record the status of background checks and clearances for its workers, contractors, and volunteers (such as national police checks, Working with Children Checks, and NDIS Worker Screening), together with the outcome of those checks and any certificates the organisation uploads. Information about an individual's criminal-history record checks is sensitive information under the Privacy Act. Similarly, complaint records may contain allegations or other sensitive details about the people involved. Where a Customer Organisation uses these features, it does so as the data controller and is responsible for ensuring it has a documented lawful basis for collecting and recording the information, for obtaining any consent required by law, and for recording only what is necessary for the compliance purpose (for example, the fact and status of a clearance rather than the underlying criminal-history detail). We process this information only on the Customer Organisation's instructions and do not use it for any purpose of our own.
Incident records and incident attachments may naturally include references to or information about your clients, patients, service recipients, or other vulnerable individuals. Incident records in regulated sectors (such as healthcare, aged care, NDIS, childcare, and other community services) commonly document events involving vulnerable people, and may therefore contain health information or information about safeguarding concerns. When recording incidents, the Customer Organisation must ensure: (1) that it has a documented lawful basis for collecting and recording the incident information under Australian privacy law and any other applicable law, (2) that consent has been obtained where required by law, and (3) that any attachments to incidents (such as photographs) do not contain identifiable information about such individuals unless absolutely necessary and lawfully authorised. Accorda is designed to support compliance management and incident tracking, but is not a specialised system for medical records, safeguarding case management, or the secure handling of sensitive incident media; if your incident records or attachments frequently contain sensitive information about vulnerable individuals, consider whether a more specialised system is appropriate.
The Funding planner and Service agreements module (Section 3.5) is designed to record information about NDIS participants. The fact that a person is an NDIS participant, and the supports they receive, can reveal that they have a disability, so this information is treated as sensitive information (health information) under the Privacy Act. A provider that uses the module does so as the data controller and is responsible for having a lawful basis to collect the information, for giving notice and obtaining any consent required by law, and for recording only what the funding plan, service agreement, and signature need. The module is not designed for clinical notes, diagnoses, or case records, and providers must not use it for them (see our Acceptable Use Policy). We process this information only on the provider's instructions, do not use it for any purpose of our own, and protect it with the additional measures described in Section 9.
CPD reflections (Section 3.3) are about an end-user's own learning. An end-user may choose to mention their own health or wellbeing in a reflection, which can be health information, and can mark that reflection private. If they do not mark it private, their manager and administrators can read it, and external auditors can if the organisation allows. CPD reflections, entries, and uploads must not contain information about clients, patients, or participants. If an end-user writes about a case, they must leave out names and any detail that could identify the person (see our Acceptable Use Policy). The audit log records what changed in a CPD entry, never the words written in it. If an end-user uses an AI helper on a reflection, the notes they choose to send go to our AI subprocessor as described in Section 3.8, including anything they wrote about their own health.
Some Customer Organisations are NDIS registered providers. They can choose to switch on an optional module, Funding planner and Service agreements, which is off unless one of their administrators turns it on. The module helps the provider plan a participant's NDIS funding, prepare a service agreement from a template the provider tailors, and keep a record of how the agreement was agreed (for example, a scan of a copy signed on paper). Where the Service offers it, the provider may also send the agreement to be signed electronically. If you are an NDIS participant, or a parent, plan nominee, guardian, or other representative of a participant, and your provider uses this module, the provider is the data controller for your information. We hold and process it only on the provider's behalf, as its processor. You are not a user of the Service and do not need an account.
The provider may record:
If your provider sends your agreement for electronic signing through the Service, the Service emails you a secure link that expires. When you use the link, the Service records:
These details are added to the signed agreement as an evidence page. The provider uses them to show who signed, when, and that the agreement has not changed since. The signing page shows the provider's privacy notice and a short notice from us explaining our role.
Why it is used. This information is used only so the provider can plan and manage the participant's NDIS funding and supports, prepare and sign the service agreement, and keep a record of it. We do not use it for any purpose of our own, and we never use it for advertising or to train AI models.
Emails. Emails sent about an agreement contain a link only, not plan details or budgets, with one exception: when signing is complete, the person who signed is emailed a copy of the signed agreement as a PDF attachment, so they keep their own copy, at the address they have just confirmed with the six-digit code. When a representative signs for the participant, the participant is also emailed that copy at the email address the provider holds for them (if there is one and it is not the representative's own). Emails to the provider's staff contain only a link into the Service.
AI. If the provider uses the optional AI plan overview, the Service does not send names, NDIS numbers, or contact details to our AI subprocessor, and the result is always a draft that the provider's staff check and edit.
Who can see it. Within the provider, only staff the provider gives this module's permissions can see these records. External auditors cannot see them unless the provider changes that, with one exception the provider controls: an administrator may share a signed agreement with one of the provider's own external auditor accounts in the Service, for a limited time (at most 90 days, and it can be ended sooner). The auditor can then download that signed copy only, and each share and download is logged. This is a disclosure the provider makes on its own instruction. Views, downloads, sends, and signatures are logged.
Access, correction, and complaints. Because the provider controls your information, please contact the provider first if you want to see or correct it, ask for it to be deleted, or make a complaint. Their privacy contact is shown on the signing page and in their own privacy notice. If you contact us instead, we will pass your request to the provider and help them respond (see Section 11). You can also ask the provider for a paper copy of the agreement, or for another way to sign.
The funding planner is a free tool on our public website. It is separate from the Funding planner and Service agreements module inside the Service, which Section 3.5 covers. The plan you build in it is held in your own browser, and the words you type into it (the plan label, the description of each support, anything you write about a person) are never sent to us. How large that plan is, we do record: the usage log described further down this section sets out exactly what that means. When you ask the tool for a download, it asks for your email address first, and we create a record of that request.
That record holds:
We keep the email address so that we can answer you and, if you consented, send you occasional updates about Accorda, and the name of the file so that we know which tool the request came from. The request details and the timestamp are kept as evidence of when and where the consent was given: this form is open to the public internet and anyone can post to it, so without them we could not tell a genuine request from a forged one, or show that an address on our list asked to be there. They are not used to build a profile of you or to follow you across other websites. Section 10.1 states how long the record is kept.
The pages of the tool carry the same page-view measurement as the rest of our website (see Section 5). They do not carry the Meta Pixel: it is kept off this tool deliberately, so opening one of its pages is not reported to Meta and no advertising cookie is set while you use it. Nothing you type into the tool forms part of either.
Page views are not all we record about the planner. The tool also keeps a usage log of its own, whether or not you ever ask for a download. It is written each time the tool reaches one of a handful of moments, and it holds no identifier that joins an entry to your export record, to your email address, or to any other visit: no account, no session token, and no marker kept in your browser to recognise you by. Each entry does carry the day it was written, and your export record carries the date and time it was created; we do not match one against the other.
Each entry in that log holds:
Whether the plan has funding blocks in it, and whether supports have been allocated against them, are read off the plan open in your browser rather than off a button you press: a plan you saved on an earlier visit and had restored registers both of those steps without you doing anything to it. We use this to see how many people open the planner and how far through it they get, which is how we judge whether the tool is worth keeping and improving. What it records about a plan is its size and nothing else: no participant name, no plan name, no description of a support, and none of the other words you type into the tool. Those stay in your browser: the log has no field that could hold them, and the tool has no way to send them.
The compliance readiness check is a free tool on our public website. It asks you about how your organisation manages compliance, scores your answers on our server, and shows you a report. Three things are recorded about each check and kept together: a record of the session, a row for every answer, and a step-by-step log of how the visit moved through the tool. Where you give us an email address, it sits on the session record, and whatever is held against that record is joined to it. We use your email address to send you your report.
The session record holds:
We use this to see how many people start the check, how far they get, and which parts of compliance they find hardest, so that we can judge whether the tool is worth running and what to build next. Where a sector we do not yet cover is typed in, we read it to decide what to build. The campaign tags, the referrer, the device and the user-agent sit on the same row as the email address where one is given, so this is a record of your visit with your address on it rather than a count, and we can read it that way. What it does not hold is an IP address: none of the three tables the check writes to has a column for one. The standard server logs described in Section 3.1 cover the pages of the check as they cover the rest of our website, and those do record an IP address.
Every answer is stored as its own row: which question it was, which of the four options you chose, the score that option carries, the compliance domain it belongs to, and the date and time you answered. Going back and changing an answer overwrites the earlier one rather than adding to it.
The step log is written as you go, and records:
Each entry carries the date and time it was written, and some carry a little more detail beside them: our pages add the campaign tags on the arriving link, the device and the referring page, which domain was opened out, or whether the email step came before the questions or after the report. Two of these entries, the landing page being opened and the questionnaire being opened, are written without a session and stand on their own. The first of them is written as the landing page loads, and so whether or not you go on to start the check. The rest are held against the session they were sent with, and so against the email address on it where you have given one. We use the log to see where people leave the check.
The pages of the check carry the same page-view measurement as the rest of our website, and its landing page and its questionnaire carry the Meta Pixel as well: Section 5 sets out both, and Section 6.1 sets out what Meta receives. Section 10.2 states how long the records described here are kept.
Where a Customer Organisation switches on CPD (Section 3.3), the Service also offers optional helpers that use AI to save end-users time. The helpers are on unless an administrator switches them off for the workspace in the CPD settings, and they work only once an administrator has accepted our updated Data Processing Agreement. Even when they are on, nothing is sent to AI until a person presses the button for a helper, each time they use it. Every helper can be skipped: everything it does can be typed or chosen by hand.
The helpers, and what each one sends:
Before any CPD text that a person types or dictates is sent to Anthropic, the Service removes anything that looks like an NDIS number, a Medicare number, a phone number, an email address, a full date (including a date of birth), a street address or postcode, or another long string of numbers. In the CPD AI helpers, a possible client name triggers a warning before anything is sent, so the end-user can take it out. Entry titles that the AI assistant uses have identifiers removed but are not checked for names. These checks run on our own servers, not through AI. The content of a certificate photo or PDF, or of a voice recording, cannot be cleaned before it is sent, so the end-user must leave clients' details off anything they upload or say. No automatic check catches everything. So the rule in Section 3.4 still applies: CPD notes, reflections, uploads, and dictation must not include details of clients, patients, or participants.
What a helper sends is used only to give the person their suggestion. We do not keep a copy of it, other than what the person chooses to save in the CPD record. The Service keeps usage counts and the cost of each request, for billing and usage limits, but never the content sent. A suggestion is a draft: the end-user decides what goes into their CPD record and is responsible for it.
Sections 6.1 and 8 say where Anthropic and OpenAI process what they receive, how long they keep it, and that they do not train their models on it.
We use personal information to:
We use end-user personal information only to operate the Service on the Customer Organisation's instructions. We do not use it for our own purposes, do not analyse it for advertising or product development beyond the operation of the Service, and do not sell or rent it.
The one limited exception is the trial and demo follow-up retention described in Section 10. That exception applies only to the business-contact and high-level usage information of a trial or demo account. It never includes end-user content processed on behalf of a paying Customer Organisation, and never includes information about NDIS participants or their representatives.
This includes the information about NDIS participants and their representatives recorded in the Funding planner and Service agreements module, and the signing records described in Section 3.5. We send emails about a service agreement only on the provider's behalf and at its direction, and we do not contact participants or representatives for any purpose of our own.
We do not:
Accorda uses cookies that are strictly necessary for the operation of the Service, including session cookies issued during sign-in. One of these remembers, for ten minutes, that a visit has just been recorded, so the Service does not record the same visit again (see Section 3.3). Inside the Service, we do not use third-party advertising cookies or cross-site tracking. Our public website is different: it carries the Meta Pixel, described below.
We use Vercel Analytics to understand aggregate usage of the Service, such as which pages are visited. Vercel Analytics is designed to be privacy-friendly: it does not set tracking cookies, does not track you across other websites, and does not build advertising profiles. It collects aggregated page-view data rather than identifying individual visitors.
Our public website carries the Meta Pixel, an advertising tag supplied by Meta Platforms (see Section 6.1). It runs on our public marketing pages, and only on the pages we have specifically opted in to it: a page of our website carries the pixel where we have added it and nowhere else. Anywhere we have not opted in carries no pixel at all: the funding planner, which Section 3.6 covers, and our sign-in pages are among those places. The compliance readiness check is the other way about: its landing page and its questionnaire are opted in and do carry the pixel, and Section 3.7 sets out what the check itself records. The personal link that opens a completed compliance readiness check report is not opted in: that link is itself the key to the report, so the pixel is kept off it deliberately and opening one sends nothing to Meta. The pixel is not strictly necessary: it sets Meta's own cookies in your browser, and it reports to Meta each page of ours that you open, along with the one action we count as a conversion, which is asking to see the live demo. Meta can match what it receives against a browser or an account it already knows, so this is cross-site tracking for advertising, and Meta uses what it receives for its own purposes as well as ours. Those pages also carry forms asking for your name, email address and phone number, and while a Meta setting called Automatic Advanced Matching is switched on (a switch in Meta's Events Manager, not in our code), a hashed copy of what you type into them is sent to Meta as well. Section 6.1 sets out what Meta receives and what it is not given, and Section 8 sets out how you can limit what reaches Meta.
We also measure page views on our public website. Vercel Analytics, provided by our application host (see Section 6.1), is enabled on the pages our website serves (our marketing pages and the free tools among them) and reports which pages are visited.
Page views are not the only thing we record on our public website. The compliance readiness check keeps its own log of how a visit reaches and moves through it, which Section 3.7 sets out in full: that its landing page was opened, which is recorded as that page loads whether or not you go on to start the check, together with any campaign tags carried in the link that brought you to it and the address of the page that linked you to us, and, once an assessment has been started, the steps taken through it against the session they belong to. We use that log to see where people leave the questionnaire. The funding planner keeps a usage log of its own on the same footing, which Section 3.6 sets out in full. This section is an account of the cookies and tags our website carries and of our page-view measurement, and not of everything the website records: what each of the two free tools records about a visit is set out in Sections 3.6 and 3.7, and how long each is kept in Sections 10.1 and 10.2.
We use the following subprocessors to deliver the Service. Except where the entry says otherwise, each is bound by contractual and (where applicable) statutory obligations to use personal information only to provide its service to us, except that the AI providers (Anthropic and OpenAI) may also keep content flagged for misuse for the period stated in their entry:
We may add or replace subprocessors from time to time. Material changes are notified to administrators by email and reflected here.
We may disclose personal information where:
We do not disclose end-user personal information to other Customer Organisations.
Customer Organisations may upload documents and other content to Accorda (their "Customer Data"). The Customer Organisation is solely responsible for the lawful basis for collecting and uploading any personal information contained in Customer Data, including the personal information of their own employees, contractors, clients, patients, participants, and other third parties. We process Customer Data only on the Customer Organisation's instructions.
Customer Organisations should not upload personal information of their own end-customers, clients, or service recipients (such as patient records, client case files, or participant data) into Accorda except where strictly necessary for compliance documentation purposes and where they have a lawful basis to do so. The one designed exception is the Funding planner and Service agreements module, which NDIS registered providers can switch on to hold the limited participant information described in Section 3.5. See our Acceptable Use Policy for further detail.
The Service is operated from Australia, and primary processing of Customer Data occurs in the Sydney region. Some subprocessors (such as Stripe, Anthropic, OpenAI, Voyage AI, Sentry, Resend, GitHub, Meta Platforms, Vercel's edge network, and the Vercel server functions that run our public website) may process certain personal information outside Australia. Except where the entry in Section 6.1 says otherwise, before those transfers we take reasonable steps, as Australian Privacy Principle 8.1 requires, to ensure each provider handles personal information consistently with the APPs, relying on its contractual commitments to us and its privacy programme. Meta is that exception: what the Meta Pixel sends is handled outside Australia by an advertising business under its own terms, and not under an agreement binding it to the operation of Accorda.
The Meta Pixel's transfer works differently: the pixel is on our public marketing pages, so it sends what Section 6.1 describes to Meta when one of those pages is opened by anyone at all, including a reader who has never used the Service. You can limit what reaches Meta from your own browser: most browsers carry privacy settings that block third-party cookies and known tracking scripts, and a browser extension that blocks advertising tags will stop the pixel loading at all. If you hold a Meta account, the ad preferences and off-Meta activity sections of that account's settings govern what Meta may do with what it receives.
Our nightly off-site backup (Section 6.1) also involves a transfer outside Australia, though nothing is stored overseas. The job that makes it runs on a temporary computer hosted by GitHub, usually in the United States. For the few minutes of each run, the copy of the Service's database and stored files passes through that computer on its way to our backup storage with Amazon Web Services in Sydney. It is encrypted on its way to and from that computer, is held there only while the job runs, and is wiped with that computer when the run ends. The backup itself is stored only in Australia.
The optional Dictate feature involves an overseas disclosure that we want to be explicit about, consistent with Australian Privacy Principle 8 (cross-border disclosure of personal information). When, and only when, a user actively chooses to dictate an incident, complaint, or risk description, or a CPD reflection, rather than type it, the short audio recording of their voice is sent to OpenAI in the United States for transcription, and the text is then sent to Anthropic to be tidied. The feature is entirely optional, nothing is sent unless the user initiates a dictation, and a typed alternative is always available for every field Dictate can fill. The audio is transcribed and discarded (it is not stored by us), and under OpenAI's API terms it is not used for model training and is retained by OpenAI for no more than 30 days for abuse monitoring, or longer where the law requires. We take reasonable steps to ensure these overseas recipients handle personal information consistently with the APPs, including through the terms described in their entries in Section 6.1. Customer Organisations that prefer to avoid this transfer entirely can instruct their personnel to type instead of dictating, and can switch the CPD AI helpers off.
For the Funding planner and Service agreements module, plans, agreements, and signing records are stored in the Sydney region. Emails about an agreement are delivered by Resend, which may process them outside Australia. Those emails contain only a link, except the completion emails to the person who signed and, when a representative signed, to the participant, which attach the signed agreement. The optional AI plan overview sends text to Anthropic, without names, NDIS numbers, or contact details. Where Anthropic processes it is set out in its entry in Section 6.1.
The optional CPD helpers (Section 3.8) are another overseas disclosure under Australian Privacy Principle 8. Only when a person presses a helper's button, the certificate, notes, details, or team figures that helper uses are sent to Anthropic, which processes and stores them in the United States, and dictated reflections are sent to OpenAI in the United States to be transcribed, with the text then sent to Anthropic to be tidied. Before typed or dictated text is sent, the Service removes the identifiers listed in Section 3.8. The content of a photo or PDF cannot be cleaned, so people must leave clients' details off what they upload. CPD answers in the AI assistant, and CPD figures in AI-drafted summaries (Section 3.8), go to Anthropic in the same way. We take reasonable steps to ensure these recipients handle personal information consistently with the APPs: each is bound by its business terms with us, neither may train its models on what we send, and each deletes it within the periods set out in Section 6.1. A Customer Organisation that does not want CPD content sent to AI providers overseas can switch the CPD AI helpers off in its CPD settings; every helper can be done by hand instead.
We implement reasonable technical and organisational measures to protect personal information, including:
For incident attachments specifically, additional measures include: private, non-public file storage accessible only to authorised users within the same organisation; tenant-scoped access control enforced at the storage layer; automatic removal of image metadata (EXIF data including GPS, timestamps, camera information) to prevent unintended disclosure of location or device information; validation of file type and content to prevent malicious uploads; and audit logging of all attachment access and downloads.
For the Funding planner and Service agreements module specifically, additional measures include: access limited to staff the provider gives the module's permissions, with external auditors excluded by default; logging of every view, download, send, and signature; private, non-public storage of agreements and signatures, opened only through short-lived download links; signing links that are unique, expire, and need a six-digit code sent to the recipient's email address before the agreement can be viewed or signed; and a SHA-256 fingerprint of each signed agreement so later changes can be detected.
For CPD records specifically, additional measures include: private, non-public storage of evidence files, opened only through short-lived download links; a server check of every uploaded file before it is kept, so only JPEG, PNG, and PDF files are accepted, with the original upload deleted once it has been checked; photos saved again without their hidden details (such as camera, time, and GPS location); PDF files refused when they show signs of scripts or attached files; and an audit log entry for every evidence file opened or downloaded in the Service and every CPD download from it, written before the file is given out.
To operate, support, secure, troubleshoot, and maintain the Service, a small number of authorised personnel of True North Analytics (the platform operator) may access Customer Data across the Service, including through administrative tools. This access is granted on a least-privilege basis, is limited to what is necessary for those purposes, and is subject to confidentiality obligations. We do not use it to view Customer Data for any purpose other than operating and supporting the Service.
No system can be guaranteed entirely secure. We will notify affected individuals and the Office of the Australian Information Commissioner ("OAIC") of any eligible data breach in accordance with the Notifiable Data Breaches scheme under the Privacy Act.
When a Customer Organisation's subscription ends, Customer Data (including incident records and any remaining attachments) is retained in accordance with the data export and deletion provisions of our Data Processing Agreement (typically a 30-day grace period for export, followed by deletion).
Trial and demo accounts are treated differently from paid subscriptions. A trial runs for about 14 days. When a trial ends and is not continued, the account enters a short grace period of about 7 days, during which it is suspended but the data still exists and the account can be reactivated or continued. After that grace period, the trial or demo account and its Customer Data are deleted. This 7-day trial grace period is separate from, and shorter than, the 30-day export window that applies to paid subscriptions when they are cancelled.
When a trial or demo account is deleted, we keep a limited follow-up record so we can contact the business about its trial, seek feedback, and offer the opportunity to continue. This record contains business-contact details (an administrator's name and email address, and the business name and sector) and high-level usage information (counts such as the number of policies added, sign-offs, and users, the date of last activity, and key dates for the account). It does not include the documents, incident records, or other content held in the account, which are deleted with the account. We keep this follow-up record for no longer than 12 months from deletion, after which it is deleted. You can ask us not to contact you (opt out) at any time, and you can ask us to erase this record at any time. We do not sell this information, and we do not share it for anyone else's marketing. To opt out or request erasure, contact us at privacy@accorda.com.au.
A record created when someone exports a plan from the funding planner on our public website (Section 3.6), made up of the email address, the consent answer, which file was asked for, the request details kept as evidence of that consent, and the date and time, is deleted 24 months after it was created.
Nothing removes these records on a schedule; we meet the deadline by deleting expired records ourselves, so one may stay a little past it until we next do.
We delete it sooner on request. If you ask us to remove your address, or withdraw your consent to marketing, we delete the whole record rather than keeping the evidence behind it, unless we still need it to meet a legal obligation.
Entries in the funding planner's usage log (Section 3.6) have no set deletion date. They hold no email address, IP address or other identifier that links an entry to a person.
The record of a readiness check (Section 3.7), made up of the session record, the answers stored against it, and the entries of the step log, is deleted 24 months after the check was started. The two kinds of entry written without a session are deleted 24 months after each was written.
That deadline is ours to keep rather than the database's. Nothing in the tables that hold these records removes a row on a schedule, so the deadline is met by a clear-out we run, and a record a little past it may still be there until the next one.
We delete sooner on request. If you ask us to remove your readiness check record, we delete the session record, and the answers and step entries held against it go with it, unless we still need them to meet a legal obligation.
If you are an individual whose personal information we hold (whether as administrator, end-user, or otherwise), you have the right to:
For end-user information processed on behalf of a Customer Organisation, please direct such requests to that organisation in the first instance, as they are the data controller. We will assist them in responding under our Data Processing Agreement.
If you are an NDIS participant or representative whose information a provider records in the Funding planner and Service agreements module, see Section 3.5 for how to make a request.
To exercise any of these rights, contact us at privacy@accorda.com.au. We will respond within 30 days.
Accorda is a workplace-compliance platform and is not directed at children. Children do not use the Service, and we do not knowingly collect personal information directly from individuals under 16. A provider using the Funding planner and Service agreements module may record information about a participant who is a child. In that case the provider is the data controller, and the provider is responsible for deciding who has authority to sign for the child, which will usually be a parent or guardian. If you become aware that a child has provided personal information to us through the Service in any other way, contact us and we will delete it or refer it to the relevant Customer Organisation.
We may update this policy from time to time. When we make material changes, we will:
Continued use of the Service after the effective date of an updated policy constitutes acceptance of the changes.
For all privacy enquiries, including to exercise your rights, contact:
True North Analytics ABN 24 726 502 584 Email: privacy@accorda.com.au
Postal correspondence is not currently accepted; please use email.