Privacy
How we handle your data
Last updated 29 August 2026. This covers the form on this page. What Briefbee does with a client's data under contract is in the contract, not here.
What we collect
If you ask for a call
Your name, your work email, the company and role you typed, the plan you picked if you picked one, the date and time, the exact sentence you agreed to, which part of the page you sent it from, and — when the link you arrived on says so — how the visit reached us, as a word like google/cpc. That is the whole record.
Nothing beyond what you typed. We don't keep your IP address against the signup and we don't fingerprint your browser — the form talks to the database directly, with no server of ours in between to observe either. The note about how you arrived is the name of a channel, never the identifier Google puts on an individual ad click; we drop that on arrival and it is not stored anywhere.
If you ask for a test edition
The form at /start keeps, beyond your name, email, organisation and role, what you wrote about your work and what you want to read: the four texts, the weights per theme, the sources you named and the delivery time. We use it for one thing: to build your test edition and talk to you about it. None of it is published or shared beyond the processors listed below, and the same retention applies.
Analytics
This site loads Google Analytics, which is separate from the list and does not know your email address. It tells us how many people reach the page and which sections they read, so we can tell whether the description of the product is landing. To do that it sets cookies in your browser and sends your IP address and your page views to Google, who may process them outside your country.
You can stop it with any content blocker, your browser's Global Privacy Control setting, or Google's opt-out add-on. Blocking it has no effect on the form on this page, which is a direct call to our own database and does not go through Google.
Joining the list is also counted there as an event, and that count is passed to Google Ads so we can tell which advertisements bring people who actually sign up. What travels is the fact that a signup happened in this browser. Your email address is not part of it and never reaches Google at all.
Why, and on what basis
To write back with times, to hold the onboarding call, and to prepare the demonstration briefing it shows you. The lawful basis is your consent (GDPR Art 6(1)(a)), given by ticking the box that read:
I'd like Briefbee to get in touch to set up this call. My details are used for that and to prepare the demonstration briefing.
We store that sentence alongside your details so there is a record of what you actually agreed to, not merely that you agreed. We will not use any of it for anything else, and we will not sell it, rent it or pass it to anyone beyond the processors below.
Who else touches it
| Processor | What they do |
|---|---|
| Supabase | Hosts the database these details are stored in. |
| Resend | Delivers our reply with the times. |
| Railway | Serves this page and runs the process that sends those emails. |
| Google Analytics | Measures visits to this page. Never receives your details. |
| Google Ads | Counts call requests that arrived from an advertisement. Never receives your details. |
No Briefbee product feature runs against this data. In particular, nothing on this list is sent to any AI model.
How long we keep it
For as long as the conversation is open, and for twelve months after it if it doesn't become a contract — the span in which a proposal still tends to come back. If it does become a contract, the contract is what governs. If you ask to be taken off, we keep your address marked as unsubscribed rather than deleting the row outright — that is what stops it being re-added — and delete the rest at once.
Your rights
- Ask for a copy of what we hold about you — which is what you typed into the form and the date you typed it.
- Correct it, if it's wrong.
- Have it deleted.
- Object to the processing, or ask us to restrict it.
- Withdraw your consent at any time — the link is in the email, and it takes one click.
- Complain to your data protection authority.
The fastest route to any of these is to reply to the email you received. Coming off the list needs no reply at all: the link goes to a page that does it on arrival.
Changes
If we change what we do with these details, we'll change this page and ask again where consent is what we're relying on. We won't quietly widen the use of something you agreed to on narrower terms.