Alloovium Data Processing Agreement
This Alloovium Data Processing Agreement (this “DPA”) supplements the Agreement between Provider and Customer. It applies to every Order Form under the Agreement. Customer and Provider agree to this DPA when they sign or electronically accept an Order Form under the Agreement. No separate signature is needed. If Customer asks for a signed copy of this DPA, the parties may sign one. A signed copy does not change the terms of this DPA.
Capitalised words have the meanings given in Section 1 (Definitions). All other capitalised words have the meanings given in the Agreement.
1. Definitions
1.1 “Agreement” means the Alloovium Cloud Service Agreement between Provider and Customer (the “CSA”), together with each Order Form that references it.
1.2 “Applicable Laws” means the laws, rules, regulations, court orders, and other binding requirements of a relevant government authority that apply to or govern a party.
1.3 “Applicable Data Protection Laws” means the Applicable Laws that govern how the Service may process or use an individual’s personal information, personal data, personally identifiable information, or other similar term.
1.4 “Approved Subprocessors” means the Subprocessors on the list described in Section 4.1.
1.5 “Controller” will have the meaning(s) given in the Applicable Data Protection Laws for the company that determines the purpose and extent of Processing Personal Data.
1.6 “Customer” means the customer named in the Order Form.
1.7 “Customer Personal Data” means Personal Data that Customer uploads or provides to Provider as part of the Service and that is governed by this DPA.
1.8 “DPA” means this Alloovium Data Processing Agreement, including its Annexes and the policies and documents it references.
1.9 “EEA SCCs” means the standard contractual clauses annexed to the European Commission’s Implementing Decision 2021/914 of 4 June 2021 on standard contractual clauses for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the European Council.
1.10 “European Economic Area” or “EEA” means the member states of the European Union, Norway, Iceland, and Liechtenstein.
1.11 “GDPR” means European Union Regulation 2016/679 as implemented by local law in the relevant EEA member nation.
1.12 “Governing Member State” means Ireland for EEA transfers, and England and Wales for UK transfers.
1.13 “notice period” has the meaning given in Section 4.2.
1.14 “Personal Data” will have the meaning(s) given in the Applicable Data Protection Laws for personal information, personal data, or other similar term.
1.15 “Processing” or “Process” will have the meaning(s) given in the Applicable Data Protection Laws for any use of, or performance of a computer operation on, Personal Data, including by automatic methods.
1.16 “Processor” will have the meaning(s) given in the Applicable Data Protection Laws for the company that Processes Personal Data on behalf of the Controller.
1.17 “Provider” means the Alloovium entity named as Provider in the Order Form, as Section 13.3(a) of the CSA sets out.
1.18 “Provider Security Contact” means security@alloovium.com.
1.19 “Report” means audit reports prepared by another company according to the standards defined in the Security Policy on behalf of Provider.
1.20 “Restricted Transfer” means (a) where the GDPR applies, a transfer of personal data from the EEA to a country outside of the EEA which is not subject to an adequacy determination by the European Commission; and (b) where the UK GDPR applies, a transfer of personal data from the United Kingdom to any other country which is not subject to adequacy regulations adopted pursuant to Section 17A of the United Kingdom Data Protection Act 2018.
1.21 “Security Incident” means a Personal Data Breach as defined in Article 4 of the GDPR.
1.22 “Security Policy” means Provider’s security commitment in Section 2.4 of the CSA, including the Alloovium Information Security Addendum.
1.23 “Service” means the product and/or services described in the Agreement.
1.24 “Special Category Data” will have the meaning given in Article 9 of the GDPR.
1.25 “Subprocessor” will have the meaning(s) given in the Applicable Data Protection Laws for a company that, with the approval and acceptance of Controller, assists the Processor in Processing Personal Data on behalf of the Controller.
1.26 “UK GDPR” means European Union Regulation 2016/679 as implemented by section 3 of the United Kingdom’s European Union (Withdrawal) Act of 2018 in the United Kingdom.
1.27 “UK Addendum” means the international data transfer addendum to the EEA SCCs issued by the Information Commissioner for Parties making Restricted Transfers under S119A(1) Data Protection Act 2018.
1.28 Omitted details. If an Annex omits or does not define a detail, the default meaning is “none” or “not applicable”, and the clause, sentence or section that depends on it does not apply to this DPA.
2. Roles and contacts
2.1 Provider as Processor. In situations where Customer is a Controller of the Customer Personal Data, Provider will be deemed a Processor that is Processing Personal Data on behalf of Customer.
2.2 Provider as Subprocessor. In situations where Customer is a Processor of the Customer Personal Data, Provider will be deemed a Subprocessor of the Customer Personal Data.
2.3 Provider contacts. Provider’s contacts for this DPA are:
(a) contract notices: legal@alloovium.com;
(b) privacy contact, help to subscribe to Subprocessor updates, and objections: privacy@alloovium.com; and
(c) security reports and Security Incident contact: security@alloovium.com (the Provider Security Contact).
3. Processing
3.1 Processing details. Annex 1 Part B describes the subject matter, nature, purpose, and duration of this Processing, as well as the Categories of Personal Data collected and Categories of Data Subjects.
3.2 Processing instructions. Customer instructs Provider to Process Customer Personal Data: (a) to provide and maintain the Service; (b) as may be further specified through Customer’s use of the Service; (c) as documented in the Agreement; and (d) as documented in any other written instructions given by Customer and acknowledged by Provider about Processing Customer Personal Data under this DPA. Provider will abide by these instructions unless prohibited from doing so by Applicable Laws. Provider will immediately inform Customer if it is unable to follow the Processing instructions. Customer has given and will only give instructions that comply with Applicable Laws.
3.3 Processing by Provider. Provider will only Process Customer Personal Data in accordance with this DPA, including the details in Annex 1. If Provider updates the Service to update existing or include new products, features, or functionality, Provider may change the Categories of Data Subjects, Categories of Personal Data, Special Category Data, Special Category Data Restrictions or Safeguards, Frequency of Transfer, Nature and Purpose of Processing, and Duration of Processing as needed to reflect the updates by notifying Customer of the updates and changes.
3.4 Customer Processing. Where Customer is a Processor and Provider is a Subprocessor, Customer will comply with all Applicable Laws that apply to Customer’s Processing of Customer Personal Data. Customer’s agreement with its Controller will similarly require Customer to comply with all Applicable Laws that apply to Customer as a Processor. In addition, Customer will comply with the Subprocessor requirements in Customer’s agreement with its Controller.
3.5 Consent to Processing. Customer has complied with and will continue to comply with all Applicable Data Protection Laws concerning its provision of Customer Personal Data to Provider and/or the Service, including making all disclosures, obtaining all consents, providing adequate choice, and implementing relevant safeguards required under Applicable Data Protection Laws.
4. Subprocessors
4.1 Approved Subprocessors. Provider will not provide, transfer, or hand over any Customer Personal Data to a Subprocessor unless Customer has approved the Subprocessor. The list of Approved Subprocessors is available at https://alloovium.com/legal/subprocessors. The current list of Approved Subprocessors includes the identities of the Subprocessors, their country of location, and their anticipated Processing tasks.
4.2 Notice of changes. Provider will inform Customer at least 30 days in advance and in writing of any intended changes to the Approved Subprocessors whether by addition or replacement of a Subprocessor, which allows Customer to have enough time to object to the changes before Provider begins using the new Subprocessor(s). Provider gives notice of an intended change by publishing an update in its Trust Centre and emailing subscribers to its Subprocessor updates. Customer may subscribe through the Trust Centre or contact privacy@alloovium.com for subscription assistance. Provider will give Customer the information necessary to allow Customer to exercise its right to object to the change to Approved Subprocessors. The 30-day period for Customer to object under Section 4.3 starts on the date of that notice. In this DPA, the “notice period” is that 30-day period.
4.3 Objections. Customer has 30 days after notice of a change to the Approved Subprocessors to object, otherwise Customer will be deemed to accept the changes. Customer sends an objection by email to privacy@alloovium.com, with its reasons. If Customer objects to the change within 30 days of notice, Customer and Provider will cooperate in good faith to resolve Customer’s objection or concern, and will discuss the objection in good faith within the notice period. If they do not resolve the objection, Customer may stop using the features of the Service that use the new Subprocessor. On request, Provider will tell Customer which features those are. This Section 4.3 does not limit Customer’s other rights under the Agreement.
4.4 EU and UK objection rider. This Section 4.4 applies automatically, without further agreement, where the GDPR or the UK GDPR applies to Provider’s Processing of Customer Personal Data for Customer. If Provider and Customer have not resolved an objection under Section 4.3 by the end of the notice period, Customer may terminate each Order Form under which the Service uses the new Subprocessor. Customer does this by written notice to Provider within 30 days after the end of the notice period. Provider will refund the prepaid Fees for the part of the Subscription Period of that Order Form that remains after termination. Termination under this Section 4.4 is not a breach of the Agreement by either party.
4.5 Emergency replacement. Provider may replace an Approved Subprocessor without giving 30 days’ notice in advance if there is an emergency. An emergency is: (a) an outage or failure of the Subprocessor’s service that stops the Service or materially degrades it; or (b) a security event that affects the Subprocessor and puts Customer Personal Data at risk. In an emergency, Provider will give notice of the replacement under Section 4.2 as soon as possible, and will state the reason for it. The replacement Subprocessor is subject to Sections 4.6 and 4.7. Customer may object to the replacement under Section 4.3, and the notice period starts on the date of Provider’s notice.
4.6 Subprocessor agreements.
(a) When engaging a Subprocessor, Provider will have a written agreement with the Subprocessor that ensures the Subprocessor only accesses and uses Customer Personal Data (i) to the extent required to perform the obligations subcontracted to it, and (ii) consistent with the terms of Agreement.
(b) If the GDPR applies to the Processing of Customer Personal Data, (i) the data protection obligations described in this DPA (as referred to in Article 28(3) of the GDPR, if applicable) are also imposed on the Subprocessor, and (ii) Provider’s agreement with the Subprocessor will incorporate these obligations, including details about how Provider and its Subprocessor will coordinate to respond to inquiries or requests about the Processing of Customer Personal Data. In addition, Provider will share, at Customer’s request, a copy of its agreements (including any amendments) with its Subprocessors. To the extent necessary to protect business secrets or other confidential information, including personal data, Provider may redact the text of its agreement with its Subprocessor prior to sharing a copy.
4.7 Liability for Subprocessors. Provider remains fully liable for all obligations subcontracted to its Subprocessors, including the acts and omissions of its Subprocessors in Processing Customer Personal Data. Provider will notify Customer of any failure by its Subprocessors to fulfil a material obligation about Customer Personal Data under the agreement between Provider and the Subprocessor.
5. Processing locations and restricted transfers
5.1 Processing locations. Documents and other content that Customer uploads to the Service, including the Customer Personal Data in them, are stored in Google Cloud in Sydney, Australia. Approved Subprocessors process some Customer Personal Data outside Australia, in the United States and in the other locations stated on the list of Approved Subprocessors. This includes AI model providers, sign-in, and error and usage tracking.
5.2 Authorisation. Customer agrees that Provider may transfer Customer Personal Data outside the EEA, the United Kingdom, or other relevant geographic territory as necessary to provide the Service. If Provider transfers Customer Personal Data to a territory for which the European Commission or other relevant supervisory authority has not issued an adequacy decision, Provider will implement appropriate safeguards for the transfer of Customer Personal Data to that territory consistent with Applicable Data Protection Laws.
5.3 Ex-EEA transfers. Customer and Provider agree that if the GDPR protects the transfer of Customer Personal Data, the transfer is from Customer from within the EEA to Provider outside of the EEA, and the transfer is not governed by an adequacy decision made by the European Commission, then by entering into this DPA, Customer and Provider are deemed to have signed the EEA SCCs and their Annexes, which are incorporated by reference. Any such transfer is made pursuant to the EEA SCCs, which are completed as follows:
(a) Module Two (Controller to Processor) of the EEA SCCs apply when Customer is a Controller and Provider is Processing Customer Personal Data for Customer as a Processor.
(b) Module Three (Processor to Sub-Processor) of the EEA SCCs apply when Customer is a Processor and Provider is Processing Customer Personal Data on behalf of Customer as a Subprocessor.
(c) For each module, the following applies (when applicable):
(i) The optional docking clause in Clause 7 does not apply;
(ii) In Clause 9, Option 2 (general written authorization) applies, and the minimum time period for prior notice of Subprocessor changes is 30 days;
(iii) In Clause 11, the optional language does not apply;
(iv) All square brackets in Clause 13 are removed;
(v) In Clause 17 (Option 1), the EEA SCCs will be governed by the laws of Governing Member State;
(vi) In Clause 18(b), disputes will be resolved in the courts of the Governing Member State; and
(vii) Annexes 1 to 3 of this DPA contain the information required in Annex I, Annex II, and Annex III of the EEA SCCs.
5.4 Ex-UK transfers. Customer and Provider agree that if the UK GDPR protects the transfer of Customer Personal Data, the transfer is from Customer from within the United Kingdom to Provider outside of the United Kingdom, and the transfer is not governed by an adequacy decision made by the United Kingdom Secretary of State, then by entering into this DPA, Customer and Provider are deemed to have signed the UK Addendum and their Annexes, which are incorporated by reference. Any such transfer is made pursuant to the UK Addendum, which is completed as follows:
(a) Section 5.3 of this DPA contains the information required in Table 2 of the UK Addendum.
(b) Table 4 of the UK Addendum is modified as follows: Neither party may end the UK Addendum as set out in Section 19 of the UK Addendum; to the extent ICO issues a revised Approved Addendum under Section 18 of the UK Addendum, the parties will work in good faith to revise this DPA accordingly.
(c) Annexes 1 to 3 of this DPA contain the information required by Annex 1A, Annex 1B, Annex II, and Annex III of the UK Addendum.
5.5 Other international transfers. For Personal Data transfers where Swiss law (and not the law in any EEA member state or the United Kingdom) applies to the international nature of the transfer, references to the GDPR in Clause 4 of the EEA SCCs are, to the extent legally required, amended to refer to the Swiss Federal Data Protection Act or its successor instead, and the concept of supervisory authority will include the Swiss Federal Data Protection and Information Commissioner.
6. Security Incidents
6.1 Security Incident response. Upon becoming aware of any Security Incident, Provider will: (a) notify Customer without undue delay when feasible, but no later than 72 hours after becoming aware of the Security Incident; (b) provide timely information about the Security Incident as it becomes known or as is reasonably requested by Customer; and (c) promptly take reasonable steps to contain and investigate the Security Incident. Provider’s notification of or response to a Security Incident as required by this DPA will not be construed as an acknowledgment by Provider of any fault or liability for the Security Incident.
7. Audits and reports
7.1 Audit rights. Provider will give Customer all information reasonably necessary to demonstrate its compliance with this DPA and Provider will allow for and contribute to audits, including inspections by Customer, to assess Provider’s compliance with this DPA. However, Provider may restrict access to data or information if Customer’s access to the information would negatively impact Provider’s intellectual property rights, confidentiality obligations, or other obligations under Applicable Laws. Customer acknowledges and agrees that it will only exercise its audit rights under this DPA and any audit rights granted by Applicable Data Protection Laws by instructing Provider to comply with the reporting and due diligence requirements below. Provider will maintain records of its compliance with this DPA for 3 years after the DPA ends.
7.2 Security reports. Customer acknowledges that Provider is regularly audited against the standards defined in the Security Policy by independent third-party auditors. Upon written request, Provider will give Customer, on a confidential basis, a summary copy of its then-current Report so that Customer can verify Provider’s compliance with the standards defined in the Security Policy. The Reports are: Provider’s SOC 2 Type I report, and its SOC 2 Type II report and ISO 27001 certification when issued.
7.3 Security due diligence. In addition to the Report, Provider will respond to reasonable requests for information made by Customer to confirm Provider’s compliance with this DPA, including responses to information security, due diligence, and audit questionnaires, or by giving additional information about its information security programme. All such requests must be in writing and made to the Provider Security Contact and may only be made once a year.
8. Cooperation
8.1 Response to inquiries. If Provider receives any inquiry or request from anyone else about the Processing of Customer Personal Data, Provider will notify Customer about the request and Provider will not respond to the request without Customer’s prior consent. Examples of these kinds of inquiries and requests include a judicial or administrative or regulatory agency order about Customer Personal Data where notifying Customer is not prohibited by Applicable Law, or a request from a data subject. If allowed by Applicable Law, Provider will follow Customer’s reasonable instructions about these requests, including providing status updates and other information reasonably requested by Customer. If a data subject makes a valid request under Applicable Data Protection Laws to delete or opt out of Customer’s giving of Customer Personal Data to Provider, Provider will assist Customer in fulfilling the request according to the Applicable Data Protection Law. Provider will cooperate with and provide reasonable assistance to Customer, at Customer’s expense, in any legal response or other procedural action taken by Customer in response to a third-party request about Provider’s Processing of Customer Personal Data under this DPA.
8.2 DPIAs and DTIAs. If required by Applicable Data Protection Laws, Provider will reasonably assist Customer in conducting any mandated data protection impact assessments or data transfer impact assessments and consultations with relevant data protection authorities, taking into consideration the nature of the Processing and Customer Personal Data.
9. Deletion and return
9.1 Deletion by Customer. Provider will enable Customer to delete Customer Personal Data in a manner consistent with the functionality of the Services. Provider will comply with this instruction as soon as reasonably practicable except where further storage of Customer Personal Data is required by Applicable Law.
9.2 Deletion at the end of the Agreement.
(a) After the DPA expires, Provider will return or delete Customer Personal Data at Customer’s instruction unless further storage of Customer Personal Data is required or authorised by Applicable Law. Unless Customer instructs Provider to return Customer Personal Data, Provider will delete Customer Personal Data from the Service’s active systems within 60 days after the Agreement expires or is terminated, unless Applicable Law requires otherwise. Copies of Customer Personal Data in backups, earlier document versions and archives are deleted under Provider’s retention schedule, and stay subject to this DPA until they are deleted. If return or destruction is impracticable or prohibited by Applicable Laws, Provider will make reasonable efforts to prevent additional Processing of Customer Personal Data and will continue to protect the Customer Personal Data remaining in its possession, custody, or control. For example, Applicable Laws may require Provider to continue hosting or Processing Customer Personal Data.
(b) If Customer and Provider have entered the EEA SCCs or the UK Addendum as part of this DPA, Provider will only give Customer the certification of deletion of Personal Data described in Clause 8.1(d) and Clause 8.5 of the EEA SCCs if Customer asks for one.
10. Limitation of liability
10.1 Liability caps and damages waiver. To the maximum extent permitted under Applicable Data Protection Laws, each party’s total cumulative liability to the other party arising out of or related to this DPA will be subject to the waivers, exclusions, and limitations of liability stated in the Agreement.
10.2 No separate DPA cap. This DPA has no separate covered claim or liability cap. For the limits in the Agreement, a breach of this DPA by either party is a breach of Section 5 (Data protection) of the CSA.
10.3 Related-party claims. Any claims made against Provider or its Affiliates arising out of or related to this DPA may only be brought by the Customer entity that is a party to the Agreement.
10.4 Exceptions. This DPA does not limit any liability to an individual about the individual’s data protection rights under Applicable Data Protection Laws. In addition, this DPA does not limit any liability between the parties for violations of the EEA SCCs or UK Addendum.
11. California
11.1 Service provider relationship. To the extent California Consumer Privacy Act, Cal. Civ. Code § 1798.100 et seq (“CCPA”) applies, the parties acknowledge and agree that Provider is a service provider and is receiving Personal Data from Customer to provide the Service as agreed in the Agreement and detailed in Annex 1 Part B (see Nature and Purpose of Processing), which constitutes a limited and specified business purpose. Provider will not sell or share any Personal Data provided by Customer under the Agreement. In addition, Provider will not retain, use, or disclose any Personal Data provided by Customer under the Agreement except as necessary for providing the Service for Customer, as stated in the Agreement, or as permitted by Applicable Data Protection Laws. Provider certifies that it understands the restrictions of this paragraph and will comply with all Applicable Data Protection Laws. Provider will notify Customer if it can no longer meet its obligations under the CCPA.
12. Precedence, governing law and term
12.1 Conflicts between documents. This DPA forms part of and supplements the Agreement. If there is any inconsistency between this DPA, the Agreement, or any of their parts, the part listed earlier will control over the part listed later for that inconsistency: (1) the EEA SCCs or the UK Addendum, (2) this DPA, and then (3) the Agreement.
12.2 Governing law and courts. The governing law and Chosen Courts of the Agreement apply to this DPA. Section 5 sets the law and courts for the EEA SCCs and the UK Addendum.
12.3 Term. This DPA will start when Provider and Customer sign or electronically accept an Order Form under the Agreement and will continue until the Agreement expires or is terminated. However, Provider and Customer will each remain subject to the obligations in this DPA and Applicable Data Protection Laws until Customer stops transferring Customer Personal Data to Provider and Provider stops Processing Customer Personal Data.
Annex 1: Processing details
Part A: List of parties
| Data Exporter | Name: Customer Address: the address of Customer stated in the Order Form. Contact Person: Customer's notice contact stated in the Order Form. Activities relevant to transfer: See Annex 1 Part B Role: Controller. Where Customer Processes Customer Personal Data on behalf of another Controller, Customer's role is Processor. |
|---|---|
| Data Importer | Name: Provider Address: legal@alloovium.com. Provider's postal address is stated in the Order Form. Contact Person: Provider's privacy contact, privacy@alloovium.com Activities relevant to transfer: See Annex 1 Part B Role: Processor |
Part B: Description of transfer and processing activities
| Service | The Alloovium cloud service described in the Order Form: an AI workspace for construction businesses that extracts, organises, generates, and automates work on project and business documents. |
|---|---|
| Categories of Data Subjects |
|
| Categories of Personal Data |
|
| Special Category Data | Is special category data Processed? Yes. Health information can appear in the documents described above, for example in incident and injury reports. |
| Special Category Data Restrictions or Safeguards | See Security Policy. Customer may submit Special Category Data only where it is incidental to construction project or business documents that Customer processes in its ordinary use of the Service, as the Agreement permits. Customer must not use the Service for any collection whose main purpose is to hold Special Category Data. Customer is responsible for its lawful basis, notices, and consents for that data. |
| Frequency of Transfer | Continuous |
| Nature and Purpose of Processing | Provider will Process Customer Personal Data as instructed in Section 3.3 of this DPA. The nature of processing includes:
Purpose: to provide, maintain, support, and secure the Service for Customer under the Agreement. |
| Duration of Processing | Provider will process Customer Personal Data as long as required (i) to conduct the Processing activities instructed in Section 3.2(a) to (d) of this DPA; or (ii) by Applicable Laws. |
Part C: Competent supervisory authority
| Competent Supervisory Authority | The supervisory authority will be the supervisory authority of the data exporter, as determined in accordance with Clause 13 of the EEA SCCs or the relevant provision of the UK Addendum. |
|---|
Annex 2: Technical and organisational security measures
| Technical and Organisational Security Measures | See Security Policy |
|---|
Annex 3: Subprocessors
| List of Subprocessors | The Approved Subprocessors, listed at https://alloovium.com/legal/subprocessors. |
|---|
Source and licence
This DPA is adapted from the Common Paper Data Processing Agreement Standard Terms (Version 1.1), available at https://commonpaper.com/standards/data-processing-agreement/1.1/ under the CC BY 4.0 licence (https://creativecommons.org/licenses/by/4.0/). Alloovium has modified, rearranged and added to that text. Common Paper is not a party to this DPA and has not reviewed it. Common Paper does not endorse this DPA.