Data Processing

Data Processing Agreement

Effective 19 November 2026 · Version 1.11

This Data Processing Agreement ("DPA") forms part of the Terms of Service between True North Analytics (ABN 24 726 502 584) ("we", "us", "Processor") and the Customer ("you", "Controller") and governs our processing of Personal Information on your behalf in connection with Accorda (the "Service").

By using the Service, the Customer is deemed to have entered into this DPA. The Customer may also request a counter-signed copy by emailing info@accorda.com.au.

In the event of any conflict between this DPA and the Terms of Service, this DPA prevails to the extent of the conflict on matters of personal information processing.

1. Definitions

In this DPA:

  • "Personal Information" has the meaning given in the Privacy Act 1988 (Cth), and includes "personal data" as that term is used in equivalent overseas privacy laws applicable to a particular Customer.
  • "Customer Personal Information" means Personal Information processed by us on the Customer's behalf in connection with the Service.
  • "Data Subject" means an identified or identifiable individual whose Personal Information is included in Customer Personal Information.
  • "APPs" means the Australian Privacy Principles in Schedule 1 to the Privacy Act 1988 (Cth).
  • "Subprocessor" means a third party engaged by us to process Customer Personal Information.
  • "Personal Information Breach" means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Information.

Other capitalised terms used but not defined here have the meanings given in the Terms of Service.

2. Roles and scope

2.1 Roles

The parties agree that, in respect of Customer Personal Information:

  • The Customer is the data controller (or, in Australian Privacy Act terms, the APP entity that determines the purposes and means of processing)
  • We are the data processor, processing Customer Personal Information only on the Customer's documented instructions

2.2 Subject matter and duration

The subject matter of this DPA is the processing of Customer Personal Information through the Service. This DPA continues for as long as we process Customer Personal Information in connection with the Service.

2.3 Nature and purpose of processing

