Data processing agreement
Last updated 6 November 2026
This agreement applies where a business (“the controller”) uses Analytics by DeltaBreen to measure its own sites and apps, and so has DeltaBreen Limited (the operator of Analytics by DeltaBreen), a company registered in Ireland with company number 826627, of Gorey, Co. Wexford, Ireland (“the processor”) process personal data on its behalf, as Article 28 of the GDPR requires. It forms part of the terms of service, and where the two differ on personal data, this agreement wins. For the controller's own account, sign-in and billing, the processor is a controller itself, as the privacy policy says.
1. What is processed
Subject and purpose: providing the analytics, heatmaps, session recordings and experiments the controller uses, as the terms describe. Nature: collecting, storing, aggregating and showing the data to the controller's people, assigning visitors to experiments, passing data where the controller directs, and deleting it. Data subjects: the visitors to the controller's sites and apps, the controller's own users it identifies, and the members of its workspace. Personal data: a visitor id made from a daily-rotating salted hash, or the controller's first-party id after consent, or its own user id for a logged-in user; the pages visited, referrers and campaign tags, the coarse location looked up from the IP address (country, region, city; the address itself is not stored), device, browser, operating system, screen size and language; events and their properties as the controller sends them; clicks and scrolls for heatmaps; and, where recording applies, a recording of the page with field inputs masked. The service is not designed for special categories of data. Duration: as long as the controller has a workspace; data is deleted after the retention period of the controller's plan.
2. Instructions
The processor processes this data only on the controller's documented instructions, which are the terms of service, this agreement and the controller's settings and use of the service, including as to transfers outside the EU, unless the law of the EU or of a member state requires otherwise; it then tells the controller first, unless that law forbids it. The processor tells the controller straight away if, in its view, an instruction breaks data protection law.
3. The controller's part
The controller is responsible for having a lawful basis for the processing, for any consent its use of consent mode, identification or recording needs, for telling its visitors about it, for its instructions being lawful, and for what it chooses to send to the service or elsewhere.
4. Confidentiality and security
Everyone the processor lets handle the data is bound by confidentiality. The processor keeps appropriate technical and organisational measures under Article 32 of the GDPR, and improves them over time without lowering the protection they give: data is held on servers in the EU and encrypted in transit; IP addresses are never stored; the salts behind visitor ids rotate daily and are kept out of backups; secrets and credentials are encrypted at rest; access is limited to those who need it, by role; recordings are played only on a separate domain to people allowed to see them, and each viewing is recorded; the databases are backed up nightly; and software is kept up to date and checked for known vulnerabilities. The security page describes the measures in more detail and promises nothing beyond this section.
5. Sub-processors
The controller gives general authorisation to the sub-processors listed in the privacy policy. The processor tells the workspace's owner by email at least 30 days before adding or replacing one. The controller may object on reasonable data protection grounds; if the two cannot resolve it, the controller may end the terms and is refunded the unused part of what it paid in advance. The processor binds each sub-processor by contract to data protection duties at least as protective as these, and remains responsible to the controller for them.
6. Transfers outside the EU
The processor keeps the data in the EU and transfers it outside the EU only to the sub-processors listed, with the safeguard the list names: an adequacy decision, the EU–US Data Privacy Framework or the European Commission's Standard Contractual Clauses.
7. Transfers the controller directs
Where the controller exports its data, reads it with an API key, sends it to a webhook or connects its own AI assistant, the processor acts on that instruction. The recipient is the controller's choice and not a sub-processor of the processor.
8. Helping the controller
The processor provides the means to export and erase the data of one identified user, and helps the controller, as far as the nature of the processing and the information it has allow, to answer data subject requests and to meet its duties on security, breach notification, impact assessments and prior consultation with a supervisory authority (Articles 32 to 36 of the GDPR).
9. Breaches
The processor tells the controller without undue delay after becoming aware of a personal data breach affecting the controller's data, with what is known of its nature, the data and people concerned, its likely consequences and the measures taken or proposed, and adds to it as more is known.
10. End of processing
The controller can export its data while it has its account. When the account is deleted, its workspaces' data is deleted thirty days later, and leaves the backups within a further thirty days, unless the law of the EU or of a member state requires it to be kept.
11. Audits
The processor makes available the information needed to show it meets this agreement, and allows and contributes to audits, including inspections, by the controller or an auditor it chooses who is bound by confidentiality. An audit is arranged on 30 days' notice, at the controller's cost, at most once a year unless a breach or a supervisory authority calls for another, and may first be answered with documents and answers to questions.
12. Liability and duration
Liability under this agreement follows the terms of service, except where the GDPR does not allow it to be limited. This agreement lasts for as long as the processor processes personal data for the controller.