Privacy Policy
This policy explains what AC Bridge records about you, why, how long we keep it, and what you can do about it. It is written to be read, not to be survived. If anything here is unclear, ask us and we will explain it.
The one thing to know AC Bridge records your sessions by default. When you use the Service, the contents of the Claude Code and Codex sessions you drive through it are sent to our servers and stored. This happens on every plan — trial and paid alike — unless you turn it off. We do this to run and improve the Service. What this includes, and how to turn it off.
What we will not do We do not sell your data. We do not share it with advertisers, brokers, or dataset buyers, and we never will under this policy. If that ever changes, it would require a new version of this policy and your explicit, opt-in agreement — not a quiet edit to this page. AC Bridge is funded entirely by subscriptions.
Who we are
AC Bridge is operated by Sam Holmes, a sole trader based in the United Kingdom, trading as AC Bridge. For data-protection purposes we are the controller of the personal data described here. You can reach us at privacy@ac-bridge.com.
What the Service does
AC Bridge turns the smart devices around you into ambient status lights for Claude Code and Codex sessions running on your own computer, lets those agents control the devices you allow, and syncs your settings and connected devices across your machines. The agents run under your own accounts on your hardware — we do not provide Claude, Codex, or any agent, and we hold no Anthropic or OpenAI API key. AC Bridge works with Claude Code and Codex but is not affiliated with, sponsored by, or endorsed by Anthropic or OpenAI.
What we record, and how to stop it
Recording is on by default on every plan. It is not tied to your subscription and it is not tied to consent — if you do nothing, we record. We think being blunt about that is better than burying it.
When recording is on, we store:
| What | Meaning in plain words |
|---|---|
| Session transcripts | The contents of the Claude Code and Codex sessions you drive through AC Bridge — your prompts, the agent’s responses, and the tool activity in between. In practice this can include your source code, file contents, and command output. |
| Approval previews | A preview of a command or tool call that an agent asked permission to run, so we can show you what you approved. |
| Session index | Working directory path, git branch name, CLI version, timestamps, token counts. |
Before any of this leaves your machine, our software scans it and strips things that look like secrets — API keys, private keys, tokens, and your home-directory path. This is a safety net, not a guarantee. Ordinary text is not redacted, and redaction cannot know that a given string is sensitive to you.
To turn recording off, use any of these. They take effect on the machine you run them on:
- Run
acbridge capture offon that machine. - Set
BRIDGE_NO_CAPTURE=1in the environment. - Drop an
.acbridge-no-capturefile in a project to exclude it.
Turning recording off does not change your plan, your price, or what the Service can do for you. There is no penalty for it, and we do not treat you differently for using it.
Everything else we hold
| Data | What it is | Why we have it |
|---|---|---|
| Account identity | Email address, display name, and a user id from our login provider. A profile picture URL if your sign-in provider supplies one. | To sign you in and route agent state to your own sessions. |
| Billing state | Your Stripe customer and subscription ids, plan status, trial dates, renewal date, billing interval, and a US/UK region flag. | To run your subscription. We never see or store your card details — those go straight to Stripe. |
| Account events | Sign-up, sign-in, plan changes, starting checkout, downloading the app. | Support, fraud prevention, and understanding whether the product works. |
| Usage counters | Counts only: devices controlled, profiles, actions, sessions, machines, relay time, token totals. | To show you your own usage and to size the Service. |
| Your machines | A label you choose and the operating system. Not your hostname, and not an automatic identifier. | To show you which machines are paired. |
| Smart-home devices | Device names, makes, models, rooms, and the commands sent to them. | So you can map agent states to your devices and let agents control the ones you allow. |
| Linked accounts | Access tokens for smart-home services you connect, encrypted so we cannot read them. | To talk to those services on your behalf. |
| Error logs | Diagnostics when something breaks. | To fix it. |
What we deliberately do not collect
- No IP addresses. We do not store your IP address or MAC address in our databases. Our hosting and security providers process IP addresses at the network layer in order to deliver and protect the Service, as any host must.
- No card numbers. Stripe collects and holds those; we only ever see an identifier.
- No passwords. Our login provider handles authentication.
- No location tracking. We use your country only to pick a currency at checkout, and only keep whether you paid in US or UK pricing.
Our lawful bases (UK GDPR)
| Purpose | Lawful basis |
|---|---|
| Creating your account, signing you in, routing agent state, syncing your settings, taking payment | Contract — we cannot provide the Service you asked for without this. |
| Recording sessions to run, debug, and improve the Service | Legitimate interests — ours, in making the Service work and making it better. We have weighed this against your privacy: it is why recording is disclosed at the top of this page rather than buried, why it can be switched off per machine at any time with no penalty, why secrets are stripped before upload, and why the data is deleted on the schedule below. |
| Keeping the Service secure and preventing abuse | Legitimate interests — ours and every other user’s, in a Service that is not abused. |
| Meeting our tax and accounting obligations | Legal obligation. |
Where we rely on legitimate interests, you have the right to object — see Your rights below. For recording specifically, you do not have to wait for us: turning capture off on a machine is immediate and unconditional.
Your sessions can contain almost anything
Please take this seriously
A session transcript comes from your own computer. It can contain source code, file contents,
command output, customer data, credentials you typed, and other people’s personal
data. We strip what looks like a secret, but we cannot know what is sensitive to you or
to a third party. You decide what enters a session. If you work with material
you are not free to share with us, exclude it with .acbridge-no-capture, or run
acbridge capture off on that machine. If your sessions contain other people’s
personal data, you are responsible for having a basis to put it there.
Anyone who can reach a paired device is acting through your setup
Please take this seriously AC Bridge lets your agents change the devices you allow, and shows session state on the lights around you — anyone in the room can see it, and anyone who can reach a paired device or session is acting through your setup. Only use AC Bridge where that is acceptable to you, scope device control to what you are comfortable with, and keep approval prompts on for anything that matters.
How long we keep it
Recorded content is deleted on a schedule, automatically. It first sits in our live database, then moves to encrypted cold storage, then is destroyed:
| Data | Live database | Cold storage | Total |
|---|---|---|---|
| Session transcripts | 30 days | 24 months | ~24 months |
| Connection + device events | 30–90 days | 12 months | ~12 months |
| Approval previews | 365 days | not archived | 12 months |
| Error logs | 30 days | 6 months | ~6 months |
Your account details, billing state, and usage counters are kept for as long as your account exists, and are deleted within 30 days of you asking us to close it. We keep a minimal, permanent record that a deletion happened, and whatever our tax obligations require us to keep — typically invoice records for six years.
Your rights
Under UK GDPR you have the right to access your data, correct it, delete it, restrict or object to how we use it, and to receive a portable copy. Exercising any of them costs you nothing and we will not treat you worse for it.
To use any of these, email privacy@ac-bridge.com. We will respond within 30 days. Requests are fulfilled by a person, not a button — we would rather tell you that than pretend otherwise. A deletion removes your content from our live database and from cold storage, and unpairs your machines.
If you think we have got this wrong, please tell us first — but you have every right to complain to the Information Commissioner’s Office (ico.org.uk), or to your local supervisory authority if you are in the EEA.
Who else touches your data
We keep this list short on purpose. Each of these processes data under its own terms, and only to do the job named:
| Who | What for | What they get |
|---|---|---|
| Cloudflare | Hosting, network security, cold storage, and aggregate site analytics | Traffic to the Service; stored transcripts at rest |
| Neon | Database hosting | Everything described above that is stored |
| WorkOS | Sign-in and accounts | Your email, name, and sign-in activity |
| Google, Microsoft, GitHub, or Apple | Only if you choose to sign in with them | The fact that you signed in, per that provider’s own terms |
| Stripe | Payments and the billing portal | Your name, email, card details, and billing address — collected directly by Stripe |
| Resend | Sending you the welcome email | Your email address and name |
| Your smart-home providers | Only those you connect yourself — for example Philips Hue, SmartThings, Nest, Tuya, LIFX, Kasa, Shelly | The device commands you ask us to send |
| Google Fonts | Delivering the fonts on this website | Your IP address and browser, when a page loads |
| Anthropic | Not our sub-processor — your prompts reach Claude through your own Claude account on your own machine | Governed by your agreement with Anthropic, not ours |
Where your data goes
Some of the providers above are based in, or store data in, the United States. Where personal data leaves the UK we rely on the safeguards UK law requires — the UK extension to the EU Standard Contractual Clauses, or an adequacy decision where one applies.
Security
Everything travels over HTTPS or WSS. Agent state and device commands can only reach sessions and devices linked to your own identity, only your paired relay can put anything into a session, and anything needing approval is surfaced for you to confirm rather than simply running. Tokens for services you link are encrypted before storage, and we cannot read them.
Children
AC Bridge is a developer tool and is not intended for children. Do not use it if you are under 16, or under the minimum age in your country if that is higher.
Changes to this policy
This page carries a version and an effective date at the top. If we make a material change we will raise the version and tell you. We will never widen what we do with data you have already given us by quietly editing this page.
Contact
Email privacy@ac-bridge.com — a person reads it.