Skip to content

Security Measures

Effective date: 1 October 2026

Annex 3 to the Data Processing Agreement

1. Introduction

1.1 This document describes the technical and organisational measures that Courtive Limited (“Courtive”) implements to protect Customer Data and to keep the Platform confidential, available and reliable, as required by Article 32 of the UK GDPR. It forms Annex 3 to Courtive’s Data Processing Agreement (the “DPA”), and terms defined in the DPA have the same meanings here.

1.2 Courtive may update these measures, but will not reduce the overall level of protection they provide during the Term.

1.3 Further detail about these measures is available to Customers on request, subject to confidentiality.

2. Governance and certification

2.1 A member of Courtive’s senior management has overall responsibility for information security and data protection.

2.2 Courtive maintains written information security policies, approved by its directors, and registers of its devices, cloud services and access.

2.3 Courtive is certified under Cyber Essentials and is preparing for Cyber Essentials Plus.

3. Courtive access to systems and Customer Data

3.1 Access is granted on the principle of least privilege. Access to production systems is limited to named personnel who need it for their role.

3.2 Multi-factor authentication is required for all Courtive accounts, including email, the cloud hosting console, the code repository and administration tools.

3.3 Passwords, keys and other credentials for production systems are kept in a managed secrets store and are never stored in source code.

4. Authorised User access controls

4.1 Authentication:

  • (a) each Authorised User has a unique account;
  • (b) passwords are stored only in hashed form using bcrypt, a salted, industry-standard algorithm;
  • (c) multi-factor authentication is required for sign-in, either by the Platform or by the Customer’s single sign-on provider;
  • (d) single sign-on through the Customer’s OpenID Connect or SAML 2.0 identity provider is available on request; and
  • (e) accounts are locked after repeated failed log-in attempts.

4.2 Matter-based permissions:

  • (a) Authorised Users can access only the Matters to which they have been added;
  • (b) Client Users can see only their own Matter, and only the documents and questionnaires shared with them;
  • (c) Counsel Users can access only the Matters to which they have been invited; and
  • (d) the Customer’s administrators control who is added to each Matter and what they can do, and can remove access at any time.

4.3 Audit trail: the Platform records each download of documents generated in a Matter, and by whom, and records key document extraction actions. These records are available to the Customer on request.

5. Customer separation and AI safeguards

5.1 Separation of customers: each customer’s data is logically separated in Courtive’s databases and file storage. Every request to the Platform is checked against the Authorised User’s customer and Matter permissions. Automated tests check that users cannot access another customer’s or another Matter’s data.

5.2 No training: Customer Data is not used to train, fine-tune or otherwise improve any AI model, whether by Courtive or by its AI Providers. This is enforced through Courtive’s contracts with its AI Providers.

5.3 AI Provider controls: Courtive uses AI models only through business services governed by commercial terms, not consumer services. The Sub-Processors List sets out the retention, access and location details for each AI Provider. Only the Customer Data needed for a particular task is sent to an AI Provider.

5.4 Changes to the AI models or prompts used by the Platform are tested before release, including against a set of test documents that contain no real client data.

6. Encryption

6.1 In transit: connections between users, the Platform and Sub-processors are encrypted using TLS.

6.2 At rest: databases, file storage and backups are encrypted using AES-256, with keys managed by Google Cloud.

7. Infrastructure and network security

7.1 The Platform is hosted with Google Cloud in data centres in the EU that hold ISO/IEC 27001 and SOC 2 certification. Physical security of the data centres is provided by the hosting provider.

7.2 Databases are not reachable from the public internet. Public services require authentication, and internal services accept only authenticated service identities.

7.3 Development, testing and production environments are kept separate. Real Customer Data is never used in development or testing.

7.4 Systems are configured securely: default passwords are changed, unnecessary services are disabled.

8. Logging and monitoring

8.1 Application logs are kept for 30 days, and Google Cloud administrative audit logs for 400 days.

8.2 Logs are configured to exclude the content of Customer Data.

8.3 Automated alerts notify Courtive of interruptions to the availability of the Platform.

9. Backup and business continuity

9.1 Encrypted daily backups of the production database are kept for 7 days in the same Google Cloud region in the EU (Belgium), and point-in-time recovery is available for 7 days. Document storage keeps earlier versions of files.

9.2 Courtive’s recovery objectives are set out in the Service Level Agreement, if any.

10. Incident management

10.1 Courtive maintains a written incident response plan.

10.2 Courtive notifies Customers of Personal Data Breaches as set out in clause 12 of the DPA.

11. Supplier management

11.1 Before engaging a Sub-processor, Courtive assesses its data protection terms, processing locations and data retention practices.

12. Devices and remote working

12.1 Devices used by Courtive personnel are enrolled in Courtive’s device management, with screen lock, firewall and automatic update policies applied.

13. Retention and deletion

13.1 During the Term, the Customer controls how long Customer Data is kept. When the Agreement ends, Customer Data is deleted as set out in clause 14 of the DPA.

Data flow summary

StageWhat happensWhere

Upload

An Authorised User uploads documents or completes a questionnaire over an encrypted connection.

User’s browser over HTTPS to the Platform (Google Cloud, Belgium)

Storage

Customer Data is stored encrypted and linked to the relevant Matter.

Google Cloud, EU

Processing

The content needed for a task is sent over an encrypted connection to an AI Provider, and the result is returned to the Platform.

AI Providers, at the locations stated in the Sub-Processors List

Review

Draft Outputs are shown to Authorised Users with access to the Matter. Edits and exports are recorded.

The Platform

Export

An Authorised User exports documents in Word, PDF or Excel format.

User’s browser

Deletion

Customer Data is deleted as set out in clause 14 of the DPA.

All of the above locations