Last updated 29 September 2026
In short
- Your company decides what happens to the personal data in its workspace. We follow its instructions and nothing else.
- We never sell it, use it for advertising, or use it to train AI, and nor may any company we work with.
- If there is a security breach that affects it, we tell you within 48 hours of becoming aware of it.
- We tell you 30 days before we add a company that handles it, and you can object.
- When you leave, you can export all of it, and then we delete it.
- This addendum is part of our terms of service, so it applies to every company from the day it signs up.
This summary is not legally binding. The full text below is.
1What this addendum covers
This data processing addendum (the “Addendum”) forms part of our terms of service (the “Terms”). It applies whenever Headwater processes personal data in Customer Data (“Customer Personal Data”) for the Customer. It is written to meet Article 28 of the UK General Data Protection Regulation and of the EU General Data Protection Regulation.
The Customer is the controller of Customer Personal Data, and Headwater is its processor. Where the Customer is itself a processor for another controller, such as a company in its group, Headwater is its subprocessor, and the Customer confirms that its instructions are authorised by that controller.
Words defined in the Terms have the same meanings here. “Controller”, “processor”, “data subject”, “personal data”, “personal data breach”, and “processing” have the meanings given in Data Protection Law.
The details of the processing are in Annex 1.
2Your instructions
We process Customer Personal Data only on the Customer’s documented instructions. The Terms, this Addendum, what Admins set and do in Headwater, and anything else the parties agree in writing are the Customer’s instructions.
If the law requires us to process Customer Personal Data in another way, we will tell the Customer before we do, unless the law forbids it.
We will tell the Customer straight away if we think an instruction breaks Data Protection Law.
We will not sell or share Customer Personal Data, or use it for advertising. We will not keep, use, or disclose it for any purpose other than providing the Service to the Customer, or outside our direct business relationship with the Customer, and we will not combine it with personal data from any other source except as the Service needs. Where US state privacy laws apply, we act as the Customer’s service provider or processor under them.
We will not use Customer Personal Data, or allow anyone else to use it, to train, fine-tune, test, or improve any artificial intelligence or machine learning model.
3Our people
Everyone we allow to process Customer Personal Data is bound by a duty of confidentiality, is trained in data protection, and has only the access their job needs.
Our people open Customer Personal Data only in the cases set out in clause 6.4 of the Terms: with an Admin’s permission, which is logged where Admins can see it; to keep the Service secure; or when the law requires it.
4Security
We protect Customer Personal Data with the technical and organisational measures in Annex 2, which are appropriate to the risks of the processing. We review them at least once a year.
We may improve the measures over time, but we will not reduce the overall protection they give during the Terms.
5Subprocessors
The Customer authorises us to use the subprocessors listed in Annex 3 and in our privacy policy.
Each subprocessor is bound by a written contract that protects Customer Personal Data at least as well as this Addendum, including a ban on using it to train AI models, a limit on how long it is kept, and a duty to delete it.
We will email the Customer’s Admins at least 30 days before we add or replace a subprocessor, and update the list. The new subprocessor will not process Customer Personal Data until the 30 days have passed. If we must replace a subprocessor urgently to keep the Service running, we will tell the Customer as soon as we can, and the Customer’s rights in clause 5.4 still apply.
The Customer may object to a new subprocessor on reasonable data protection grounds within 30 days of our notice. We will then work with the Customer in good faith to resolve it. If we can’t, the Customer may end the Terms and we will refund the Fees paid for any time after they end.
We remain fully responsible to the Customer for everything our subprocessors do.
6Transfers outside the UK and EEA
We store Customer Personal Data in the European Economic Area, in Ireland.
We transfer Customer Personal Data outside the UK and the European Economic Area only to subprocessors listed in Annex 3, and only with a transfer mechanism that Data Protection Law recognises. These are adequacy regulations or decisions, including the UK Extension to the EU-US Data Privacy Framework and the EU-US Data Privacy Framework for providers certified under them, or the EU Standard Contractual Clauses (module three, processor to processor) with the UK International Data Transfer Addendum for data from the UK. We assess each transfer, and add protections such as encryption where the assessment shows they are needed.
Where the law requires a transfer mechanism for Customer Personal Data that the Customer sends to us, the EU Standard Contractual Clauses (module two or three, as fits) are incorporated into this Addendum, with the UK International Data Transfer Addendum where it applies, unless an adequacy decision or regulation covers the transfer. The optional docking clause applies, the supervisory authority is the one that has jurisdiction over the Customer, and the clauses are governed by the law of Ireland for EU transfers.
7Helping the Customer
If a data subject asks us to act on their rights about Customer Personal Data, we will pass the request to the Customer within five Working Days, and not answer it ourselves except to tell them we have done so. Headwater gives Admins tools to find, correct, export, and delete data, and we will give the Customer any other reasonable help it needs to answer.
We will give the Customer reasonable help with its duties under Data Protection Law, including security, breach notifications, data protection impact assessments, and consultations with a regulator, taking into account what we know about the processing. This help is free unless it is excessive.
8Personal data breaches
We will tell the Customer without undue delay, and within 48 hours of becoming aware, of any personal data breach that affects Customer Personal Data.
We will tell the Customer what happened, what kinds of data and roughly how many people and records are affected, the likely consequences, what we have done and will do about it, and who to contact. If we don’t know all of this at first, we will tell the Customer what we know and add to it as we find out more.
We will take reasonable steps straight away to contain the breach, investigate it, and reduce its effects, and keep the Customer told throughout.
We will not tell data subjects or regulators about a breach of Customer Personal Data without the Customer’s agreement, unless the law requires us to.
Telling the Customer about a breach is not an admission of fault by us.
9Audits
We will give the Customer the information it reasonably needs to show that we meet this Addendum, including our security documentation, summaries of any independent audits, and answers to one security questionnaire a year.
If that information isn’t enough, the Customer, or an independent auditor bound by confidentiality, may audit our compliance once a year, or more often after a breach or where a regulator requires it. The Customer must give us 30 days’ notice, keep to Working Days, and avoid disrupting the Service or seeing other customers’ data. Each party pays its own costs.
10Returning and deleting data
Admins can export Customer Personal Data at any time during the Terms, and for 30 days after they end, in common formats that other software can read.
After that, we delete all Customer Personal Data from our live systems within 30 days, and from our backups within a further 90 days, and confirm it in writing if the Customer asks. We keep it longer only where the law requires us to, and then we protect it and use it for nothing else.
12Liability, precedence, and how long this lasts
Liability under this Addendum is subject to clause 16 of the Terms, including the higher limit in clause 16.5.
If this Addendum conflicts with the Terms about personal data, this Addendum applies. If it conflicts with the Standard Contractual Clauses, they apply.
This Addendum lasts for as long as we process any Customer Personal Data.
Questions about this Addendum go to [email protected].
13Annex 1: Details of the processing
| Details | |
|---|---|
| Subject matter | Providing the Service to the Customer under the Terms. |
| Duration | The length of the Terms, plus the time needed to delete data under clause 10. |
| Nature and purpose | Storing, organising, showing, searching, sending, backing up, and deleting Customer Personal Data so that the Customer and its Users can run their plan in Headwater. Sending notifications and emails. If the Customer adds Brook, sending requests to AI Providers to produce outputs, and turning what is said in a team’s video call into text to write huddle notes, when the team invites Brook to the call. |
| Data subjects | The Customer’s employees, contractors, and other people it adds to Headwater; people named in Customer Data; and people in video calls that a team invites Brook to. |
| Types of personal data | Names, work email addresses, job titles, teams, and reporting lines. Content written by or about people, such as climbs, check-ins, issues, decisions, comments, documents, and 1:1 notes. Brook conversations. Huddle transcripts, with speakers’ names. Sign-in and technical records. |
| Special category data | None is needed for the Service. The Customer decides whether any is put into it, and is responsible for having a lawful basis. |
| How often | Continuously, while the Customer uses the Service. |
| How long it is kept | As set out in the retention table in our privacy policy, and deleted at the end as set out in clause 10. |
- Subject matter
- Details
- Providing the Service to the Customer under the Terms.
- Duration
- Details
- The length of the Terms, plus the time needed to delete data under clause 10.
- Nature and purpose
- Details
- Storing, organising, showing, searching, sending, backing up, and deleting Customer Personal Data so that the Customer and its Users can run their plan in Headwater. Sending notifications and emails. If the Customer adds Brook, sending requests to AI Providers to produce outputs, and turning what is said in a team’s video call into text to write huddle notes, when the team invites Brook to the call.
- Data subjects
- Details
- The Customer’s employees, contractors, and other people it adds to Headwater; people named in Customer Data; and people in video calls that a team invites Brook to.
- Types of personal data
- Details
- Names, work email addresses, job titles, teams, and reporting lines. Content written by or about people, such as climbs, check-ins, issues, decisions, comments, documents, and 1:1 notes. Brook conversations. Huddle transcripts, with speakers’ names. Sign-in and technical records.
- Special category data
- Details
- None is needed for the Service. The Customer decides whether any is put into it, and is responsible for having a lawful basis.
- How often
- Details
- Continuously, while the Customer uses the Service.
- How long it is kept
- Details
- As set out in the retention table in our privacy policy, and deleted at the end as set out in clause 10.
14Annex 2: Security measures
| Area | What we do |
|---|---|
| Encryption | TLS 1.2 or higher for data in transit. AES-256 for data at rest, including backups. |
| Hosting | Customer Data is stored in data centres in Ireland run by Amazon Web Services, which are certified to ISO 27001. |
| Keeping customers apart | Every record belongs to one company, and our servers check every request against the person’s access to that company. |
| Signing in | Passwordless sign-in with one-time email codes, or Google or Microsoft. Only verified email addresses can sign in. Removing a person’s access takes effect straight away. |
| Our people’s access | Named accounts only, two-step verification on every system that holds Customer Data, access limited to what each job needs and reviewed every quarter, and removed the day someone leaves. Support access to a workspace only with an Admin’s permission, and logged. |
| Monitoring | Logs of access to our systems, and alerts for unusual activity. |
| Backups | Regular encrypted backups, kept for 90 days, with restores tested. |
| Building the software | Every change is reviewed before release. Dependencies are kept up to date. Secrets are kept out of code. Development and testing never use Customer Data. |
| Incidents | A written plan for responding to incidents, and notice to the Customer within 48 hours of confirming a breach. |
| Suppliers | Each subprocessor is checked before we use it and bound by a written data protection contract. |
| Deletion | Customer Data deleted at the end of the Terms, from live systems and then from backups, as clause 10 sets out. |
- Area
- Encryption
- What we do
- TLS 1.2 or higher for data in transit. AES-256 for data at rest, including backups.
- Area
- Hosting
- What we do
- Customer Data is stored in data centres in Ireland run by Amazon Web Services, which are certified to ISO 27001.
- Area
- Keeping customers apart
- What we do
- Every record belongs to one company, and our servers check every request against the person’s access to that company.
- Area
- Signing in
- What we do
- Passwordless sign-in with one-time email codes, or Google or Microsoft. Only verified email addresses can sign in. Removing a person’s access takes effect straight away.
- Area
- Our people’s access
- What we do
- Named accounts only, two-step verification on every system that holds Customer Data, access limited to what each job needs and reviewed every quarter, and removed the day someone leaves. Support access to a workspace only with an Admin’s permission, and logged.
- Area
- Monitoring
- What we do
- Logs of access to our systems, and alerts for unusual activity.
- Area
- Backups
- What we do
- Regular encrypted backups, kept for 90 days, with restores tested.
- Area
- Building the software
- What we do
- Every change is reviewed before release. Dependencies are kept up to date. Secrets are kept out of code. Development and testing never use Customer Data.
- Area
- Incidents
- What we do
- A written plan for responding to incidents, and notice to the Customer within 48 hours of confirming a breach.
- Area
- Suppliers
- What we do
- Each subprocessor is checked before we use it and bound by a written data protection contract.
- Area
- Deletion
- What we do
- Customer Data deleted at the end of the Terms, from live systems and then from backups, as clause 10 sets out.
15Annex 3: Subprocessors
| Company | What for | Where |
|---|---|---|
| Convex | Database and servers. Stores every workspace. | Ireland (EU) |
| Vercel | Runs the Headwater app and this website | United States |
| Clerk | Sign-in | United States |
| Resend | Sends Headwater’s emails | United States |
| Stripe | Takes payments | United States |
| Anthropic | AI models for BrookOnly for companies that add Brook | United States |
| OpenAI | AI models for BrookOnly for companies that add Brook | United States |
| Groq | AI models for BrookOnly for companies that add Brook | United States |
| TypeSafe | Checks whether a goal is SMART, for BrookOnly for companies that add Brook | [location] |
| Recall.ai | Brings Brook into a team’s video call to write the huddle notesOnly when a team invites Brook to its call | Germany (EU) |
- Company
- Convex
- What for
- Database and servers. Stores every workspace.
- Where
- Ireland (EU)
- Company
- Vercel
- What for
- Runs the Headwater app and this website
- Where
- United States
- Company
- Clerk
- What for
- Sign-in
- Where
- United States
- Company
- Resend
- What for
- Sends Headwater’s emails
- Where
- United States
- Company
- Stripe
- What for
- Takes payments
- Where
- United States
- Company
- Anthropic
- What for
- AI models for BrookOnly for companies that add Brook
- Where
- United States
- Company
- OpenAI
- What for
- AI models for BrookOnly for companies that add Brook
- Where
- United States
- Company
- Groq
- What for
- AI models for BrookOnly for companies that add Brook
- Where
- United States
- Company
- TypeSafe
- What for
- Checks whether a goal is SMART, for BrookOnly for companies that add Brook
- Where
- [location]
- Company
- Recall.ai
- What for
- Brings Brook into a team’s video call to write the huddle notesOnly when a team invites Brook to its call
- Where
- Germany (EU)