About this DPA
This Data Processing Agreement (DPA) is made between Bloody Good Tests Pty Ltd (ABN 62 667 990 963) of 16 Nexus Way, Southport QLD 4215, trading as Eirly Health (Eirly, we, us and our), and the organisation that accepts the MSA or an Order Form (the Customer).
It is published at eirly.health/legal/data-processing-agreement and forms part of the Eirly Master Services Agreement published at eirly.health/legal/master-services-agreement, together with any Order Form under it, under which Eirly supplies the Services (the MSA).
Binding by reference. This DPA forms part of the MSA. It is accepted when the Customer accepts the MSA, or an Order Form that refers to it. It is not signed separately. Eirly will countersign a copy on request for a Customer that wants a signed copy. A data processing agreement the parties signed before this version stays in force for its Order Form until the parties replace it in writing.
Effective date. The date from which the MSA applies to the Customer under MSA clause 2.2 or, where an Order Form applies, the Commencement Date under that Order Form. This DPA applies to all Processing from that date.
No Order Form. Where there is no Order Form, "Order Form" in this DPA means the Customer's plan or order in the Platform.
1. Definitions
1.1 In this DPA:
APPs means the Australian Privacy Principles in Schedule 1 to the Privacy Act.
Customer Personal Information means Personal Information that Eirly Processes on behalf of the Customer under the MSA.
Diagnostic Provider means a pathology laboratory, diagnostic imaging provider, specimen collection provider (including mobile or at-home collection providers using their own scheduling or logistics systems), or other third party that performs, or provides diagnostic services necessary to fulfil, an order facilitated by Eirly under the MSA.
Eligible Data Breach has the meaning given in Part IIIC of the Privacy Act.
Health Information, Personal Information and Sensitive Information have the meanings given in the Privacy Act.
Privacy Act means the Privacy Act 1988 (Cth).
Privacy Law means the Privacy Act, the APPs, the Notifiable Data Breaches scheme, and any other law applicable to the Processing of Personal Information in Australia, including State and Territory health records legislation.
Process and Processing mean any operation performed on Personal Information, including collection, storage, use, disclosure, alteration and destruction.
Personnel means Eirly's employees, contractors and agents who have access to Customer Personal Information.
Sub-processor means a third party engaged by Eirly to Process Customer Personal Information.
1.2 Capitalised terms not defined in this DPA have the meaning given in the MSA.
2. Roles of the parties
2.1 No controller/processor distinction under Australian law. The parties acknowledge that the Privacy Act does not adopt the "controller" and "processor" distinction used in European data protection law. Each party is an APP entity in its own right and is directly bound by Privacy Law in respect of the Personal Information it holds. Nothing in this DPA operates to transfer, limit or exclude either party's own obligations under Privacy Law.
2.2 Eirly as service provider. Subject to clause 2.3, Eirly Processes Customer Personal Information on behalf of, and in accordance with the documented instructions of, the Customer for the purposes set out in Schedule 1.
2.3 Eirly acting in its own right. The Customer acknowledges that Eirly acts as an APP entity in its own right, and not on the Customer's instructions, to the extent Eirly:
-
exercises clinical governance over pathology results, including the flagging of out-of-range results and the escalation of critical results, practitioner review gates, and decisions as to whether and when a result is released;
-
generates, signs and retains pathology referrals, and discloses information to Diagnostic Providers as necessary to fulfil an order;
-
creates and retains clinical and business records required by Australian law, including clinical record-retention obligations;
-
discharges its own obligations under Privacy Law, including responding to a request under APP 12 or APP 13 from an individual with whom Eirly has a direct relationship, and assessing and notifying an Eligible Data Breach; or
-
complies with any other requirement of Australian law, or responds to a request from a regulator, court or law enforcement agency.
2.4 Clinical safety prevails. The Customer must not issue an instruction that would require Eirly to release, withhold, alter or delete a pathology result contrary to Eirly's clinical governance framework or applicable clinical standards. Eirly may decline any such instruction, and must notify the Customer promptly if it does so.
2.5 Unlawful instructions. Eirly must notify the Customer if, in its reasonable opinion, an instruction from the Customer would breach Privacy Law, and may suspend Processing under that instruction until it is withdrawn or amended.
3. Processing of Customer Personal Information
3.1 Eirly must Process Customer Personal Information only:
-
in accordance with the Customer's documented instructions, which comprise the MSA, this DPA (including Schedule 1), and the Customer's configuration and use of Eirly's application programming interfaces and platform;
-
as permitted by clause 2.3; or
-
as required by Australian law, in which case clause 3.5 applies.
3.2 Eirly must not sell Customer Personal Information, and must not use Customer Personal Information for its own marketing purposes.
3.3 Eirly may create and use aggregated and de-identified data derived from Customer Personal Information for the purposes of operating, securing, analysing and improving its services, provided that the data is de-identified in accordance with Privacy Law and is not re-identifiable, and is not disclosed in a form that identifies the Customer or any individual. Eirly may publish aggregate statistics, such as totals and averages, that do not identify the Customer or any individual. Eirly must not re-identify that data, and must require any recipient of it, including a Sub-processor, not to re-identify it or attempt to do so.
3.4 The details of the Processing are set out in Schedule 1.
3.5 Government and legal requests. If a regulator, court or law enforcement agency demands access to Customer Personal Information, Eirly must:
-
notify the Customer before disclosing it, where the law allows, so the Customer can respond;
-
where reasonable, challenge a demand that it considers unlawful or overbroad; and
-
disclose only the minimum that the demand lawfully requires.
This clause does not limit Eirly's own duties to regulators and courts under clause 2.3(5), or any duty it has under Privacy Law.
4. Personnel
4.1 Eirly must ensure that Personnel with access to Customer Personal Information:
-
are subject to written confidentiality and data-handling obligations that survive the end of their engagement;
-
are granted access on a least-privilege basis and only to the extent required to perform their role; and
-
receive privacy and information security awareness training on commencement and at least annually thereafter, covering the Privacy Act and the APPs, health information obligations and consent, the Notifiable Data Breaches scheme, and retention and destruction standards.
4.2 Eirly must revoke access to Customer Personal Information promptly when Personnel cease to require it.
4.3 Related bodies corporate. Where a related body corporate of Eirly, or its personnel, has access to Customer Personal Information, Eirly must procure that it complies with this DPA, and Eirly remains liable to the Customer for its acts and omissions as if they were Eirly's own.
5. Security
5.1 Eirly must implement and maintain the technical and organisational measures summarised in Schedule 2, having regard to the state of the art, the costs of implementation, and the nature, scope and purposes of the Processing, and to the risk to individuals, recognising that Customer Personal Information includes Health Information and is therefore Sensitive Information.
5.2 Eirly must not materially reduce the overall level of protection provided by the measures in Schedule 2 during the term of the MSA.
5.3 Vulnerability management. Eirly maintains a vulnerability management program under which automated dependency vulnerability scanning is enabled across its repositories, and identified vulnerabilities are remediated according to the following targets: critical within 14 days and high within 60 days of identification, with medium and low severity vulnerabilities addressed on a best-efforts basis. These targets apply to vulnerabilities identified on or after the Effective date. Vulnerabilities identified before the Effective date are being remediated under Eirly's documented remediation plan, and Eirly will report progress against that plan to the Customer on request under clause 10.1.
5.4 For the avoidance of doubt, clause 5.3 states an obligation as to process and remediation timeframes. Eirly does not warrant that its systems are free from vulnerabilities or security defects.
6. Sub-processors
6.1 The Customer grants Eirly general written authorisation to engage Sub-processors to Process Customer Personal Information.
6.2 The Sub-processors engaged at the date of this DPA, with the Processing each performs and the country in which it occurs, are listed in Schedule 3.
6.3 Before engaging a new Sub-processor to Process Customer Personal Information, or before a Sub-processor begins Processing in a country not shown on the list, Eirly must:
-
assess the Sub-processor's security posture and the location in which it will Process Customer Personal Information; and
-
give at least 30 days' notice, by emailing the Customer's Owners (as defined in the MSA), and Eirly then updates Schedule 3. The notice must identify the Sub-processor, the Processing it will perform, and the country in which that Processing will occur.
6.4 Eirly may give shorter notice, or notify promptly after the change, where a change is urgently needed for security or service continuity. In that case Eirly must give the notice in clause 6.3(2) as soon as practicable.
6.5 The Customer may object to a new Sub-processor within 30 days of the notice, on reasonable grounds relating to the protection of Customer Personal Information. The parties must discuss the objection in good faith. If it cannot be resolved, the Customer may end the affected part of the Services on written notice, without liability for termination, and Eirly must refund the prepaid fees for the period after the Services end.
6.6 Eirly must impose on each Sub-processor obligations that are substantially equivalent to, and no less protective than, those in this DPA, and remains liable to the Customer for the acts and omissions of its Sub-processors as if they were its own.
7. Individual rights
7.1 Taking into account the nature of the Processing, Eirly must provide reasonable assistance to enable the Customer to respond to a request from an individual to access, correct, or otherwise exercise rights in respect of their Personal Information under Privacy Law.
7.2 Eirly must acknowledge a request for assistance under clause 7.1 within 5 business days and provide the assistance within 10 business days, unless a longer period is reasonable having regard to the complexity of the request, in which case Eirly must notify the Customer of the expected timeframe.
7.3 Where an individual makes a request directly to Eirly in respect of an account or record Eirly holds in its own right under clause 2.3, Eirly may respond directly to that individual as required by Privacy Law, and must promptly notify the Customer of any such request that relates to Customer Personal Information.
7.4 Eirly may charge its reasonable costs for assistance under this clause that is materially in excess of the ordinary course, provided it notifies the Customer of the expected cost before incurring it.
8. Data breach
8.1 Eirly must notify the Customer of a suspected or actual unauthorised access to, unauthorised disclosure of, or loss of Customer Personal Information (Security Incident) without undue delay, and in any event within 72 hours of Eirly becoming aware that a Security Incident has occurred and that it affects Customer Personal Information.
8.2 The initial notification must include the information set out in Schedule 4, to the extent known at the time. Eirly must provide further information as it becomes available, and must not delay the initial notification in order to complete its investigation.
8.3 Eirly must take reasonable steps to contain and remediate the Security Incident, and must preserve evidence relevant to it.
8.4 Eirly must cooperate reasonably with the Customer in the Customer's own assessment of whether the Security Incident constitutes an Eligible Data Breach.
8.5 Independent statutory obligation. The parties acknowledge that each party has its own obligation under Part IIIC of the Privacy Act to assess and, where required, notify an Eligible Data Breach to the Office of the Australian Information Commissioner and to affected individuals. Nothing in this DPA displaces, delays or conditions that obligation. Where both parties have a notification obligation in respect of the same Eligible Data Breach, they must consult in good faith and use reasonable endeavours to coordinate the content and timing of their notifications.
8.6 Neither party may name the other in a public statement about a Security Incident without the other's prior written consent, except where required by law or by a regulator.
8.7 Not an admission. A notice under this clause, and any step Eirly takes in response to a Security Incident, is not an admission of fault or liability.
8.8 Unsuccessful attempts. This clause does not apply to unsuccessful or blocked attempts to access Customer Personal Information that do not compromise its security, such as pings, port scans, denied log-in attempts and blocked malicious traffic.
9. Privacy impact assessments
9.1 Eirly must provide the Customer with reasonable assistance, at the Customer's cost, in connection with any privacy impact assessment or consultation with a regulator that the Customer is required to undertake in relation to the Processing, taking into account the information available to Eirly.
10. Audit and assurance
10.1 Eirly must make available to the Customer, on request and no more than once in any 12-month period, information reasonably necessary to demonstrate compliance with this DPA. That information comprises:
-
Eirly's Information Security Policy;
-
a completed security questionnaire in the Customer's reasonable form; and
-
the executive summary of Eirly's most recent independent third-party penetration test, together with a statement of remediation status,
each of which is Confidential Information of Eirly and is provided subject to the confidentiality obligations in the MSA.
10.2 The Customer may conduct an on-site audit of Eirly's compliance with this DPA only:
-
where a law gives the Customer a right to audit that the information under clause 10.1 cannot satisfy;
-
after a Security Incident affecting the Customer's Customer Personal Information, that Eirly has confirmed and that was not caused by the Customer or its personnel; or
-
where a regulator requires the audit.
10.3 An audit under clause 10.2 is subject to each of the following:
-
it may be conducted no more than once in any 12-month period;
-
the Customer gives at least 30 days' written notice;
-
the scope, timing and duration of the audit are agreed in advance, acting reasonably;
-
the audit is conducted during business hours, in a manner that does not unreasonably disrupt Eirly's operations;
-
any third-party auditor is not a competitor of Eirly and is subject to confidentiality obligations no less protective than those in the MSA;
-
the audit does not extend to Eirly's multi-tenant infrastructure, source code, or data of any other customer; and
-
the Customer bears its own costs and Eirly's reasonable costs of supporting the audit, unless the law requires the audit or the audit finds that Eirly has not complied with this DPA, in which case Eirly bears its own costs.
10.4 Eirly is not required to provide the full technical report of a penetration test or vulnerability assessment. Where a critical or high severity finding is identified in a penetration test, Eirly will, on the Customer's request, disclose to the Customer the nature of the finding and the remediation timeline in writing, in addition to the executive summary.
11. Data location and cross-border disclosure
11.1 Eirly stores and Processes Customer Personal Information in Australia, in Amazon Web Services region ap-southeast-2 (Sydney), except as shown for a Sub-processor in Schedule 3.
11.2 Where Eirly uses artificial intelligence services in the provision of the Services, inference is performed on Amazon Bedrock using Australian inference profiles, which route only between Australian regions.
11.3 Sub-processors shown in Schedule 3 as processing data outside Australia do so only for the limited purposes stated there. Before disclosing Personal Information to an overseas recipient, Eirly takes the steps required by APP 8.1 to ensure the recipient does not breach the APPs, unless an exception in APP 8.2 applies.
11.4 Eirly must give notice under clause 6.3 before Processing Customer Personal Information in a country not shown in Schedule 3. The Customer may object within 30 days of the notice on reasonable grounds relating to the protection of Customer Personal Information, and clause 6.5 then applies as if the change were a new Sub-processor.
11.5 Diagnostic Providers. Despite clause 11.1, Eirly discloses Customer Personal Information to Diagnostic Providers as necessary to fulfil an order, as described in clause 2.3(2). Those Diagnostic Providers perform their services in Australia, except that, in the case of pathology, a laboratory may refer a specimen to a specialist reference laboratory outside Australia where the test is not performed domestically. Where that occurs, the referral is made by the Australian laboratory in its own right, under its own obligations under Privacy Law, and the Customer Personal Information disclosed is limited to that necessary to perform and report the test. Some at-home test kits are sent to, and analysed by, laboratories outside Australia. Eirly maintains a list of the Diagnostic Providers it uses and the locations in which they process Customer Personal Information or report results, updates it from time to time, and will make it available to the Customer on request.
12. Retention, return and deletion
12.1 Eirly must retain Customer Personal Information only for as long as necessary for the purposes set out in Schedule 1, or as required by Australian law. The retention periods Eirly applies are set out in section 22 of its Privacy Policy.
12.2 On expiry or termination of the MSA, Eirly must, at the Customer's election (made within the request period in MSA clause 20.5), return Customer Personal Information to the Customer in a structured, commonly used, machine-readable format, or delete it. This happens within the periods in MSA clause 20.5 and, for anything not retained under clause 12.3, in any case within 90 days of the election or of the end of the MSA, whichever is later. Nothing in this clause weakens the periods or rights in MSA clause 20.5.
12.3 Retention override. Clause 12.2 is subject to any obligation of Eirly under Australian law to retain Customer Personal Information, as applied by MSA clause 20.5, including clinical record-retention obligations, which generally require retention of health records for a minimum of 7 years from the date of last service, and in the case of a patient who was a minor at the time of the service, until that patient attains the age of 25 years. Eirly must notify the Customer of the categories of Customer Personal Information it is required to retain and the basis for retention, and must continue to protect that data in accordance with this DPA for so long as it is retained. Where Eirly returns health records to the Customer under clause 12.2, it records the return as a transfer of those records to the Customer.
12.4 The Customer acknowledges that Customer Personal Information contained in backups, archives and audit records is deleted in accordance with Eirly's ordinary retention and expiry cycles, which may extend beyond the period in clause 12.2. Audit records are retained on the following basis:
-
Provenance (the record of who ordered, requested, signed or accessed a record, on whose authority, and when) is retained for as long as the health record it relates to (clause 12.3), in order to meet Australian record-keeping obligations and to evidence delegated ordering.
-
Payload (the content of the request and response, and before-and-after snapshots of changed records) is retained for 12 months and then deleted or de-identified, being retained only for error investigation, security and dispute resolution.
Payload records containing Customer Personal Information are encrypted at the application layer for the period they are held.
12.5 Eirly must certify deletion in writing on request.
13. Artificial intelligence
13.1 Eirly must not use Customer Personal Information to train, fine-tune or otherwise improve any machine learning model, without the Customer's consent. Clause 3.3 is not affected: Eirly may use aggregated and de-identified data derived from Customer Personal Information, on the terms of that clause (including the prohibition on re-identification), to improve the accuracy of its own systems, including its document-reading and result-processing tools. No identifiable Customer Personal Information is used for that purpose, and no Customer Personal Information is used to train a third party's model.
13.2 Eirly must not disclose Customer Personal Information to any third-party artificial intelligence provider. AI functionality within the Services is delivered through Amazon Bedrock within Eirly's own cloud environment, and Eirly holds no direct relationship with any model vendor.
13.3 Access to models is restricted by policy to an explicit allow-list of approved models.
14. Compliance program
14.1 Eirly represents that, as at the date this version of the DPA takes effect:
-
it is working towards SOC 2, and does not yet hold a SOC 2 report or ISO 27001 certification; and
-
an independent penetration test of its externally exposed applications has been completed within the last 12 months.
14.2 Eirly will conduct an independent third-party penetration test of its externally exposed applications at least annually, and will make the executive summary available to the Customer under clause 10.1. Current certifications and the date of the most recent test are available to the Customer on request.
15. Liability
15.1 Each party's liability arising out of or in connection with this DPA is subject to, and counts towards, the limitations and exclusions of liability in the MSA (including MSA clause 22). This DPA does not create a separate or additional cap or indemnity.
16. General
16.1 Precedence. If there is an inconsistency between this DPA and the MSA in relation to the Processing of Personal Information, this DPA prevails to the extent of the inconsistency.
16.2 Term. This DPA takes effect on the Effective date and continues for so long as Eirly Processes Customer Personal Information.
16.3 Governing law. This DPA is governed by the laws of Queensland, Australia, and the parties submit to the exclusive jurisdiction of the courts of Queensland and the Federal Court of Australia, and the courts that hear appeals from them, as under the MSA.
16.4 Variation. Eirly may vary the published DPA by following the variation process in the MSA, which requires at least 30 days' notice. No variation may materially reduce the protection of Customer Personal Information under this DPA without the Customer's agreement. Eirly may update Schedule 3 under clause 6.3 and the summary in Schedule 2 under clause 5.2. A copy of this DPA that the parties have signed, or that is annexed to a signed Order Form, may be varied only by a document signed by both parties.
16.5 Severability. If a provision of this DPA is void or unenforceable, it is severed and the remainder continues in force.
17. Customer obligations
17.1 The Customer warrants that, insofar as it is aware, in respect of Customer Personal Information it provides to or has Eirly collect:
(a) it will take reasonable steps to make notifications required under APP 5, and hold all consents and authorisations required under Privacy Law, for Eirly to Process that Customer Personal Information for the purposes set out in Schedule 1, including the collection, use and disclosure of Health Information;
(b) its instructions to Eirly, and its configuration and use of Eirly's platform and APIs, comply with Privacy Law; and
(c) it is entitled to disclose the Customer Personal Information to Eirly and to authorise the Processing contemplated by this DPA.
17.2 The Customer will use reasonable endeavours to ensure the accuracy, quality and legality of Customer Personal Information and of the means by which it acquired that Customer Personal Information.
Acceptance
This DPA is not signed separately. It is accepted by the Customer accepting the MSA, online or by signing an Order Form, and takes effect on the Effective date. Eirly will countersign a copy on request.
Schedule 1: Details of Processing
| Item | Detail |
|---|---|
| Subject matter | Provision of diagnostic ordering, pathology result ingestion and normalisation, referral generation, clinical governance, and result delivery |
| Duration | The term of the MSA, plus any period of retention required under clause 12.3 |
| Nature of Processing | Collection, receipt, storage, normalisation, encryption, clinical review, transmission, display and deletion |
| Purpose | To enable the Customer to offer Diagnostic Services to its end users, and to enable Eirly to fulfil orders, exercise clinical governance and meet its own legal obligations |
| Categories of individual | The Customer's end users and patients; the Customer's practitioners, clinicians and staff |
| Categories of Personal Information | Name; date of birth; residential and postal address; email address; telephone number; gender; Medicare number, where the Customer's end users are billed through Medicare |
| Sensitive Information / Health Information | Pathology results and biomarker values; reference ranges and out-of-range flags; pathology referrals; HL7 messages received from laboratories; clinical notes; test and panel selections; consents |
| Excluded | Eirly does not Process payment card data. Payments, where applicable, are processed by the payments Sub-processor listed in Schedule 3. |
Schedule 2: Technical and organisational measures (summary)
Eirly maintains the measures below, which are drawn from its Information Security Policy. The detailed Information Security Policy is given to the Customer on request under clause 10.1, as Confidential Information of Eirly.
-
Encryption. Data is encrypted in transit. Health Information and Personal Information are encrypted at rest, and additionally encrypted at the application layer, with separate keys for distinct data domains. Keys and credentials are held in a managed secret store.
-
Access control. Access is role-based and least-privilege, enforced on the server. Administrative functions are separated from customer-facing functions. Multi-factor authentication is enforced for Personnel. Access is provisioned and revoked against a documented process, and administrative actions are recorded in an audit log.
-
Network and infrastructure. Infrastructure is defined as code and deployed through controlled pipelines. Databases are not publicly accessible. Production is segregated from development and testing environments.
-
Secure development. Code changes are peer-reviewed before release and tested automatically, and database changes run through a gated deployment step.
-
Logging and monitoring. Application and infrastructure telemetry is monitored with alerting. Observability logs record resource identifiers rather than Personal Information or clinical data. Audit and API request records are a separate system, encrypt Personal Information and clinical content at the application layer, and are retained on the basis in clause 12.4.
-
Resilience. Databases are replicated, backed up with point-in-time recovery, and protected against accidental deletion. Eirly maintains recovery objectives and tests restoration.
-
Personnel and endpoint. Personnel are bound by confidentiality, trained on joining and at least annually, and use encrypted, locked devices. Physical security of hosting facilities is provided by Eirly's cloud provider.
-
Testing. An independent test of the external applications is done at least annually (clause 14.2).
Schedule 3: Sub-processors
Changes to this list are made under clause 6: the Customer's Owners are emailed at least 30 days before a new Sub-processor Processes Customer Personal Information.
Primary Processing location: Australia (AWS ap-southeast-2, Sydney).
AI inference: Amazon Bedrock, Australian inference profiles.
| Sub-processor | Purpose | Location |
|---|---|---|
| Amazon Web Services | Cloud hosting, storage, AI inference | Australia |
| Datadog | Application logs and metrics: request details and resource identifiers, and a random user identifier for a signed-in user. No clinical data is sent by design, though free text may occasionally include some | Japan |
| Twilio (SendGrid) | Transactional email and SMS | United States |
| Stripe | Payment processing | United States |
| Intercom | Customer support chat: a signed-in user's name, email address and account status, and anything typed into a conversation. | United States |
| Slack | Internal operational notifications | United States |
| PostHog | Product analytics and feature flags: a signed-in user's random user identifier, email address and usage events | United States |
| Google Analytics | Page-view analytics: pages visited, and a signed-in user's random user identifier and account type | United States |
Datadog's log storage is in Japan. Eirly is moving it to an Australian region and will give notice under clause 6 before any change. Clinical data is not sent to those logs by design.
Schedule 4: Security Incident notification particulars
A notification under clause 8.1 must include, to the extent known:
-
the nature of the Security Incident, including the categories and approximate number of individuals and records affected;
-
the date or date range on which it occurred and the date Eirly confirmed it;
-
the likely consequences of the Security Incident;
-
the measures taken or proposed to contain and remediate it, and to mitigate its adverse effects;
-
whether Eirly considers the Security Incident may constitute an Eligible Data Breach; and
-
the name and contact details of Eirly's Privacy Officer.
Security and privacy contacts: security@eirly.health; Privacy Officer, privacy@eirly.health
Schedule 5: European data protection
This Schedule applies only if, and from the date on which, the Customer notifies Eirly in writing that it Processes personal data through the Services that is subject to Regulation (EU) 2016/679 (GDPR) or the UK GDPR.
Until that notice is given, this Schedule has no effect, Eirly makes no representation as to GDPR compliance, and the parties acknowledge that the Processing under this DPA is governed by Australian Privacy Law.
On receipt of such a notice, the parties will negotiate in good faith and execute an addendum containing terms meeting the requirements of Article 28(3) of the GDPR, mapped to the corresponding clauses of this DPA.