Legal
Last updated: 28 March 2026
This Data Processing Agreement ("DPA") forms part of the Service Agreement between Moirai Health Pty Ltd (ABN pending), a company incorporated under the laws of Australia with its registered office in Canberra, ACT ("Processor", "Moirai", "we", "us"), and the entity that has executed the Service Agreement ("Controller", "Customer", "you").
This DPA applies to the Processing of Personal Data by the Processor on behalf of the Controller in connection with the provision of the Moirai clinical AI governance infrastructure (the "Service"). It reflects the parties' commitment to comply with the Australian Privacy Act 1988 (Cth), the Australian Privacy Principles ("APPs"), and where applicable, the EU General Data Protection Regulation ("GDPR").
In the event of any conflict between this DPA and the Service Agreement, this DPA shall prevail with respect to the Processing of Personal Data.
| Subject matter | Provision of the Moirai clinical AI governance infrastructure, including tool registration, compliance tracking, policy management, evidence storage, and reporting. |
| Duration | For the term of the Service Agreement, plus any period required for data deletion or return as specified in Section 11. |
| Nature & purpose | Processing Personal Data as necessary to provide, maintain, and improve the Service, including user authentication, access control, governance record-keeping, compliance scoring, report generation, and customer support. |
| Types of data | User account information (name, email, role), practice details (practice name, address, ABN), AI tool metadata (tool names, vendors, risk classifications, deployment dates), governance documents (policies, evidence records, compliance assessments), and usage/audit logs. |
| Categories of Data Subjects | Practice staff (clinicians, administrators, IT personnel), practice administrators and authorised users of the Service. |
Important note: Moirai is designed to process practice-level governance and compliance data. The Service is not intended to process, and the Customer shall not submit, Protected Health Information (PHI), patient records, or individually identifiable health information through the platform.
The Processor shall:
The Processor implements and maintains the following technical and organisational security measures to protect Personal Data:
| Category | Measure |
|---|---|
| Encryption | AES-256 encryption at rest for all stored data. TLS 1.2+ encryption for all data in transit. |
| Access control | Role-based access control (RBAC) at the application layer. Row Level Security (RLS) enforced at the database layer, scoped to practice_id. |
| Authentication | Secure authentication via Supabase Auth with cookie-based sessions. Row Level Security enforced at the database layer with practice-scoped isolation. |
| Infrastructure | Hosted on infrastructure operated by SOC 2 Type II certified sub-processors (Supabase, Vercel). Automatic patching and security updates managed by hosting providers. |
| Monitoring | Real-time error monitoring via Sentry. Audit logging of data access and modifications. Anomaly detection on authentication events. |
| Data isolation | Logical tenant separation at the database level via RLS policies. No cross-practice data access. |
| Backups | Automated daily backups with point-in-time recovery. Backups encrypted at rest and stored in the same region (ap-southeast-2). |
| Incident response | Documented incident response procedures with defined escalation paths. Regular review and testing of response plans. |
| Personnel | Background checks for all personnel with access to production systems. Mandatory security awareness training. Principle of least privilege enforced. |
The Processor shall regularly assess the effectiveness of these measures and update them as necessary to address evolving threats and industry best practices.
The Controller provides general authorisation for the Processor to engage the following Sub-processors. The Processor has entered into data processing agreements with each Sub-processor that impose data protection obligations no less protective than those set out in this DPA.
| Sub-processor | Purpose | Location |
|---|---|---|
| Supabase Inc. | Database hosting & backend services | ap-southeast-2 (Sydney, Australia) |
| Vercel Inc. | Application hosting & CDN | Global CDN (edge network) |
| Anthropic PBC | AI-generated governance content (no patient data sent) | United States |
| Stripe Inc. | Payment processing & billing | United States |
| Sentry (Functional Software Inc.) | Error monitoring & performance tracking | United States |
| PostHog Inc. | Product analytics & feature flags | European Union |
| Resend Inc. | Transactional email delivery | United States |
| Loops Inc. | Lifecycle email & user communications | United States |
The Processor shall notify the Controller at least 30 days before engaging any new Sub-processor or replacing an existing Sub-processor. The notification shall include the Sub-processor name, purpose, and location. The Controller may object to the engagement of a new Sub-processor by providing written notice within 14 days of receiving the notification, including reasonable grounds for the objection. If the parties cannot resolve the objection within 30 days, the Controller may terminate the affected Service with no penalty.
The primary datastore for the Service is located in ap-southeast-2 (Sydney, Australia). All core application data, including governance records, compliance assessments, and evidence documents, is stored in this region.
Where Sub-processors Process Personal Data outside of Australia, the Processor ensures that adequate safeguards are in place in accordance with APP 8 (cross-border disclosure of personal information). These safeguards include:
The Controller acknowledges that certain ancillary services (authentication, billing, error monitoring, email delivery) may involve the Processing of limited Personal Data in the United States and European Union, as specified in the Sub-processor table above.
The Processor shall assist the Controller in responding to requests from Data Subjects exercising their rights under the Australian Privacy Act 1988 (Cth), including:
The Processor shall promptly notify the Controller upon receiving a request from a Data Subject directly and shall not respond to the request without the Controller's prior written authorisation, unless required by law.
The Processor shall notify the Controller without undue delay, and in any event within 72 hours of becoming aware of a Data Breach affecting Personal Data Processed under this DPA.
The notification shall include, to the extent available:
Where it is not possible to provide all information at the time of notification, information may be provided in phases without undue delay. The Processor shall cooperate with the Controller and take reasonable steps to assist in the investigation, mitigation, and remediation of each Data Breach, including compliance with the Notifiable Data Breaches (NDB) scheme under Part IIIC of the Privacy Act 1988.
The Processor shall make available to the Controller all information necessary to demonstrate compliance with this DPA and shall allow for and contribute to audits and inspections conducted by the Controller or an independent auditor mandated by the Controller.
Audit requests are subject to the following conditions:
This DPA shall become effective upon the date the Controller executes the Service Agreement and shall remain in effect for the duration of the Service Agreement. The obligations of the Processor under this DPA shall survive termination of the Service Agreement to the extent necessary to complete the Processing activities described herein.
Upon termination or expiry of the Service Agreement:
This DPA shall be governed by and construed in accordance with the laws of New South Wales, Australia, without regard to its conflict of laws provisions. Any disputes arising out of or in connection with this DPA shall be subject to the exclusive jurisdiction of the courts of New South Wales.
To the extent that the GDPR applies to the Processing of Personal Data under this DPA, the relevant provisions of the GDPR shall apply in addition to the terms of this DPA, and in the event of conflict, the GDPR provisions shall prevail.
For questions, requests, or notifications relating to this DPA, please contact:
Moirai Health Pty Ltd
Data Protection Contact
Email: privacy@moirai.health
Canberra, ACT 2601, Australia
The Processor shall respond to all DPA-related enquiries within 10 business days.