Alloovium Information Security Addendum
1. Purpose and status
1.1 This Information Security Addendum (Addendum) is the Information Security Addendum referred to in Section 2.4 (Security) of the Alloovium Cloud Service Agreement (CSA). It forms part of the Agreement between Provider and Customer.
1.2 This Addendum sets out the security measures Provider maintains for the Cloud Service and for Customer Content. It adds to, and does not reduce, Provider’s obligations under the CSA, including Section 5 (Data protection) and Section 11 (Confidentiality).
1.3 Provider means the Alloovium entity named as Provider in the Order Form, as Section 13.3(a) of the CSA sets out. This Addendum applies without change whether Provider is Alloovium Pty Ltd or Alloovium, Inc.
1.4 The Data Processing Agreement described in Section 1.2(a) of the CSA (DPA) applies to every Customer. If this Addendum and the DPA conflict for Personal Data, the DPA controls, as Section 5.1 of the CSA provides.
2. Definitions
2.1 Capitalised words that this Addendum does not define have the meanings given in the CSA or the Order Form.
2.2 Personnel means Provider’s employees and individual contractors.
2.3 Security Incident means a confirmed unauthorised access to, or acquisition, disclosure, alteration, loss, or destruction of, Customer Content while Provider or a Subprocessor stores, transmits, or otherwise processes it.
2.4 Subprocessor means a third party that Provider engages to process Customer Content in order to provide the Cloud Service.
3. Security programme
3.1 Provider maintains a written information security programme. Provider’s management approves the programme’s policies, which cover at least: information security, access control, cryptography, data management, incident response, business continuity and disaster recovery, third-party management, and risk management.
3.2 Provider reviews these policies at least once every 12 months and updates them as needed.
3.3 Provider designs the programme with reference to the AICPA Trust Services Criteria and ISO/IEC 27001. This clause describes the reference frameworks only. It does not state that Provider holds any certification or attestation. Provider describes its current audit status in its Trust Centre at https://alloovium.com/legal/trust. The Trust Centre is for information only and does not form part of the Agreement.
4. Hosting and data location
4.1 Provider hosts the Cloud Service on Google Cloud. Provider stores the documents that Customer submits to the Cloud Service, and the content that the Cloud Service generates from them, at rest in Google Cloud in Sydney, Australia, with the overseas processing listed in the Subprocessor list described in Section 11.
4.2 Some Subprocessors store or process Customer Content outside Australia, including in the United States, to provide the Cloud Service. These include the artificial intelligence model providers that process Customer Content to answer User requests, the authentication provider that stores User account details, and the error and usage tracking providers. The Subprocessor list described in Section 11 states the location of each Subprocessor.
4.3 Sections 4.1 and 4.2 apply whichever Alloovium entity is Provider.
5. Encryption
5.1 Provider encrypts Customer Content in transit over public networks using TLS 1.2 or higher.
5.2 Provider encrypts Customer Content at rest in the Cloud Service’s databases and document storage using AES-256 or an equivalent industry-standard algorithm.
5.3 Provider encrypts the credentials that the Cloud Service stores to connect to Customer’s third-party systems.
6. Access control
6.1 Provider logically separates Customer Content from the data of Provider’s other customers.
6.2 Provider limits Personnel access to Customer Content in production systems to authorised Personnel who need that access to provide, support, or secure the Cloud Service.
6.3 Provider requires multi-factor authentication for Personnel access to the administrative consoles of its production hosting environments.
6.4 Provider logs Personnel access to production Customer Content.
6.5 Provider removes a person’s access to production systems promptly when that person no longer needs it, including when the person leaves Provider.
6.6 Provider reviews Personnel access to production systems at least once every 12 months.
6.7 Provider makes these features available in the Cloud Service for Customer to use: multi-factor authentication for Users, single sign-on through supported identity providers, and role-based permissions. Customer is responsible for configuring them for its Users.
7. Personnel
7.1 Personnel with access to Customer Content are bound by confidentiality obligations consistent with Section 11.4 (Permitted disclosures) of the CSA.
7.2 Personnel complete information security awareness training when they join Provider and at least once every 12 months after that.
8. Development and change management
8.1 Provider maintains a documented secure development policy for the Cloud Service.
8.2 Provider manages changes to the Cloud Service’s source code in a version control system and tests changes before it releases them to production.
9. Vulnerability management and monitoring
9.1 Provider scans the Cloud Service’s software dependencies for known vulnerabilities using automated tools.
9.2 Provider remediates identified vulnerabilities in order of risk.
9.3 Provider monitors the Cloud Service for errors and availability.
9.4 Any person may report a suspected vulnerability in the Cloud Service to security@alloovium.com.
10. Artificial intelligence processing
10.1 Provider uses artificial intelligence model Subprocessors only under terms or account settings that prohibit them from using Customer Content to train or improve their models.
10.2 This Section adds to, and does not reduce, Section 4.3 (Machine learning) of the CSA.
11. Subprocessors
11.1 Provider maintains a list of its Subprocessors, with the processing each performs and its location, at https://alloovium.com/legal/subprocessors.
11.2 Provider engages each Subprocessor under a written agreement that requires the Subprocessor to protect Customer Content with confidentiality and security obligations at least as protective as those in the Agreement, as Section 11.4 of the CSA requires.
11.3 Provider updates the Subprocessor list before a new Subprocessor begins to process Customer Content. The DPA sets the advance notice period, how Provider gives notice, and Customer’s right to object. Customer may subscribe to Subprocessor updates through the Trust Centre. Customer may contact privacy@alloovium.com for subscription assistance and to send objections.
12. Security Incidents
12.1 Provider maintains a documented incident response plan.
12.2 Provider will notify Customer without undue delay after becoming aware of a Security Incident, and in any event within 72 hours after becoming aware of it.
12.3 Provider will send the notice to Customer’s notice address in the Order Form and to Customer’s account administrator.
12.4 The notice will describe, to the extent then known: the nature of the Security Incident, the categories of Customer Content affected, the steps Provider has taken and will take, and a contact person. Customer may also contact Provider about the Security Incident at security@alloovium.com. Provider will update Customer as it learns more.
12.5 Provider will take reasonable steps to contain, investigate, and mitigate the Security Incident.
12.6 Provider will give Customer reasonable assistance to meet Customer’s own notification obligations under Applicable Data Protection Laws in relation to the Security Incident.
12.7 Provider will comply with the data breach notification obligations that apply to Provider under Applicable Data Protection Laws.
12.8 Provider’s notice of a Security Incident is not an admission of fault or liability.
12.9 Customer may report a suspected Security Incident to security@alloovium.com.
13. Backup and recovery
13.1 Provider backs up Customer Content stored in the Cloud Service’s databases at least once every day. Provider keeps 14 daily database backups and 7 days of point-in-time recovery for those databases.
13.2 Provider keeps document storage versioned, so that it can restore documents that are overwritten or deleted in error.
13.3 Provider stores the daily database backups and the point-in-time recovery data in Sydney, Australia, and encrypts backups at rest.
13.4 Provider tests restoration from backup at least once every 12 months.
13.5 Provider maintains documented procedures to recover the Cloud Service.
13.6 Provider plans the recovery of the Cloud Service to two objectives: a recovery time objective of 4 hours, which is the target time to restore the Cloud Service, and a recovery point objective of 5 minutes, which is the target maximum period of data loss. These are objectives, not guarantees.
13.7 Service availability commitments and service credits are set by the Service Level Agreement, not by this Addendum.
14. Deletion of Customer Content
14.1 Provider will delete Customer Content from the Cloud Service’s active systems within 60 days after termination of the Agreement, as Section 7.5(b) (Effect of termination) of the CSA and the DPA provide, unless a law requires Provider to keep it.
14.2 Copies of Customer Content held in backups, earlier document versions and archives are deleted under Provider’s retention schedule. Until they are deleted, this Addendum continues to apply to them.
14.3 Provider may keep records that Applicable Laws require it to keep. This Addendum continues to apply to those records while Provider keeps them.
15. Incidental sensitive data
15.1 Prohibited Data that Customer submits as Section 5.2(b) to (e) (Prohibited Data) of the CSA permits is Customer Content. Provider protects it under this Addendum in the same way as other Customer Content.
15.2 Section 4 applies to that data. Some Subprocessors process it outside Australia, including in the United States.
16. Customer responsibilities
16.1 This Addendum does not change Customer’s responsibilities under the CSA, including Section 2.3 (User accounts), Section 3.1 (Restrictions), Section 3.2 (Documentation and Use Limitations), and Section 5.2 (Prohibited Data).
17. Assurance
17.1 Once in any 12-month period, on Customer’s reasonable written request, Provider will give Customer:
(a) written answers to a reasonable information security questionnaire; and
(b) a copy of Provider’s most recent independent audit report on its security controls, if Provider holds one.
17.2 Information that Provider gives under this Section is Provider’s Confidential Information.
18. Changes to this Addendum
18.1 Provider may update this Addendum from time to time. An update will not materially reduce the protections in this Addendum during a Subscription Period that has already started.
18.2 The version of this Addendum in effect on the Order Date of an Order Form governs that Agreement until the start of its next Subscription Period.
18.3 Provider publishes this Addendum at https://alloovium.com/legal/security/. Provider will keep each earlier version available at a stable web address.