Skip to content

← Home

Data processing addendum

A template addendum for IT-support firms that use Holdfast for their clients. It forms part of the terms.

Last updated 14 Nov 2026 · Version 2026-11-14

Draft — this text has not been reviewed by a lawyer yet.

Parties and scope

This addendum is between the customer (the firm, the controller) and [Company legal name] (the processor). It applies when [Company legal name] processes personal data for the firm's clients under the terms. It follows Article 28(3) of the EU and UK GDPR.

Template. The owner and the customer complete the bracketed items and sign it.

Details of the processing

Processing details
ItemDetail
Subject matterProviding the audit service to the customer.
DurationFor as long as the customer uses the service, until deletion.
Nature and purposeStoring, organising and showing client records and audit data; sending service emails; producing reports.
Types of dataClient names; contact names and emails; notes typed by the customer; the locked (encrypted) audit map and numeric summary; trusted-contact names and emails; activity log entries.
Data subjectsThe customer's clients, their staff and any trusted contacts they name.

Processor obligations (Art. 28(3))

[Company legal name] will:

  • process personal data only on the customer's documented instructions, which are these terms and the customer's use of the service, unless the law requires otherwise;
  • make sure people who process the data are bound by confidentiality;
  • take the security measures in the annex below;
  • use only the sub-processors on the sub-processors page, under written contracts with equivalent duties, and give notice of changes so the customer can object;
  • help the customer answer requests from people exercising their rights, using the export and delete tools in the app;
  • help the customer with security, breach notification, impact assessments and consulting authorities, taking into account the nature of the processing;
  • delete or return all personal data when the contract ends, at the customer's choice;
  • give the customer the information needed to show these duties are met, and allow audits as set out below.

Sub-processors

The customer gives general authorisation for the sub-processors listed on the sub-processors page. We will tell the customer by email at least 30 days before adding or replacing one. The customer may object on reasonable data protection grounds in that time. [Owner: confirm the notice period.]

Personal data breach

We will tell the customer without undue delay after becoming aware of a breach affecting the customer's personal data, with what we know about it and what we are doing. A server breach would expose locked data and numeric summaries, not readable account maps.

Deletion and return

The customer can export and delete its data at any time in the app. When the contract ends, we delete the customer's data when the organisation is deleted. Backups are overwritten within [number] days. [Owner: set backup retention.]

Audits

On reasonable written notice, no more than once a year unless there has been a breach, the customer may ask for information and, where that is not enough, for an audit by the customer or an auditor it appoints, under confidentiality. Costs: [to be agreed].

International transfers

Data is hosted in: [Hosting region]. Where data is transferred outside the UK or EEA to a country without an adequacy decision, the parties rely on:

  • EU Standard Contractual Clauses (Module 2 or 3 as it applies): [reference to be attached];
  • for the UK, the UK International Data Transfer Agreement or the UK Addendum to the EU clauses: [reference to be attached].

Annex: security measures

  • Audit maps encrypted in the browser (AES-GCM) with a key derived from the user's passphrase (PBKDF2, 600,000 rounds). The server cannot read them.
  • Passwords hashed with Argon2id; optional 2-step sign-in with single-use recovery codes.
  • httpOnly cookies, CSRF protection, rate limits, security headers.
  • Role-based access and separation between organisations.
  • Activity log kept 365 days; email log kept 30 days.
  • Session list with revoke; encrypted connections.
  • [Owner: add hosting, backup and monitoring measures.]

Signatures

Signature block
Customer (controller)[Company legal name] (processor)
Name[Name][Name]
Title[Title][Title]
Date[Date][Date]