Privacy Policy
This policy explains what AC Bridge collects 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.
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 AC BRIDGE LIMITED, a company registered in England and Wales under company number 17356395, 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 keeps your settings and devices on your account, so they follow you to the computer you sign in on (one machine is active at a time). 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 collect
From the app and the bridge on your computer, we collect device and usage data only:
| What | Meaning in plain words |
|---|---|
| Device registry and profiles | The devices you add, and the profiles that decide what each device does for each agent state. |
| Your machines | Which computers are paired to your account, and when they connect to or disconnect from our servers. |
| Device and state events | Which light changed, to which state, and when — including when a session flags that it needs you, is working, or has finished. A session is identified by its name and the path of the project folder it runs in. |
| Device audit trail | A record of the commands sent to your devices, what sent them, and whether they worked. |
| Error reports | None: the app and the command-line tool send us no error reports. Our servers’ own error log, and the reports this website sends when its code fails in your browser, are listed under Everything else we hold. |
We use it to run the Service, to keep it working, to show you your usage in your account, to show aggregate usage in our admin console, and to improve the product.
Your prompts, your code, your files, the agent’s replies and your session transcripts are never collected — the hooks send only state changes.
Session transcripts were collected under earlier versions of this policy. Collection stopped on 27 September 2026. The transcript data collected before 27 September 2026 was deleted on 27 September 2026 and is not used for anything; backup copies of it expire within 30 days of that date.
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 store your card details and never see your full card number; to show your card in your account, we read its brand, last four digits and expiry from Stripe. |
| Account events | Sign-up, sign-in, plan changes, starting checkout and downloading the app; payments, refunds and disputes; email delivery problems (bounces and complaints); and a sign-up started at our login provider but never finished, with the email address it used. The events started from your browser carry the approximate country and city our hosting provider derives from your connection, and your browser’s user agent (which browser and operating system you use). Your first sign-up also records how you found us. | Support, fraud prevention, understanding whether the product works, and knowing which links bring people to us. |
| Usage counters | Device, action, profile and machine counts, together with your device names, makes and models, your machine’s name and operating system, and your profile names, so your account page can show them. | To show you your own usage and to size the Service. |
| Your machines | A machine label — your computer’s short name unless you set your own — and the operating system. | 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 | Tokens for the cloud services you link through us (SmartThings today), encrypted at rest with a key held outside the database. Our servers decrypt them only to hand your own computer a fresh access token or to renew the token with SmartThings, never for anything else. The keys and logins for every other service you connect are kept on your computer and never reach us. Keys for devices on your own network never leave your machine. | To talk to those services on your behalf. |
| Error logs | Our servers’ record of their own errors, and the error message and page address this website sends when its code fails in your browser. | To fix it. |
How you found us
When you create your account, we record how you reached the site, so we can tell which websites, posts and campaigns actually bring people to AC Bridge. The record holds, at most:
- the campaign tags in the link you followed (
utm_source,utm_medium,utm_campaign,utm_term,utm_content, or areftag), and an ad click id (gclidorfbclid) if the link carried one; - the website that sent you, by its domain name only (for example
www.google.com) — never the address of the page you were on, and never the sign-in or payment pages you pass through on your way back to us; - the first page you opened on this site in that browser tab (for example
/docs), without anything after a?.
Your browser keeps this in the tab while you look around (see Cookies, local storage and analytics) and sends it to us when you start a sign-in or sign-up. We keep it only if this is your first sign-up, attached to that sign-up event; on any other sign-in it is thrown away. Like every account event it is deleted automatically after 400 days, and it is erased if you delete your account.
You can object to this at any time, and it costs nothing: email privacy@ac-bridge.com and we will delete the record from your sign-up event.
Cookies, local storage and analytics
This site uses no advertising or tracking cookies. Everything it stores in your browser is listed here. The sign-in cookies, the signed-in flag and the welcome-window flag are there so the site works; the how-you-found-us entry is for our own measurement and lives only in that one browser tab.
| Name | What it is | How long |
|---|---|---|
__Host-wos_session (cookie) | Your sign-in session, sealed so only our server can read it, and HttpOnly, so no script on the page can read it either. Set only when you sign in. | Up to 30 days, or until you sign out |
__Host-wos_oauth_state, __Host-wos_return_to, __Host-wos_attribution (cookies) | Used only while a sign-in is in progress: a one-time security check, the page to return you to, and the how-you-found-us record on its way to our server. HttpOnly. | 30 minutes at most; cleared when the sign-in completes |
ac:attribution (sessionStorage) | The how-you-found-us record, held in this browser tab only. It is sent to us only when you start a sign-in or sign-up. | Until you close the tab |
ac:onboard:dismissed: followed by a one-way code made from your account ID (localStorage) | Remembers that you closed the welcome window in your account area, so it does not open again. It holds no email address, and the code cannot be turned back into your account ID. | Until you clear this site’s data |
ac:signed-in (localStorage) | Remembers that you have signed in on this browser, so the Log in page can take you straight to your account instead of asking you to sign in again. It holds no identity or password; your server-side session decides. | Until you sign out, your session ends, or you clear this site’s data |
Signing in takes you through pages run by our login provider, WorkOS (and Google, GitHub or Microsoft if you choose one of them), and paying takes you to Stripe. Those pages sit on their own domains and may set their own cookies under their own policies.
Analytics. We count visits with Cloudflare Web Analytics, which Cloudflare adds to our pages as they are served. It sets no cookies and stores nothing in your browser, Cloudflare states that it does not fingerprint visitors, and what we see is only totals: page views per page, referring sites, countries, browsers and device types. It is added for every visitor, wherever they are, including the UK and the European Union, and it works in the same cookie-free way for all of them; if we ever change that, this page will say so. There is no other analytics, advertising or session-recording tool on this site. If the site’s code fails in your browser, it sends us the error message and the page address so we can fix it.
What we deliberately do not collect
- No session content. Your prompts, code, files and the agent’s replies stay on your machine (see What we 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 see only an identifier and, to show your card in your account, its brand, last four digits and expiry.
- No passwords. Our login provider handles authentication.
- No precise location. We never ask your device where it is. The approximate country and city on your account events come from our hosting provider’s view of your connection, and the US/UK flag on your billing record, still set from your country at checkout, no longer affects the price: everyone pays one price, in pounds sterling.
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. |
| Collecting device and usage data to run the Service, keep it working, show usage in your account and our admin console, and improve the product | Legitimate interests — ours, in running the Service and making it better. We have weighed this against your privacy: the data is limited to your devices, the names of your machines, profiles and sessions, project folder names and paths, states and counts, never the content of your sessions, and it is deleted on the schedule below. |
| Sending you one reminder, about a day before your free trial ends and your card is first charged | Contract — it is part of running the subscription you started, so the first charge is never a surprise. It is the only reminder we send. To unsubscribe from any email that is not essential to your account, reply “unsubscribe” or write to privacy@ac-bridge.com. |
| Understanding which sites and campaigns bring people to AC Bridge (how you found us) | Legitimate interests — ours, in knowing which of our links are worth the effort. The record is small (campaign tags, a domain name and a path on this site), kept once per account, and you can object for free. |
| Keeping the Service secure and preventing abuse, such as taking the free trial more than once | 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.
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 run an agent on your computer, is acting through your setup. Only use AC Bridge where that is acceptable to you, scope device control to what you are comfortable with, keep approval prompts on for anything that matters, and do not disable permission checks for an agent that can control your devices.
How long we keep it
Device and usage events are deleted on a schedule, automatically. They first sit in our live database; some then move to encrypted cold storage, and all are destroyed at the end:
| Data | Live database | Cold storage | Total |
|---|---|---|---|
| Connection + device events | 90 days | Device events: 12 months. Connection events are not archived. | Device events ~12 months; connection events 90 days |
| Error logs | 30 days | 6 months | ~6 months |
| Approval log (which tool asked for permission, its short description, and the answer) | 365 days | Not archived | ~12 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. Deleting an account erases your email address, name, usage counters, and the approximate country, city and browser recorded with your account events. What an erasure keeps is the billing record we are required to retain: the Stripe customer reference, your plan and billing history, and the dates and types of account events — with nothing in them that identifies you. We also keep a minimal, permanent record that a deletion happened, and whatever our tax obligations require us to keep — typically invoice records for six years. To stop one person taking the free trial more than once, an erasure also keeps a one-way fingerprint of your email address for 12 months (a keyed code the address cannot be read back from), and, if a card started a free trial, Stripe’s fingerprint of that card (an opaque code, never the card number), with its link to your account removed. If a live plan or trial is running, we cancel it first so you are not charged again.
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 from the address on your account (for a deletion, we confirm with that address before we act). 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 data 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, the event archive and database backups, and aggregate site analytics | Traffic to the Service; archived device events, error logs and backups at rest |
| Neon | Database hosting | Everything described above that is stored |
| WorkOS | Sign-in and accounts | Your email, name, and sign-in activity |
| Google, GitHub or Microsoft | 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 email address and account id, which we send; your name, payment details and billing country or postcode, which Stripe collects directly |
| Resend | Delivering our emails: your sign-in codes (composed by WorkOS), the welcome, and account and billing notices such as the trial-ending reminder, payment problems and cancellation confirmations | Your email address, your name, and the content of those emails |
| GitHub | Running our nightly database backup job | A copy of our database, only while the job runs, before it goes to storage with Cloudflare |
| Your smart-home providers | Only those you connect yourself. Cloud services (SmartThings, Govee, Tuya, Meross, eWeLink) are reached from your computer; devices on your home network (Philips Hue, LIFX, Kasa, Shelly and others) are controlled there directly | A cloud service you connect gets your login or key for it, and the commands and status requests sent from your computer. Devices on your home network send nothing to their makers through AC Bridge; to find a Hue bridge, your computer asks the discovery service of Signify (the maker of Philips Hue) where it is. |
| 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 between your computer and our servers travels over HTTPS or WSS; commands on your home network use each device’s own local protocol. Device commands can only reach devices linked to your own account, and actions on locks, doors, garages and valves wait for your confirmation. Tokens for services you link through us (SmartThings today) are encrypted before storage, with the key held outside the database, and our servers decrypt them only to hand your own computer a fresh access token or to renew the token with SmartThings. Keys for devices on your own network never leave your machine.
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.