Legal and trust

Data processing terms

Last updated 22 July 2026

Scope

Where DIGIDENT LTD processes personal data contained in customer-entered notes or workflows solely on the customer's instructions, the customer is controller and DIGIDENT LTD is processor. For account, billing, security and product analytics data, DIGIDENT LTD acts as controller.

Instructions

We process customer content only to provide, secure, support and improve contracted functionality, and as required by law. The customer warrants that its instructions and uploaded content are lawful.

Confidentiality and security

Authorised personnel are subject to confidentiality obligations. Measures include access control, encryption in transit, password hashing, database separation, signed webhooks, logs and restoration procedures appropriate to the risk.

Sub-processors

Planned sub-processors are Cloudflare for hosting, Resend for email and GoCardless for payment services. GoCardless generally acts under its own payment privacy terms for payer data. Material processor changes will be notified where required.

Assistance

Taking account of the processing, we provide reasonable assistance with data-subject requests, security incidents, DPIAs and regulator enquiries. Customers should contact digidentAI@proton.me without delay.

Deletion and return

On termination, customer-entered content is deleted or returned within a reasonable operational period unless law requires retention. Backup and security-log copies expire under documented schedules.

Audit information

We make information reasonably necessary to demonstrate these commitments available, subject to confidentiality, security and proportionality. On-site audits require reasonable notice and are normally limited to once annually unless an incident or regulator requires otherwise.

Transfers

Restricted transfers use an applicable adequacy regulation or approved safeguards. The customer authorises the listed sub-processors on this basis.

Pre-launch completion

Final controller-processor roles, transfer mechanisms and supplier terms must be reconciled in the pre-launch data map before these terms become contractual.