We process Customer Personal Information to provide and operate the Service for the Customer, including:

  • Hosting Customer Data
  • Providing user authentication and access control
  • Generating compliance evidence (sign-offs, audit logs, certificates)
  • Recording, categorizing, and managing incidents and corrective actions
  • Recording and managing complaints, risk registers, worker screening and staff credential records, and internal audits
  • Managing optional file attachments (incident photos and documents, and uploaded credential or clearance certificates)
  • Sending transactional emails (sign-off reminders, account notifications, and, where the Customer uses electronic signing in the Funding planner and Service agreements module, signing links and the completed-agreement email sent on the Customer's behalf)
  • Providing AI-assisted features (where the Customer's plan includes them)
  • Where the Customer switches on the optional Funding planner and Service agreements module (available only to NDIS registered providers): recording NDIS participant funding plans, generating service agreements from our standard template as tailored by the Customer, recording how each agreement was agreed and storing signed copies, and, where the Service offers electronic signing and the Customer uses it, sending agreements for electronic signature through secure, expiring links, confirming the signer's control of an email address with a six-digit code, recording signing evidence, and delivering signed copies
  • Where the Customer switches on the optional CPD (continuing professional development) module: keeping a record of each Authorised User's professional development, including entries, reflections, evidence files, links, and statements, checking and cleaning uploaded evidence files, importing existing CPD records from spreadsheets the Customer provides, producing CPD registers and downloads, and, unless the Customer switches them off, offering optional AI helpers that an Authorised User starts each time (reading a CPD certificate, tidying reflection notes, suggesting types of learning and learning goals, a team summary of figures for management review, and dictating a reflection)
  • Providing customer support
  • Securing the Service and detecting fraud or abuse

2.4 Categories of Data Subjects

Customer Personal Information may relate to:

  • The Customer's administrators
  • The Customer's staff and other Authorised Users
  • The Customer's workers, contractors, and volunteers who are the subject of worker screening or credential records (whether or not they use the Service themselves)
  • Individuals who raise, or are the subject of, complaints, risks, or incidents recorded in the Service (who may be the Customer's clients, patients, participants, their family members, or staff)
  • Other third parties whose Personal Information is included in Customer Data uploaded by the Customer (subject to the AUP: the Customer must minimise such information). In particular, when incident and complaint records are created, they may involve or relate to the Customer's clients, patients, service recipients, or other vulnerable individuals; the Customer remains responsible for ensuring it has a lawful basis and appropriate consent for recording and processing such information.
  • NDIS participants, and their representatives (such as parents, plan nominees, and guardians), whose information the Customer records in the Funding planner and Service agreements module, or who, where the Customer uses electronic signing, sign or decline a service agreement through it. These individuals are not Authorised Users. They interact with the Service only through a secure, expiring signing link sent on the Customer's behalf, if one is sent

2.5 Types of Personal Information

Customer Personal Information typically includes:

  • Identifiers (name, email address)
  • Workplace role and tenant assignment
  • Activity records (sign-in times, sign-off events, IP addresses, user-agents)
  • Incident records (including: incident title, date of occurrence, type, severity, status, owner, service context, triage notes, and AI-generated provenance metadata)
  • External reporting details for incidents (authority/regulator, reference numbers, dates, notes)
  • Complaint records (including complainant name and contact details unless anonymous, the nature and context of the complaint, severity, status, resolution, and external-referral details)
  • Risk register entries (including risk description, category, ratings, controls, owner, and review dates)
  • Worker screening records (including required screening schemes such as NDIS Worker Screening, national police checks, and Working with Children Checks, recorded clearance status and expiry, and verification outcomes)
  • Credential and qualification records (including credential name and type, an optional licence or certificate identifier, issuer, and validity dates)
  • Internal audit records (findings, corrective actions, and supporting evidence)
  • Optional file attachments (incident photos and documents, and uploaded credential or clearance certificates)
  • Participant funding and agreement records (name, email address, phone number, NDIS number, plan start and end dates and how the plan is managed, supports, support item numbers, quantities, prices, budgets and time blocks, optional goals, optional date of birth and address, and the content and versions of service agreements)
  • Representative details (name, contact details, role, and the Customer's note of the basis of their authority)
  • Where the Customer uses electronic signing, electronic signature evidence (typed name, drawn signature image if used, signer role, the email address the signing link was sent to, the result and time of the six-digit code check, timestamped signing events (sent, opened, verified, viewed, signed, declined, and countersigned), IP address, browser and device type, the electronic-signing consent wording accepted, the template and agreement versions, and SHA-256 fingerprints of the document before and after signing)
  • CPD records (profession, the CPD rules that apply, and registration or accreditation date and status; for each entry the date, title, type, provider, hours or points, category, how much of it counts toward kinds of learning a profession requires, and learning goal; reflections and whether each is private; evidence files, links, and short statements; opening balances and professional body portal totals; checks, notes, and flags with their reasons; who added each entry and when; the file name of any imported spreadsheet; and earlier versions of entries and reflections)
  • Voice recordings made with the optional Dictate feature, which are sent for transcription and then discarded, not stored, and the transcribed text, which is then sent to Anthropic to be tidied
  • Other information the Customer chooses to include in Customer Data

We do not solicit and do not knowingly process sensitive information (as defined by the Privacy Act) for our own purposes. However, some records may contain or reference sensitive information. Incident and complaint records may naturally contain health information, allegations, or information about safeguarding concerns, especially in regulated sectors such as healthcare, aged care, NDIS, childcare, and similar services. In addition, the worker screening and credentials features are designed to let the Customer record the status of background checks and clearances (such as national police checks, Working with Children Checks, and NDIS Worker Screening), which may include information about an individual's criminal-history record checks (a category of sensitive information). Where the Customer records such information, it does so as Controller and remains solely responsible for determining the lawful basis, obtaining any consent required by law, recording only what is necessary for the stated purpose, and complying with the AUP.

Information recorded in the Funding planner and Service agreements module shows that a person is an NDIS participant and the supports they receive, which can reveal disability. The parties treat it as sensitive information (health information) under the Privacy Act. The Customer, as Controller, is solely responsible for the lawful basis for collecting it, for giving notice and obtaining any consent required by law, for checking that a representative has authority to act, for recording only what the funding plan, service agreement, and signature need, and for complying with the AUP and the NDIS Practice Standards. We process it only to provide the module to the Customer.

CPD records are about the Customer's own staff. A reflection may contain health information if a staff member chooses to write about their own health or wellbeing. Reflections, entries, and evidence should not contain personal or health information about the Customer's clients, patients, or participants, and the AUP requires end-users to leave it out or de-identify it. The Customer, as Controller, is responsible for telling its staff how their CPD records are used and who can see them, for obtaining any consent required by law, and for deciding whether its external auditors may read reflection text.

3. Customer instructions

3.1 Documented instructions

We will process Customer Personal Information only on the Customer's documented instructions. The Terms of Service, this DPA, and the Customer's configuration of the Service constitute the Customer's documented instructions.

3.2 Additional instructions

The Customer may provide additional instructions in writing (including by email). We will follow such instructions to the extent technically feasible and lawful. If we consider an instruction to be unlawful, we will notify the Customer.

3.3 Compliance with law

If applicable law requires us to process Customer Personal Information beyond the Customer's instructions, we will inform the Customer of that requirement before processing, unless we are prohibited from doing so by that law.

3.4 AI helpers in the CPD module

When the Customer switches on the CPD module, the optional CPD AI helpers described in Section 3.8 of our Privacy Policy are on unless the Customer switches them off in its CPD settings. While they are on, the Customer instructs us to send the content an Authorised User chooses (a CPD certificate photo, with its hidden details removed, or PDF, reflection notes, entry details, profession with last year's target and shortfall, team totals by profession, or a voice recording, which OpenAI transcribes and Anthropic then tidies) to the AI Subprocessors listed in Annex B, but only when that Authorised User starts a helper, and only to give them a suggestion they can edit or discard. While the helpers are on, the Customer also instructs us to let the AI assistant answer questions about CPD, and to include CPD figures in AI-drafted management review and analytics summaries when at least 5 people have CPD set up, as described in Section 3.8 of our Privacy Policy. None of the CPD processing by AI described in this Section 3.4 starts until the Customer has accepted this version of the DPA; until then, and whenever the helpers are switched off, those features leave CPD out. The Customer may withdraw this instruction at any time by switching the helpers off, after which no CPD content is sent to AI.

When a helper is used, we will:

  • Remove 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 from typed or dictated text before it is sent to Anthropic
  • In the CPD AI helpers, warn the Authorised User before anything is sent when the text contains a possible client name. This check runs on our own servers, not through AI. Entry titles used by the AI assistant have identifiers removed but are not checked for names
  • Send the team summary helper only team totals and totals by profession worked out by our software, for teams of at least 5 people, never names, reflections, or individual entries
  • Send a certificate photo only as a copy with its hidden details (such as location) removed, and a PDF only as a new copy of its first two pages
  • Not keep a copy of what was sent, other than what the Authorised User chooses to save, and keep only usage counts and the cost of each request, for billing and usage limits, never the content

The content of a certificate photo or PDF, or of a voice recording, cannot be cleaned before it is sent, and no automatic check catches everything. The Customer remains responsible for instructing its personnel, under the AUP, not to put details of clients, patients, or participants into CPD notes, reflections, uploads, or dictation. We may switch off a helper (for example the certificate reader) for all customers at any time if we consider it necessary to protect personal information.

4. Confidentiality of personnel

We will ensure that any personnel or contractors authorised to process Customer Personal Information:

  • Are subject to written confidentiality obligations no less protective than those in the Terms of Service
  • Have been trained on their data protection responsibilities
  • Have access only on a need-to-know basis

5. Security

5.1 Technical and organisational measures

We will implement and maintain appropriate technical and organisational measures designed to protect Customer Personal Information against accidental or unlawful destruction, loss, alteration, unauthorised disclosure, or access. The current measures are described in Annex A below.

5.2 Review

We will review and update the security measures from time to time as appropriate having regard to the state of the art, the costs of implementation, and the nature, scope, context, and purposes of processing.

5.3 Customer security obligations

Notwithstanding our security obligations, the Customer is responsible for:

  • The security of credentials issued to its Authorised Users
  • Configuring access controls within the Service appropriately for its risk profile
  • Promptly notifying us of any compromised credentials or suspected unauthorised access
  • Determining whether the Service's security measures are appropriate for the Customer's specific use case

6. Subprocessors

6.1 General authorisation

The Customer authorises us to engage Subprocessors to assist us in providing the Service, subject to the conditions in this Section 6.

6.2 Current Subprocessors

The current Subprocessors are listed in Annex B. The list is updated from time to time and the current version is available in our Privacy Policy.

6.3 New Subprocessors

We will provide the Customer with reasonable advance notice (at least 30 days, where practicable) before engaging any new Subprocessor that will process Customer Personal Information. Notice may be given by email to the Customer's primary administrator or by updates to our Privacy Policy or this DPA.

6.4 Customer right to object

If the Customer objects to a new Subprocessor on reasonable, privacy-related grounds, the Customer must notify us in writing within 14 days of our notice. The parties will discuss the objection in good faith. If we cannot reasonably accommodate the objection, the Customer's sole remedy is to terminate the Subscription as it relates to the affected service, with a pro-rata refund of any pre-paid fees for the unused portion.

6.5 Flow-down

We will impose on each Subprocessor obligations no less protective than those in this DPA in respect of the protection of Customer Personal Information, and remain responsible to the Customer for the Subprocessor's compliance.

7. Data Subject rights

7.1 Assistance

We will provide reasonable assistance to the Customer in responding to requests from Data Subjects to exercise their rights under applicable privacy law (including rights of access, correction, deletion, and complaint).

7.2 Direct contact by Data Subjects

If we receive a request from a Data Subject in connection with Customer Personal Information, we will (without responding to the request beyond an acknowledgement):

  • Promptly notify the Customer
  • Direct the Data Subject to the Customer

7.3 Customer responsibility

The Customer is responsible for responding to Data Subject requests substantively. We provide tools within the Service (including data export, account deactivation, and audit logs) to assist the Customer. For the Funding planner and Service agreements module, these include tools to export and to delete a participant's records. For the CPD module, the Customer's data export includes CPD records, without the text of reflections a staff member marked private, and, while CPD is switched on, each staff member can download their own CPD record, including their private reflections.

7.4 Costs

Where assistance under this Section 7 requires more than minimal effort on our part, we may charge a reasonable fee, which we will notify in advance.

8. Personal Information Breach notification

8.1 Notification to the Customer

We will notify the Customer of any Personal Information Breach affecting Customer Personal Information without undue delay, and in any event within 72 hours of becoming aware of the breach. Notification will include, to the extent then known:

  • The nature of the breach, including the categories and approximate number of Data Subjects and records concerned
  • The likely consequences of the breach
  • Measures taken or proposed to address the breach and mitigate its effects
  • Contact details for further information

8.2 Co-operation

We will co-operate with the Customer's investigation of the breach and provide reasonable assistance in fulfilling the Customer's notification obligations to Data Subjects, regulators (including the Office of the Australian Information Commissioner), and other parties.

8.3 No admission

A notification under this Section 8 does not constitute an admission of fault or liability by us.

8.4 Customer notifications

The Customer is responsible for any notification it must make to Data Subjects, regulators, or other parties as a result of a Personal Information Breach. The Customer must not publicly attribute a breach to us without our prior consent, except where required by law.

9. DPIA assistance

We will provide reasonable assistance to the Customer in the conduct of any data protection impact assessment ("DPIA") or similar privacy impact assessment that the Customer is required to undertake in respect of its use of the Service. Where such assistance requires more than minimal effort on our part, we may charge a reasonable fee.

10. Records

We will maintain records of the categories of processing activities carried out on behalf of the Customer, sufficient to demonstrate compliance with this DPA. These records will be made available to the Customer on reasonable request.

11. Audits

11.1 Customer right of audit

The Customer may, on reasonable advance written notice (not less than 30 days, except in the case of an actual or suspected Personal Information Breach), request an audit of our compliance with this DPA. Audits are subject to the following conditions:

  • Audits are limited to no more than once per 12-month period, except in the case of an actual or suspected Personal Information Breach
  • Audits must be conducted during business hours, in a manner that does not unreasonably disrupt our operations
  • Audits must not require disclosure of information that would compromise the security of other customers' data, our intellectual property, or our confidential information
  • The auditor must be subject to confidentiality obligations no less protective than those in this DPA

11.2 Documentation in lieu

We may satisfy the audit obligation by providing the Customer with relevant documentation, certifications, or audit reports that we hold from third-party assessors.

11.3 Costs

The Customer bears its own costs of conducting an audit. We bear our own costs of co-operating with reasonable audit requests, except where the audit is initiated more frequently than the limits in this Section 11 permit, in which case the Customer reimburses us for the reasonable additional costs.

12. International transfers

12.1 Primary location

Customer Personal Information is primarily hosted in the Asia Pacific (Sydney) region.

12.2 Permitted transfers

We may transfer Customer Personal Information outside Australia where:

  • Necessary to provide the Service via a Subprocessor identified in Annex B
  • Necessary to comply with applicable law
  • The Customer has given consent

Where transfers occur, we rely on the protections offered by the recipient's privacy programme, contractual safeguards, and applicable law.

12.3 Cross-border disclosure

In accordance with APP 8 (cross-border disclosure of personal information), the Customer acknowledges that some Subprocessors may process Customer Personal Information outside Australia, including in jurisdictions whose privacy laws may differ from Australia's. By engaging us, the Customer is taken to consent to such disclosures within the scope of this DPA. For the CPD AI helpers (Section 3.4), this means content an Authorised User chooses to send goes to Anthropic and, for dictation, to OpenAI to be transcribed and then to Anthropic to be tidied, all in the United States (Annex B). A Customer that does not want CPD content sent to AI providers overseas can switch the CPD AI helpers off.

For the nightly off-site backup (Annex A), Customer Personal Information passes through a temporary computer hosted by GitHub, usually in the United States, for the few minutes of each run. 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, with Amazon Web Services in the Asia Pacific (Sydney) region (Annex B).

13. Return or deletion of data

13.1 At end of Service

On termination of the Customer's Subscription, we will, at the Customer's choice:

  • Return Customer Personal Information to the Customer in a structured, machine-readable format (using the data export functionality provided in the Service)
  • Delete Customer Personal Information in accordance with our deletion timelines

The Customer has 30 days from termination to make this choice and to extract Customer Personal Information through the Service.

13.2 Deletion timeline

After the 30-day grace period, we will delete Customer Personal Information from active systems within 30 days. Because backups are kept on a rolling 7-day basis, any remaining backup copies, including in the off-site backup described in Annex A, normally age out within a further 7 days (Annex A explains when the off-site backup can take longer).

13.3 Retention as required by law

We may retain Customer Personal Information as required by applicable law, in which case we will continue to protect it in accordance with this DPA for as long as it is retained.

13.4 Trial and demo follow-up record

Where the Customer's account is a trial or demo account, when it is deleted we retain a limited follow-up record for our own purpose of following up about the trial, seeking feedback, and offering 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 (such as counts of policies, sign-offs, and users, the date of last activity, and key dates). 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 and then delete it. The individual concerned may ask us not to make contact (opt out) at any time, and may ask us to erase the record at any time. We do not sell this information and do not share it for anyone else's marketing. This is described further in our Privacy Policy.

13.5 Funding planner and Service agreements records

For the Funding planner and Service agreements module, during the Subscription:

  • Agreed service agreements (signed, or recorded as agreed without a signed copy), service agreements the participant or their representative declined, and their signing evidence are kept for 7 years after the agreement's end date by default, or for the period the Customer sets in the Service. They are never deleted automatically: once that period has passed, the Customer's administrators are notified and an administrator decides when to delete them. The Customer is responsible for choosing a period that meets its own legal, NDIS, and contractual record-keeping obligations
  • Service agreements that were never agreed (drafts, agreements prepared but never sent or signed, and cancelled agreements) are deleted automatically, with their stored files, once they have not been changed for 12 months. An agreement sent for electronic signing that is not signed or declined returns to this group when its signing link expires (after 14 days) or the Customer cancels signing
  • Funding plans are deleted automatically once the plan ended more than 12 months ago and has not been changed for 12 months, unless a service agreement still uses it
  • The Customer can export a participant's records, and delete them, at any time, subject to the retention setting it has chosen
  • Deleted records are removed from active systems, and any backup copies, including in the off-site backup, normally age out on the rolling 7-day backup cycle (see Annex A)

Sections 13.1 and 13.2 apply at the end of the Service, whatever retention period the Customer has set. The Customer must export any signed agreements it needs to keep before the 30-day period in Section 13.1 ends.

13.6 CPD records

CPD records (entries, including removed ones, reflections, evidence files, and earlier versions) are kept while the Customer's workspace exists. They are not deleted automatically, and switching the module off hides them without deleting them. Removing an entry in the Service takes it out of the CPD totals, and removing a piece of evidence takes it off the entry, but both are kept, with any file, as part of the record's history. When a staff member's account is deactivated, their CPD record stays in the workspace and remains visible to the Customer's administrators. The Customer's data export does not include the text of private reflections (Section 7.3). Staff who want to keep them should download their own CPD record before their account is deactivated or the workspace is closed. The Customer may ask us to help with a staff member's request for their private reflections. The Customer is responsible for deciding how long to keep CPD records to meet its own legal, professional, and contractual obligations, and may ask us to delete a CPD record, an entry, an earlier version, or an evidence file sooner. Sections 13.1 and 13.2 apply at the end of the Service.

14. Liability

The limitation of liability provisions in the Terms of Service apply to this DPA.

15. Term

This DPA takes effect when the Customer first uses the Service after its publication, and continues until the Customer's Subscription ends and the obligations relating to return or deletion of data have been completed.

16. Changes to this DPA

We may update this DPA from time to time. Material changes will be notified to the Customer's primary administrator by email and reflected in our published version. Continued use of the Service after a material change constitutes acceptance.

17. Notices

Notices under this DPA may be given by email:

  • To the Customer: at the email address associated with the Customer's primary administrator
  • To us: info@accorda.com.au

18. Governing law

This DPA is governed by the laws of New South Wales, Australia.

Annex A: Technical and organisational security measures

We implement and maintain the following technical and organisational measures, updated from time to time:

Encryption

  • Customer Data is encrypted in transit using TLS 1.2 or higher between the Customer's browser, our application, and our Subprocessors
  • Customer Data is encrypted at rest in our database (Supabase), storage (Supabase Storage), and off-site backup (Amazon Web Services) using industry-standard encryption

Access control

  • Multi-factor authentication is available to all users and can be required for administrator accounts
  • Service personnel access is granted on a least-privilege basis
  • Authorised personnel may access Customer Personal Information across the Service where necessary to operate, support, secure, troubleshoot, and maintain it; such access is limited to what is necessary for those purposes and is subject to confidentiality obligations
  • Authentication systems use industry-standard practices including password hashing and short-lived access tokens

Tenant isolation

  • Customer Data is segregated using row-level security at the database layer; cross-tenant access is technically prevented, not just policy-prevented
  • Storage paths are tenant-scoped and access is governed by row-level security policies

Network security

  • Application traffic is delivered exclusively over HTTPS
  • Application-layer firewalls and rate limiting are in place
  • Service infrastructure is hosted on cloud providers with established security certifications

Logging and monitoring

  • Application errors and security events are logged and monitored
  • Customer-facing audit logs record administrative actions, sign-offs, and other compliance-relevant events
  • Operational logs are retained for periods stated in our Privacy Policy

Participant records (Funding planner and Service agreements)

  • The module is off by default, is available only to NDIS registered providers, and is switched on only by a Customer administrator
  • Access is limited to Authorised Users the Customer gives the module's permissions; external auditor access is excluded by default
  • A Customer administrator may share a signed agreement with one of the Customer's own external auditor accounts in the Service, for a limited time (at most 90 days) that the Customer can end sooner. The auditor can download only that signed copy, and each share, end of sharing, and download is logged. Such a share is a disclosure made on the Customer's instructions
  • Views, downloads, sends, and signatures of participant records are recorded in the Customer-facing audit log
  • Service agreements and signature images are kept in private, tenant-scoped storage and are opened only through short-lived download links
  • Where electronic signing is used, signing links are unique, expire, and require a six-digit code sent to the recipient's email address before the agreement can be viewed or signed
  • Emails to Customer staff carry only a link into the Service. Emails to participants and representatives carry only a link, except the completion email, which attaches the signed agreement. It is sent to the signer at the address just confirmed with the six-digit code and, when a representative signs, also to the participant at the email address the Customer holds for them (unless there is none, or it is the representative's own)
  • Every stored agreement PDF is fingerprinted (SHA-256). Each electronically signed agreement also carries fingerprints of the document before and after signing, and an evidence page, so later changes can be detected
  • The optional AI plan overview sends no names, NDIS numbers, or contact details to the AI Subprocessor, and its output is a draft for a person to check and edit

CPD records

  • The module is off by default and is switched on only by a Customer administrator
  • A staff member's CPD records can be read by that staff member, the Customer's administrators, and managers the Customer allows, for the people they manage only. A manager's access is worked out on every request and ends when they no longer manage the person or the person leaves
  • A reflection marked private can be read in the Service only by the staff member who wrote it. It is hidden from administrators and managers, including an administrator viewing the Service as that person, and is left out of the Customer's data export
  • External auditor accounts can read counted entries, their evidence, and the CPD register while their access is current. They can read reflection text only if the Customer switches that on, and never private reflections
  • Uploaded evidence files are checked by the server before they are kept, and the original upload is deleted once it has been checked. Only JPEG, PNG, and PDF files are accepted, judged by their content. Photos are saved again without their metadata (including GPS location). PDF files that show signs of scripts or attached files are refused
  • Evidence files, and prepared CPD record and worker evidence downloads, are kept in private storage under the Customer's own folder and are opened only through short-lived download links. Prepared downloads are removed within about two hours. The CPD register is sent straight to the person who asked for it and is not stored
  • Every evidence file opened or downloaded in the Service, and every download of a CPD register, evidence bundle, or CPD record from it, is recorded in the Customer-facing audit log before the file is given out
  • CPD audit log entries record what changed, never the words written in entries, reflections, flags, or notes
  • The CPD AI helpers can be switched off by a Customer administrator, send nothing until an Authorised User starts a helper, remove identifiers from text before it is sent, and warn before anything is sent when the text contains a possible client name (Section 3.4)

Backups

  • Customer database is backed up daily, retained for 7 days
  • Each night a separate off-site copy of the database and stored files is saved in a private storage bucket with Amazon Web Services in the Asia Pacific (Sydney) region, independent of our main hosting provider
  • The off-site copy is made by a nightly job that runs on GitHub. The data is encrypted on its way to and from GitHub's computer, is held there only while the job runs, and is stored only in Australia
  • The backup job signs in to Amazon Web Services with short-lived credentials, and its access is limited to the backup bucket
  • Backups are encrypted at rest
  • Once data is deleted from the Service, backup copies of it, including in the off-site backup, are normally gone within 7 days. If a nightly backup run is delayed, or paused by one of its safety checks (for example after a large deletion), those copies are removed at the next successful run, which we fix promptly

Incident response

  • We maintain a written Incident Response Plan describing our procedures for detection, containment, communication, and resolution of security incidents
  • Personnel are trained on the plan
  • The plan is reviewed at least annually and after any material incident

Personnel

  • Personnel with access to Customer Data are subject to confidentiality obligations
  • Access is revoked when personnel cease to require it for their role

Software development

  • Code changes are reviewed before deployment
  • Production deployments are subject to type-check and build verification
  • Vulnerability scanning of dependencies is performed regularly

Physical security

We do not maintain physical infrastructure for Customer Data; security of physical infrastructure is the responsibility of our Subprocessors (notably Supabase, Vercel, and Amazon Web Services), which operate certified data centres.

Annex B: Subprocessors

The following Subprocessors process Customer Personal Information in connection with the Service. The list is updated from time to time, with the current version available in our Privacy Policy.

SubprocessorPurposeRegion
SupabaseDatabase, authentication, storageAsia Pacific (Sydney)
VercelApplication hosting and privacy-friendly, cookieless usage analyticsMulti-region (primary: Sydney; edge: global)
StripePayment processingGlobal
AnthropicAI inference for the AI-assisted features of the Service (the assistant and help chatbot; policy and document tools; incident, complaint, and risk tools, including tidying dictated text; corrective actions, internal audit, management review, analytics, skills, induction, compliance profile, and feedback helpers; the optional plan overview in the Funding planner and Service agreements module, sent without names, NDIS numbers, or contact details; and the optional CPD AI helpers, which can include CPD certificate images and PDFs). Not used to train its models; deleted by Anthropic within 30 days unless flagged for a usage policy breach or required by lawUnited States (every request is processed in the United States)
OpenAIVoice-to-text transcription (optional Dictate feature only, for incident, complaint, and risk records and CPD reflections; audio is transcribed and discarded, and the text is then tidied by Anthropic; not used for model training; retained by OpenAI for no more than 30 days for abuse monitoring, or longer where the law requires)United States
Voyage AIText embeddings for document search and the AI assistant (document text and assistant queries; not used to train its models)United States
ResendTransactional email (including signing links and the completed-agreement email for the Funding planner and Service agreements module)Global
SentryError monitoringEuropean Union
Amazon Web Services (AWS)Off-site backup storage (a nightly copy of the database and stored files, in a private, encrypted storage bucket, kept for the backup period in Annex A)Asia Pacific (Sydney)
GitHub (Microsoft)Runs the nightly off-site backup job (the copy of the database and stored files passes through a temporary GitHub computer, encrypted on the way to and from it, for the few minutes of each run, and is wiped with that computer afterwards; nothing is kept at GitHub after the run)United States, usually (held only during each run, not kept)

Each Subprocessor is bound by contractual obligations to handle Customer Personal Information only for the purposes of operating the Service.

How to contact us

True North Analytics ABN 24 726 502 584 Email: info@accorda.com.au

Questions about this document? info@accorda.com.au
Data Processing Agreement — Accorda · Accorda