Privacy
Your data, plainly.
What we collect, why, how long we keep it, who helps us run the service, and how to use your rights. Version 2026-09-22, last updated 22 September 2026.
Who we are
Some Like It Bot Hub is a marketing operations service run by its operator ("we", "us"). For the beta request form, the invite and signup, your account and our own records, we are the controller under the UK GDPR, the Data Protection Act 2018 and, for people in the European Economic Area, the EU GDPR.
Write to [email protected] about anything in this notice. A person reads that inbox.
When a business uses the hub to run its marketing, the data it puts in about its own customers and contacts belongs to that business. For that data the business is the controller and we are its processor, acting only on its instructions under a data processing agreement. If you are one of their contacts, ask that business first; we will help them answer.
What we collect
When you ask to join the beta
- Your name, work email, company, website (optional) and what you want to use the hub for.
- Proof of your agreement: the version of this notice you saw, the time you ticked the box, and a one-way hash of your IP address. We do not store the IP address itself with your request.
- Whether and when you confirmed your email, and our decision on your request.
- A bot check. Cloudflare Turnstile looks at signals from your browser and your IP address to tell people from bots, and tells us only whether the check passed.
When you sign up from an invite
- Your company name, the workspace address you choose and your name.
- Payment is handled by Stripe on its own page. We never see or store your card details. We keep the Stripe customer and subscription references and the subscription status.
When you use the hub
- Your account: name, email, role, sign-in records and, if you turn it on, your two-step sign-in secret.
- An audit log of changes you make, with the IP address and browser used.
- The content you create, such as campaigns, posts, listings and replies.
- Prompts and results when you use the AI features.
On every visit
- Server and security logs: IP address, browser, the page asked for and the time.
Why we use it, and our lawful basis
| Purpose | Lawful basis |
|---|---|
| Replying to your beta request, confirming your email, and contacting you about the beta | Your consent (the box on the form). You can withdraw it at any time. |
| Checking requests for bots and abuse, and keeping proof of your consent | Our legitimate interest in keeping the service safe and being able to show we asked properly |
| Setting up your workspace, taking payment and providing the service | Performing our contract with you, or taking steps you asked for before it |
| Security logs, audit logs and fraud prevention | Our legitimate interest in protecting the service and its users |
| Invoices and tax records | Legal obligation |
We do not sell your data, we do not use it for advertising, and nobody is approved or refused by an automated decision: a person reads every beta request.
How long we keep it
| Data | Kept for |
|---|---|
| A beta request you did not confirm | 7 days, then deleted |
| A declined beta request | 30 days after the decision, then deleted |
| A confirmed request still waiting | Until the beta ends or 12 months without any decision, then deleted |
| An invite link nobody used | Deleted 30 days after it expired (links expire after 14 days) |
| A request that became a workspace | The personal details on the request are removed 30 days after the workspace is created; only a count remains |
| Your account and workspace | While you are a customer, then 30 days to export before deletion |
| Audit logs | 24 months |
| Server and security logs | 30 days |
| AI request logs | 30 days |
| Invoices and payment records | As long as tax law requires (in the UK, 6 years) |
| Encrypted backups | 30 days, so deleted data leaves the backups within 30 days |
Who helps us run the service
These processors handle personal data for us under written contracts. None may use it for their own purposes, except where noted.
| Processor | What for | Where |
|---|---|---|
| Hetzner Online GmbH | The server and storage that hold the service and its data | Helsinki, Finland (EU) |
| Cloudflare, Inc. | DNS, secure connections, protection from attacks, and the Turnstile bot check | Global network; requests are handled at the location nearest you |
| Stripe | Payments and subscriptions. Stripe is also a controller for the fraud checks it runs itself | EU and United States |
| GreenGeeks | The mail server that sends our emails, such as the beta confirmation | United States |
| Anthropic, PBC | The language model behind the AI features, only when you use them. We never send your contacts' personal details to it. A workspace can choose EU-only processing, which runs the AI features on our own server in Finland instead. | United States |
International transfers
Your data is stored in Finland. The UK treats the EEA as adequate, so data can move between the UK and Finland freely. Where a processor above handles data outside the UK or EEA, we rely on the European Commission's standard contractual clauses with the UK addendum, or on the EU-US Data Privacy Framework and its UK extension where the provider is certified. Write to [email protected] for a copy of the safeguards.
Your rights
You have the right to:
- get a copy of the personal data we hold about you (access);
- have it corrected if it is wrong (rectification);
- have it deleted (erasure);
- have us limit what we do with it (restriction);
- object to processing based on our legitimate interests;
- get the data you gave us in a machine-readable file (portability);
- withdraw your consent at any time, without affecting what we did before.
The quickest way to delete a beta request is the Remove my request link at the bottom of every beta email. For anything else, write to [email protected] from the address the request is about. We reply within one month. We may ask you to confirm the request from that address so we do not hand your data to someone else.
You can complain to the Information Commissioner's Office in the UK (ico.org.uk), or to the data protection authority where you live or work in the EEA. We would like the chance to put things right first, so please write to us.
Cookies
We use only cookies the service needs to work. None of them track you across sites.
- Sign-in cookies (authjs.session-token, authjs.csrf-token, authjs.callback-url and short-lived sign-in state): keep you signed in and protect forms. Removed when you sign out or after 8 hours.
- growth_tenant: remembers which workspace you had open.
- growth_consent: remembers your choice in the cookie notice, for 6 months.
- Cloudflare security cookies (such as __cf_bm): set by Cloudflare to tell people from bots.
If you choose to allow analytics in the cookie notice, the hub also loads our own Umami analytics from our EU server. It sets no cookies and stores no identifier on your device.
How we protect it
Connections are encrypted. Stored credentials are encrypted. Access to production is limited to the operator and uses keys, not passwords. Each workspace's data is kept apart from the others in the database. If a breach puts your data at risk, we will tell you and the regulator as the law requires.
Changes
When this notice changes we update the version and date at the top. If a change affects how we use data you already gave us, we will email you first. Earlier versions are available from [email protected].
See also the terms of the beta.