Last updated 29 September 2026
In short
- We never sell your data, use it for advertising, or use it to train AI.
- Your company owns what it puts in Headwater. We only use it to provide Headwater to your company.
- Our staff can only see your workspace if an admin in your company gives them access. Your admins can see a record of every page they open.
- Workspaces are stored in Ireland, in the EU. This policy lists every company that handles your data for us.
- Our website sets no cookies. The app only sets the cookies it needs to work.
- You can ask to see, correct, export, or delete your data, and we reply within one month.
This summary is not legally binding. The full text below is.
1Who we are
Overcrate Ltd (“Headwater”, “we”, “us”, or “our”) makes Headwater, software that companies use to run their plan. We are registered in England and Wales under company number 16507860, our registered office is 128 City Road, London, EC1V 2NX .
This policy explains how we handle personal data when you use Headwater, visit useheadwater.com, join our waiting list, or contact us. It is written to meet the UK General Data Protection Regulation, the Data Protection Act 2018, and the Privacy and Electronic Communications Regulations (together, “UK data protection law”), and for people in the European Economic Area (EEA), the EU General Data Protection Regulation (“EU GDPR”).
For anything about privacy, email [email protected]. We reply within five working days. Our representative in the EU, for people in the EEA, is Overcrate Limited.
If this policy and one of the promises on our privacy page ever differ, whichever gives your data more protection applies.
2Your company’s data, and ours
We handle personal data in two different roles. Your rights depend on which role we are in.
Workspace content
When your company uses Headwater, it decides what goes into its workspace: its vision, pillars, initiatives, and climbs, check-ins, issues, decisions, documents, comments, huddle notes, 1:1 notes, Brook conversations, and the people it adds. We call all of this workspace content. For workspace content, your company is the controller and Headwater is its processor. We handle it only on your company’s instructions, under our data processing addendum, and only to run Headwater for your company.
Our own records
For account details, sign-in and security records, billing, our website, our waiting list, and messages you send us, Headwater is the controller. Most of this policy is about this data.
If you have a request about workspace content, such as seeing or deleting what your company holds about you, please ask your company first, because it decides what happens to it. If you ask us, we’ll pass your request to your company and help them answer it.
3What we never do
Whatever role we are in, we never:
- sell personal data or workspace content, or give it away in exchange for anything, in any form, including when it has been anonymised or combined with other data;
- use it for advertising, or share it with advertising networks, data brokers, or anyone who would use it to market to you;
- use workspace content to train, fine-tune, test, or improve any artificial intelligence or machine learning model, whether ours or anyone else’s, or allow our providers to do so;
- use workspace content to build profiles of people, compare companies with each other, or for any purpose of our own;
- make decisions about you based only on automated processing that have legal or similarly significant effects on you;
- open workspace content, except in the cases in section 7.
4What we collect
| Data | What it includes | Where it comes from |
|---|---|---|
| Account details | Your name, work email address, job title, company, teams, and who you report to. | You, or your company’s admin when they add you. |
| Sign-in records | When and how you sign in (email code, Google, or Microsoft), your device and browser, and your IP address. | Your device, through our sign-in provider. |
| Workspace content | Everything you and your colleagues put in Headwater. | You and your company. We are its processor. |
| Huddle transcripts | What is said in a team’s video call, and the names shown in it. | The call, only when a team invites Brook to it. |
| Technical records | IP address, browser, pages requested, errors, and timings. | Your device, automatically. |
| Billing details | Billing contact, company address, VAT number, and payment method. Our payment provider holds card details; we see only the card type, last four digits, and expiry date. | Your company. |
| Messages | What you send us by email or through support. | You. |
| Waiting list | Your work email address. | You, on our coming soon page. |
- Data
- Account details
- What it includes
- Your name, work email address, job title, company, teams, and who you report to.
- Where it comes from
- You, or your company’s admin when they add you.
- Data
- Sign-in records
- What it includes
- When and how you sign in (email code, Google, or Microsoft), your device and browser, and your IP address.
- Where it comes from
- Your device, through our sign-in provider.
- Data
- Workspace content
- What it includes
- Everything you and your colleagues put in Headwater.
- Where it comes from
- You and your company. We are its processor.
- Data
- Huddle transcripts
- What it includes
- What is said in a team’s video call, and the names shown in it.
- Where it comes from
- The call, only when a team invites Brook to it.
- Data
- Technical records
- What it includes
- IP address, browser, pages requested, errors, and timings.
- Where it comes from
- Your device, automatically.
- Data
- Billing details
- What it includes
- Billing contact, company address, VAT number, and payment method. Our payment provider holds card details; we see only the card type, last four digits, and expiry date.
- Where it comes from
- Your company.
- Data
- Messages
- What it includes
- What you send us by email or through support.
- Where it comes from
- You.
- Data
- Waiting list
- What it includes
- Your work email address.
- Where it comes from
- You, on our coming soon page.
Our website sets no cookies and uses no analytics. Our hosting provider keeps short-lived technical logs of requests to run the site and keep it secure.
Headwater is not designed for special category data, such as health, religion, or ethnicity, or for data about criminal offences. Please don’t put it in your workspace unless your company has a lawful basis for it and has told the people it concerns.
5How we use it, and why the law allows it
| What we do | Data we use | Lawful basis |
|---|---|---|
| Run Headwater for your company: your account, sign-in, workspace, notifications, and the emails you ask for | Account details, sign-in records, technical records | Our contract with your company, and our legitimate interest in giving its people the service it pays for |
| Store and handle workspace content | Workspace content | Your company’s instructions, as its processor |
| Keep Headwater secure, and prevent fraud and misuse | Sign-in records, technical records | Legitimate interests: protecting Headwater and every company on it |
| Bill your company and keep accounts | Billing details | Contract, and our legal duty to keep financial records |
| Answer your messages | Messages, account details | Legitimate interests: helping you |
| Tell your admins about changes to Headwater, our terms, or this policy | Account details | Contract, and legitimate interests |
| Send product news, only if you ask for it | Your email address | Consent, which you can withdraw at any time |
| Tell you when Headwater opens | Waiting list | Consent, which you can withdraw at any time |
| Improve Headwater, from technical records and what people tell us, never from workspace content | Technical records, messages | Legitimate interests: making Headwater better |
| Meet our legal duties, and make or defend legal claims | What the duty or claim needs | Legal obligation, and legitimate interests |
- What we do
- Run Headwater for your company: your account, sign-in, workspace, notifications, and the emails you ask for
- Data we use
- Account details, sign-in records, technical records
- Lawful basis
- Our contract with your company, and our legitimate interest in giving its people the service it pays for
- What we do
- Store and handle workspace content
- Data we use
- Workspace content
- Lawful basis
- Your company’s instructions, as its processor
- What we do
- Keep Headwater secure, and prevent fraud and misuse
- Data we use
- Sign-in records, technical records
- Lawful basis
- Legitimate interests: protecting Headwater and every company on it
- What we do
- Bill your company and keep accounts
- Data we use
- Billing details
- Lawful basis
- Contract, and our legal duty to keep financial records
- What we do
- Answer your messages
- Data we use
- Messages, account details
- Lawful basis
- Legitimate interests: helping you
- What we do
- Tell your admins about changes to Headwater, our terms, or this policy
- Data we use
- Account details
- Lawful basis
- Contract, and legitimate interests
- What we do
- Send product news, only if you ask for it
- Data we use
- Your email address
- Lawful basis
- Consent, which you can withdraw at any time
- What we do
- Tell you when Headwater opens
- Data we use
- Waiting list
- Lawful basis
- Consent, which you can withdraw at any time
- What we do
- Improve Headwater, from technical records and what people tell us, never from workspace content
- Data we use
- Technical records, messages
- Lawful basis
- Legitimate interests: making Headwater better
- What we do
- Meet our legal duties, and make or defend legal claims
- Data we use
- What the duty or claim needs
- Lawful basis
- Legal obligation, and legitimate interests
Where we rely on legitimate interests, we have weighed them against your rights and interests. Email [email protected] for a copy of that assessment.
We send service emails that Headwater needs to work, such as sign-in codes. Everything else, such as product news, is only sent if you ask for it, and every one of those emails has a link to stop them. We don’t track whether you open our emails or click their links.
6Brook and AI
Brook is the AI assistant in Headwater. It is an add-on, and it is off unless your company adds it. People use Brook to ask questions about their plan, to write huddle pre-reads, notes, and monthly reviews, to set climbs, and to check whether goals are SMART. Every feature that sends workspace content to an AI provider is part of Brook, so if your company doesn’t add Brook, none of its workspace content is sent to an AI provider.
Each time someone uses Brook, we send their request, with the parts of their company’s workspace needed to answer it, to one of the AI providers listed in section 9. The provider sends back an answer, which we show in Headwater and keep in your workspace. We only ever send data from the workspace of the company the person belongs to, and your data is never used in answers for anyone at another company.
Our contracts with our AI providers forbid them from using your data to train or improve their models. They may keep requests for up to 30 days to detect misuse, and then delete them. A provider may keep a request longer only if the law requires it or its safety systems flag the request as misuse, which for Anthropic can mean up to two years. Where a provider offers zero data retention and we have it in place, the provider keeps nothing once it has answered.
We keep a record of each AI request, with who asked, the feature, the model, and what it cost, for as long as your company uses Headwater. We keep the text of requests and answers for 30 days, to find and fix faults, and then delete it. Nobody at Headwater reads that text without your company’s permission.
Brook is never used to make decisions about people, and your workspace is only changed when someone asks Brook to change it. Answers from AI models can be wrong, so please check them before you rely on them.
Huddle notes
A team can add Brook to its video call to have the huddle notes written automatically. Our provider, Recall.ai, adds a participant called Brook to the call, which everyone in the call can see. Recall.ai turns what people say into text, and the huddle notes are written from that text. We don’t record audio or video, and we delete the transcript within 24 hours of the huddle ending. The notes are kept in your workspace. Your company is responsible for telling people in the call that notes are being taken.
Headwater in Claude
If you connect your own Claude account to Headwater, Claude can read the parts of the workspace that you can see, when you ask it to. Anthropic, the company that makes Claude, then handles that data under your agreement with Anthropic, not under this policy. If you use a personal Claude account, check your Claude privacy settings to see whether your chats can be used for training.
7When we look at workspace content
Nobody at Headwater opens your company’s workspace content, except:
- when your company asks for help. One of your company’s admins can let our support team into your workspace, for as long as the admin chooses. Every page our team opens is recorded in an access log that your admins can see;
- to keep Headwater secure. If we need to investigate or stop an attack, a security incident, or a serious breach of our terms, we look at only what we need to. We then tell your admins what we looked at and why, unless the law or the investigation stops us;
- when the law requires it, as set out in section 10.
Headwater stores, backs up, and searches workspace content automatically, and sends it to AI providers when someone uses Brook. Nobody at Headwater sees the content when this happens.
Only a few of our people can reach the systems that store workspace content. Each is bound by confidentiality, signs in with two-step verification, and has only the access their job needs.
9The companies that handle your data
| Company | What for | What it gets | Where |
|---|---|---|---|
| Convex | Database and servers. Stores every workspace. | Everything in a workspace, and account details | Ireland (EU) |
| Vercel | Runs the Headwater app and this website | Requests as they pass through, and technical logs | United States |
| Clerk | Sign-in | Name, email address, and sign-in records | United States |
| Resend | Sends Headwater’s emails | Name, email address, and the content of each email | United States |
| Stripe | Takes payments | Billing contact, company address, and card details, which we never see in full | United States |
| Anthropic | AI models for BrookOnly for companies that add Brook | Each request, with the parts of the workspace it needs | United States |
| OpenAI | AI models for BrookOnly for companies that add Brook | Each request, with the parts of the workspace it needs | United States |
| Groq | AI models for BrookOnly for companies that add Brook | Each request, with the parts of the workspace it needs | United States |
| TypeSafe | Checks whether a goal is SMART, for BrookOnly for companies that add Brook | The text of the goal | [location] |
| Recall.ai | Brings Brook into a team’s video call to write the huddle notesOnly when a team invites Brook to its call | What is said in the call, and the names shown in it | Germany (EU) |
- Company
- Convex
- What for
- Database and servers. Stores every workspace.
- What it gets
- Everything in a workspace, and account details
- Where
- Ireland (EU)
- Company
- Vercel
- What for
- Runs the Headwater app and this website
- What it gets
- Requests as they pass through, and technical logs
- Where
- United States
- Company
- Clerk
- What for
- Sign-in
- What it gets
- Name, email address, and sign-in records
- Where
- United States
- Company
- Resend
- What for
- Sends Headwater’s emails
- What it gets
- Name, email address, and the content of each email
- Where
- United States
- Company
- Stripe
- What for
- Takes payments
- What it gets
- Billing contact, company address, and card details, which we never see in full
- Where
- United States
- Company
- Anthropic
- What for
- AI models for BrookOnly for companies that add Brook
- What it gets
- Each request, with the parts of the workspace it needs
- Where
- United States
- Company
- OpenAI
- What for
- AI models for BrookOnly for companies that add Brook
- What it gets
- Each request, with the parts of the workspace it needs
- Where
- United States
- Company
- Groq
- What for
- AI models for BrookOnly for companies that add Brook
- What it gets
- Each request, with the parts of the workspace it needs
- Where
- United States
- Company
- TypeSafe
- What for
- Checks whether a goal is SMART, for BrookOnly for companies that add Brook
- What it gets
- The text of the goal
- 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
- What it gets
- What is said in the call, and the names shown in it
- Where
- Germany (EU)
We tell your company’s admins at least 30 days before we add or replace a company that handles workspace content, and your company can object, as set out in our data processing addendum.
11Data outside the UK and EU
Workspaces are stored in Ireland, in the EU. UK law recognises the EU as protecting personal data to the UK’s standard.
Some of our providers are in the United States, as section 9 shows. When they handle personal data from the UK or the EEA, we protect it in one of these ways:
- 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, with the UK’s International Data Transfer Addendum for data from the UK, together with extra protections such as encryption where our assessment of the transfer shows they are needed.
Email [email protected] for a copy of the safeguards that apply to a provider.
12How long we keep it
| Data | How long |
|---|---|
| Workspace content | While your company’s subscription runs. When it ends, your admins have 30 days to export it. We then delete it, and it’s gone from our backups within 90 days. |
| A workspace your company deletes | Deleted from our live systems within 30 days, and from our backups within 90 days. |
| Things deleted inside a workspace | Removed from the workspace straight away, and from our backups within 90 days. Your workspace’s change history keeps a record of edits until the workspace is deleted. |
| Account details | While you have access to a company in Headwater. If you lose access to every company, we delete your account within 90 days. |
| Sign-in and security records | Up to 12 months. |
| Technical records | Up to 30 days. |
| Records of AI requests | Who asked, the feature, the model, and the cost: while your company uses Headwater. The text of requests and answers: 30 days. |
| Copies kept by AI providers | Up to 30 days, or longer only as set out in section 6.3. |
| Huddle transcripts | Deleted within 24 hours of the huddle ending. |
| Billing records | Six years after the end of the financial year they relate to, because UK tax law requires it. |
| Messages to us | Up to two years after the conversation ends. |
| Waiting list | Until we’ve told you Headwater is open, then deleted within six months, or sooner if you ask. |
- Data
- Workspace content
- How long
- While your company’s subscription runs. When it ends, your admins have 30 days to export it. We then delete it, and it’s gone from our backups within 90 days.
- Data
- A workspace your company deletes
- How long
- Deleted from our live systems within 30 days, and from our backups within 90 days.
- Data
- Things deleted inside a workspace
- How long
- Removed from the workspace straight away, and from our backups within 90 days. Your workspace’s change history keeps a record of edits until the workspace is deleted.
- Data
- Account details
- How long
- While you have access to a company in Headwater. If you lose access to every company, we delete your account within 90 days.
- Data
- Sign-in and security records
- How long
- Up to 12 months.
- Data
- Technical records
- How long
- Up to 30 days.
- Data
- Records of AI requests
- How long
- Who asked, the feature, the model, and the cost: while your company uses Headwater. The text of requests and answers: 30 days.
- Data
- Copies kept by AI providers
- How long
- Up to 30 days, or longer only as set out in section 6.3.
- Data
- Huddle transcripts
- How long
- Deleted within 24 hours of the huddle ending.
- Data
- Billing records
- How long
- Six years after the end of the financial year they relate to, because UK tax law requires it.
- Data
- Messages to us
- How long
- Up to two years after the conversation ends.
- Data
- Waiting list
- How long
- Until we’ve told you Headwater is open, then deleted within six months, or sooner if you ask.
We may keep data longer only where the law requires it, and then we keep it secure and use it for nothing else.
13How we protect it
- Data is encrypted as it travels, with TLS 1.2 or higher, and where it is stored, with AES-256.
- Workspaces are stored in data centres in Ireland run by Amazon Web Services, which are independently certified to ISO 27001.
- Every record belongs to one company, and every request is checked against the person’s access, so one company can never see another company’s data.
- People sign in with a one-time code sent to their email, or with Google or Microsoft. Headwater has no passwords, so there are none to steal.
- Our own people use two-step verification on every system that holds your data, and have only the access their job needs.
- We back up workspaces regularly, keep backups encrypted, and delete them after 90 days.
If a breach of security affects personal data we hold for your company, we’ll tell your admins within 48 hours of confirming it, with what happened, what it affects, and what we are doing about it. Where the law requires, we’ll report it to the ICO within 72 hours.
If you find a security problem in Headwater, please email [email protected]. We won’t take legal action against anyone who reports a problem to us in good faith and gives us time to fix it.
14Your rights
Under UK data protection law and the EU GDPR, you have the right to:
- get a copy of the personal data we hold about you, and know how we use it;
- have data corrected if it is wrong or incomplete;
- have data deleted when we no longer need it, or when you withdraw your consent;
- ask us to limit how we use your data while a question about it is settled;
- get your data in a format other software can read, or have it sent to another company;
- object to how we use your data where we rely on legitimate interests, and to any direct marketing at any time;
- withdraw your consent at any time, where we rely on it;
- not be subject to decisions made only by automated processing that have legal or similarly significant effects.
To use any of these rights, email [email protected]. It’s free. We may ask you to confirm who you are, and we reply within one month. If a request is complex, we may take up to two more months, and we’ll tell you within the first month if we need to. For workspace content, see section 2.
Complaints
If you are unhappy with how we have handled your data, please tell us first at [email protected]. We’ll confirm we have your complaint within 30 days, look into it without delay, keep you told of progress, and tell you what we found and what we have done.
You can also complain to the Information Commissioner’s Office at ico.org.uk or on 0303 123 1113. In the EEA, you can complain to the data protection authority where you live or work.
If you live in the United States
Some US states, such as California, give you rights to know about, correct, and delete personal information, and to opt out of its sale or sharing. We don’t sell or share personal information as those laws define it, or use sensitive personal information to infer anything about you. Email [email protected] to use your rights. We won’t treat you differently for using them.
16Children
Headwater is for businesses and other organisations, and is not for anyone under 18. We don’t knowingly collect personal data from children. If you think we have, email [email protected] and we’ll delete it.
17Changes to this policy
When we change this policy, we’ll post the new version here with a new date. For a significant change, we’ll email every company’s admins at least 30 days before it takes effect.
A change that gives your data less protection will never apply to data we already hold without your company’s agreement. Our terms of service say the same.
18Contact
Privacy: [email protected]
Security problems: [email protected]
Post: Overcrate Ltd, 128 City Road, London, EC1V 2NX