Skip to content

Controls (22)

Security controls at Courtive, taken from our published Security Measures.

Documents

Data protection (6)

  • Encryption at rest

    Documents are stored in Google Cloud Storage and matter records in Cloud SQL for PostgreSQL. Google encrypts both with AES-256 (Cloud Storage uses AES-256-GCM), including database tables, temporary files and backups. Each chunk of data has its own key, wrapped by keys held in Google’s central keystore and rotated regularly, using a FIPS 140-2 validated module.

  • Encryption in transit

    Connections to Courtive use HTTPS. The database accepts only encrypted connections and has no public IP address.

  • Data stays in the EU

    The application, documents, database and backups are hosted on Google Cloud in Belgium (europe-west1). AI processing runs on AWS Bedrock in EU regions, with data retention set to none.

  • No training on client data

    Client documents are not used to train, fine-tune or improve any AI model, by Courtive or its AI providers.

  • Backups

    The production database is backed up daily, with backups and point-in-time recovery kept for 7 days in the same EU region. Document storage keeps earlier versions of files.

  • Return and deletion

    When an agreement ends, client data is returned and deleted as set out in clause 14 of the DPA.

Access control (5)

  • Sign-in

    Each user has their own account. Passwords are stored only as bcrypt hashes, and accounts lock after repeated failed log-in attempts.

  • Multi-factor authentication

    Multi-factor authentication is required to sign in, either by Courtive or by the firm’s own single sign-on provider. Single sign-on through OpenID Connect or SAML 2.0 is available on request.

  • Matter-based permissions

    Users see only the matters they have been added to. Clients see only their own matter, and only the documents and questionnaires shared with them.

  • Customer separation

    Each firm’s data is logically separated, every request is checked against the user’s firm and matter, and automated tests check that users cannot reach another firm’s or matter’s data.

  • Download history

    The platform records each download of documents generated in a matter, and by whom.

Infrastructure (5)

  • Private database

    The database is reachable only on a private network, never from the public internet.

  • Locked-down storage

    Storage buckets block public access and use uniform, identity-based access control.

  • Authenticated services

    Public services require sign-in, and internal services accept only authenticated service identities.

  • Separate environments

    Development, staging and production run in separate environments. Real client data is never used for development or testing.

  • Logging

    Application logs are kept for 30 days and Google Cloud administrative audit logs for 400 days. Logs exclude the content of client data, and automated alerts report interruptions to availability.

Company (6)

  • Policies

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

  • Cyber Essentials

    Courtive is certified under Cyber Essentials, covering the whole organisation, and is preparing for Cyber Essentials Plus.

  • Staff access

    Access to production is limited to named people who need it. Every Courtive account requires multi-factor authentication, and production credentials are kept in a managed secrets store, never in source code.

  • Devices

    Courtive devices are enrolled in device management, with screen lock, firewall and automatic updates applied.

  • Incident response

    Courtive has a written incident response plan and notifies customers of personal data breaches as set out in clause 12 of the DPA.

  • Sub-processors

    Courtive assesses each sub-processor’s data protection terms, locations and retention before using it, and gives customers 30 days’ notice of a new one.