BrandHealth

Data Processing Agreement

Last updated: October 2026

Template. This is a standard processor agreement for customers who need one under the GDPR, UK GDPR or similar laws. Have a lawyer review it before relying on it, and complete the bracketed items.

1. Parties and scope

This agreement is between the customer organisation (the Controller) and BrandHealth (the Processor) and applies to personal data the Processor handles for the Controller through BrandHealth: brand and keyword settings, collected public mentions (which may identify authors or journalists), media contacts the Controller adds, and the Controller's users. It forms part of the Terms of Service.

2. Instructions and purpose

The Processor processes personal data only on the Controller's documented instructions, which are the use of the service as configured by the Controller, to deliver monitoring, analysis, alerts, reports, outreach and press-release distribution. The Processor tells the Controller if an instruction appears to break data-protection law.

3. Confidentiality and security

People with access to the data are bound by confidentiality. The Processor applies appropriate measures, including: encrypted connections (HTTPS); salted password hashing; optional two-factor sign-in; encryption of stored provider keys; per-organisation data separation and role-based access; sign-in rate limiting and audit logs; daily backups with 14-day retention; and prompt security updates.

4. Subprocessors

The Controller gives general authorisation for the subprocessors listed at /subprocessors. The Processor imposes equivalent data-protection obligations on them, stays responsible for them, and tells the Controller of intended changes so it can object.

5. International transfers

Where personal data from the EEA, UK or Switzerland is transferred to a country without an adequacy decision, the parties rely on the Standard Contractual Clauses (and the UK addendum where needed), which are incorporated by reference with the Controller as exporter and the Processor as importer. [Lawyer to confirm modules and annexes.]

6. Helping the Controller

Taking the nature of processing into account, the Processor helps the Controller answer data-subject requests (access, rectification, erasure, restriction, portability, objection), carry out impact assessments and consult regulators. The Controller can export and delete its data from the service at any time.

7. Personal data breaches

The Processor tells the Controller without undue delay, and within 48 hours of becoming aware, of a breach affecting the Controller's personal data, with the information it has to help the Controller meet its 72-hour duty.

8. Audits

The Processor provides the information needed to show compliance and allows reasonable audits on notice, no more than once a year unless a breach has occurred.

9. End of service

When the Controller deletes its account the data is erased at once; backups are overwritten within 14 days. The Controller can export its data first. The Processor keeps nothing further unless the law requires it.

10. Controller responsibilities

The Controller is responsible for having a lawful basis for the keywords, brands and media contacts it adds and for contacting journalists in line with applicable law, including honouring opt-outs.

11. Contact

Privacy contact: [privacy contact].

← Back to Home