Privacy policy
This policy explains what personal data Bright Web Limited collects when you use Baseboard, why, who we share it with and what rights you have. It applies to the Baseboard website and dashboard at baseboard.bright-web.co.uk, the Baseboard CLI and SDK, and Baseboard's MCP server.
Last updated: 19 November 2026.
Who we are
Baseboard is run by Bright Web Limited, a private limited company registered in England and Wales under company number 17338706. Our registered office is Suite A, 82 James Carter Road, Mildenhall, Suffolk, IP28 7DE, United Kingdom.
For anything about your data, email support@bright-web.co.uk or write to us at the address above. We don't have a data protection officer; the same team handles every request.
Two kinds of data
Baseboard handles personal data in two different roles, and this policy covers them differently.
Your account data. When you sign up, invite a colleague or pay for a plan, we decide what to collect and why. For this data we are the controller, and this policy describes how we use it.
Your customers' data. Baseboard's job is to show you data from services your own app runs on: sign-in providers, billing providers, databases, error trackers, logs and so on. When Baseboard reads or changes records about your app's users, it does so only on your instructions, and you decide what is connected. For this data you (or your organisation) are the controller and we are your processor. The terms that govern that processing are in the data processing section of our terms. Questions from your app's users about their data should go to you, and we'll help you answer them.
What we collect about you
- Account details: your name, your email address and the name of your workspace, given when you sign up or accept an invite.
- Sign-in codes: a one-way hash of each six-digit code we email you, with how many attempts were made and when it expires. We never store the code itself.
- Workspace content: projects, pages, groups, alert rules and the alerts they've sent, theme and branding settings, member permissions, invites you create (including the invitee's email address), and access tokens you make for agents and the CLI (we store only a hash of each token).
- Credentials for services you connect: API keys, tokens and connection strings. These are encrypted before they are stored, using keys held in Google Cloud Key Management Service, and are never shown back in full.
- Activity records: an audit log of each action a member, access token or agent takes in a project (who, which tool, its input and whether it worked). Credentials are never written to it.
- Assistant conversations: messages you send to Baseboard's built-in assistant, its replies, the results of tools it ran for you, and the number of tokens each reply used.
- Billing records: your plan, how many members it covers, and the Stripe customer and subscription IDs. Card details go straight to Stripe and never reach us.
- Technical data: your IP address, browser type and the time of each request, recorded in our hosting providers' logs. We use these to keep the service running and to investigate abuse and errors.
We don't use advertising trackers or third-party analytics, and we don't buy data about you from anyone.
Why we use it and our legal basis
UK data protection law (the UK GDPR and the Data Protection Act 2018) requires a lawful basis for each use. Ours are:
| What we do | Legal basis |
|---|---|
| Create your account, sign you in, run your workspace and the services you connect | Performance of our contract with you |
| Take payment for paid plans and keep billing records | Performance of contract, and legal obligation (tax and accounting records) |
| Send sign-in codes, invites, alert emails you've set up, and notices about your account or these terms | Performance of contract |
| Run the assistant when you ask it something | Performance of contract |
| Keep logs and audit records, prevent fraud and abuse, and fix errors | Legitimate interests in keeping Baseboard secure and working |
| Respond to legal claims and requests from authorities | Legal obligation, or legitimate interests in defending our rights |
We don't send marketing email. If we ever want to, we'll ask first.
We don't make decisions about you that have legal or similarly significant effects based solely on automated processing.
Who we share it with
We use these service providers to run Baseboard. Each acts on our instructions under a written contract and may only use your data to provide its service to us.
| Provider | What they do | Where data is processed |
|---|---|---|
| Convex, Inc. | Database and backend hosting | Ireland (AWS eu-west-1) |
| Cloudflare, Inc. | Serves the website and dashboard | Worldwide edge network |
| Resend (Plus Five Five, Inc.) | Sends sign-in, invite and alert emails | United States |
| Anthropic, PBC | Runs the AI model behind the built-in assistant | United States |
| Google LLC (Google Cloud) | Holds the encryption keys that protect stored credentials | Google Cloud region for our key ring |
Payments. Paid plans are sold through Stripe's managed payments service, which acts as the merchant of record. Stripe collects your payment and billing details, works out and files VAT and sales tax, and sends receipts. Stripe is a controller for the data it collects at checkout, under Stripe's privacy policy.
The assistant. When you ask the assistant something, your message, earlier messages in that chat and the results of any tools it runs (which can include records from services you've connected) are sent to Anthropic to produce a reply. Under the commercial terms we use, Anthropic doesn't use this data to train its models.
Services you connect. When you connect a provider (for example Stripe, Supabase or Sentry), Baseboard calls that provider with the credentials you gave it. Data you send there, such as a refund or a ban, is handled under your own agreement with that provider.
Alert destinations. Alerts you configure are posted to the Slack channel, Microsoft Teams channel, webhook URL or email address you chose.
We may also disclose data when the law requires it, to protect people's safety, or to a buyer if Bright Web Limited or Baseboard is sold. In a sale, the buyer would have to keep to this policy.
We never sell personal data.
International transfers
Some providers above process data outside the UK. Where a provider is in a country without a UK adequacy decision, we rely on the UK International Data Transfer Addendum to the EU Standard Contractual Clauses, or the UK Extension to the EU-US Data Privacy Framework where the provider is certified under it. You can ask us for a copy of the relevant safeguards.
How long we keep it
- Account and workspace data: while your account exists. When you ask us to close your account or delete a workspace, we delete it within 30 days, except what we must keep for legal reasons.
- Sign-in codes: each code expires after 10 minutes, and its record is deleted when it's used, replaced by a newer code or expires.
- Audit log: while the workspace exists. Your plan controls how far back the dashboard shows it.
- Assistant chats: while the workspace exists. Starting a new chat archives the old one, which is kept with the workspace.
- Billing and tax records: six years after the end of the financial year they relate to, as UK tax law requires.
- Hosting logs: kept by our providers for their standard periods, usually no more than 30 days.
How we protect it
Credentials for connected services are encrypted with envelope encryption: each is sealed with a data key, and that key is sealed with a key in Google Cloud KMS that never leaves Google. All traffic to Baseboard uses HTTPS. Members only see and change what an owner has allowed, and every change is written to the audit log. No system is perfectly secure, but if a breach puts your rights at risk we'll tell you and the Information Commissioner's Office as the law requires.
Cookies and browser storage
Baseboard doesn't set advertising or analytics cookies. It stores a few items in your browser's local storage because the dashboard can't work without them:
- your sign-in session, so you stay signed in;
- a sign-in that's waiting for its emailed code, so a reload doesn't lose it;
- the colour theme you picked, so pages draw in it straight away.
These are strictly necessary for a service you've asked for, so the law doesn't require a consent banner for them. Signing out clears the session. Stripe sets its own cookies on its checkout pages to process payment and prevent fraud.
Your rights
Under UK data protection law you have the right to:
- get a copy of the personal data we hold about you;
- have inaccurate data corrected;
- have your data deleted;
- restrict how we use it, or object to uses based on legitimate interests;
- receive data you gave us in a machine-readable format, or have it sent to another provider.
To use any of these, email support@bright-web.co.uk. We'll reply within one month, and we may ask you to confirm your identity first. Exercising your rights is free unless a request is clearly unfounded or excessive.
If your request is about your app's users' data that Baseboard processes for you, you (as controller) handle it, and we'll help.
Complaints
If you're unhappy with how we've handled your data, please tell us first at support@bright-web.co.uk and we'll try to put it right. We'll acknowledge your complaint within 30 days.
You can also complain to the UK's data protection regulator, the Information Commissioner's Office, at ico.org.uk/make-a-complaint or on 0303 123 1113.
Children
Baseboard is for people running software businesses. It isn't meant for anyone under 18, and we don't knowingly collect data from children.
Changes to this policy
We'll update the date at the top when this policy changes. If a change affects how we use data you've already given us, we'll email account owners before it takes effect.