Bridge Builders
HomeAboutServicesContact

PRIVACY

Privacy. The short version:

This website doesn’t track you. No cookies, no tracking pixels, no analytics, no session recording, no advertising networks, nobody else’s scripts. Our forms prepare a message in your own email app instead of posting it to a database, and our AI assistant runs on your device without sending us a word.

We receive information about you when you deliberately send it — you email us, ask for a proposal, or become a customer. Then we hold it like any business holds its email and its invoices, and we say so below rather than pretending otherwise.

That’s not a promise you have to trust — it’s something you can check. Open your browser’s developer tools and watch the network while you use this site. The rest of this page is the detail behind it.

Most privacy policies are long because the company is doing a lot with your data and would rather you didn’t notice. Ours is short because we aren’t.

If any of it is unclear, ask us. It’s a policy about you; you should be able to read it.

1. We don't use cookies, and we don't track you

No cookies. No tracking pixels. No analytics. No session recording. No advertising networks.

There's no cookie banner on this site because this site doesn't set cookies. We're not being clever with the wording.

We don't use Google Analytics, heatmaps, session recording, or any other tool that watches what you do here. We can't tell how long you stayed, which pages you read, or what you clicked. We may look at aggregate search-performance information — how often our pages show up in a search engine and get clicked — but that describes our pages, not you, and it doesn't follow you around this site.

Nothing on this website loads from anyone else's server: no third-party fonts, scripts, tag managers, or embedded widgets. There's no back door for someone else to watch you through, and it's enforced by an automated check on every deployment rather than by good intentions.

You don't have to take our word for any of it. Open your browser's developer tools, look at the Network tab, and reload this page — every request goes to one place. Check the Application tab for cookies while you're there. That's better proof than a paragraph of assurance.

2. When you chat with our AI assistant

Right now, your conversation doesn't leave your browser.

The assistant on this site runs entirely on your own device. It answers from a list of approved information that was downloaded with the page. When you type a question, our website doesn't transmit it — not to us, and not to an AI provider. We can't read your conversation because we never receive it.

Our code doesn't save a transcript, and closing the tab ends it. We can only speak for our own code, though: browser extensions, accessibility tools, or other software on your device are outside our control, as they are on any website.

The honest caveat: we're upgrading the assistant to a real AI model, and when we do, your messages will have to be sent off your device to be answered. That's how those models work. When it changes, this page changes with it — before the feature goes live, not afterwards. We're not going to quietly redefine what this section means.

If you use the assistant's "share my details" form, see the next section — that part works like any other form here.

3. When you contact us, or send an order

Our forms don't post your details to a database. They prepare an email for you to send.

There's no Bridge Builders database or form-handling backend behind this site — it's a set of static files. So the contact form, the order form, and the assistant's details form all do the same thing: compose an email, fill it in with what you typed, and hand it to your own email app. You press send, or you don't.

Nothing reaches us until you deliberately send it. Change your mind and close the email, and we'll never know it existed — there's no half-finished record sitting in a database somewhere.

Once you press send it's an ordinary email, and it travels like one: your own email provider handles it, then our domain registrar (Porkbun) forwards it, then it lands in our inbox at Google. Each of those handles the message under its own terms, and each can see what's in it — as is true of every email anyone has ever sent. It gets filtered for spam and backed up like any other mail.

Please don't send passwords, card numbers, government ID numbers, or medical details this way. Email isn't the place for them, here or anywhere, and there's no reason you'd need to.

What we end up with is your name, your email address, whatever you chose to tell us, and — if you sent an order — the options you picked and the estimate attached to them. In a normal inbox. Not a marketing platform, and not a CRM watching whether you opened our reply.

4. What your browser remembers

It's browser storage, not a cookie — and it stays on your device.

If you use an estimator or start an order, your browser saves your choices locally so you can close the tab and come back to your quote instead of starting over. The BridgeView demo does the same if you rearrange it.

That sits on your own device and our website doesn't transmit it anywhere. We're not being coy: code running on a website can technically read that site's own browser storage — ours simply doesn't send it to us, which is why there's no copy of your half-finished quote on our side to lose.

You can clear it any time by clearing this site's data in your browser. Bear in mind that browser sync, device backups, or extensions are outside our control, as they are for any site.

5. What our web host can see

Our website is delivered by a company called Vercel. To serve and secure a page, their systems process the technical information any web server needs — your IP address, an approximate location derived from it, your browser and device type, which page you asked for and when, where you came from, and security and diagnostic logs.

That's how the web works and no website can switch it off. Some of it Vercel handles for us; some it handles for its own security, operational, and legal purposes, under its own terms.

We don't use any of it to identify or profile anyone. We're a small shop — we look at logs when something is broken.

If you're a customer, your own site runs on a hosting account in your name, so those logs are yours rather than ours.

6. Who else is involved

Short enough to print — which is the point.

Most websites quietly involve a dozen companies: analytics, ad networks, tag managers, chat vendors, CDNs. Each one is somebody else who sees you. Ours is short enough to list, so here it is.

Just visiting the site: Vercel, who deliver the pages, and nobody else. No analytics, no ad tech, no third-party fonts or scripts.

Using the assistant: nobody. It runs on your device.

If you email us or send an order: Porkbun, our domain registrar, forwards the message, and Google holds our inbox. Both can see what's in it, the way any email provider can. We also use ordinary business tools you'd expect — invoicing and payment processing when you become a customer, and accountants or lawyers if we ever genuinely need them.

That's the list. We don't sell your information to any of them, and none of them are here to watch you. When it grows, this section grows with it — before the feature ships, not after.

7. What we do with what you send us

Mostly, we reply to you. That's why you sent it and it's why we want it.

Beyond that, we use it for the ordinary business the message is part of: preparing a proposal, doing the work you asked for, invoicing you, supporting you afterwards, keeping the records a business has to keep, and dealing with a problem if one comes up. Nothing else.

We keep your message so we can pick the conversation up where we left it, the way anyone keeps their email.

We don't add you to a mailing list because you asked a question. If we ever start a newsletter, you'll have to actually ask for it.

If you become a customer, we'll hold the practical things we need to do the work — your contact details, what we agreed, and access to accounts that are in your name.

8. What we will never do

We don't sell your data. There's no asterisk on that sentence.

We don't sell, rent, or trade your information, or your customers' information, to anybody. Not to advertisers, not to data brokers, not to "partners". We don't hand it over for targeted advertising.

We don't run ads on this site, or on yours.

We don't use your information, or your customers' information, to train AI models — ours or anyone else's. Where we use an AI tool to help draft something for you, we use accounts configured so your content isn't used for training.

We don't pass what you tell us to anyone beyond the handful of providers in section 6 who actually run the business — the people who deliver our mail, hold our inbox, and process an invoice. That's not sharing your data around; that's what using email and getting paid consists of.

The exception nobody can avoid: if the law genuinely required it, we'd comply — and we'd tell you, unless we were legally forbidden from doing so.

9. If you're a customer: your data and your customers' data

Everything we build runs in accounts that are in your name — hosting, payments, email, analytics if you choose to have any. We work inside them rather than holding them, though we do keep the ordinary things: our emails with you, invoices, and working copies of your content while we build.

That means your customers' data belongs to you, sits in your accounts, and comes with you if you leave. It was never ours to keep.

If your site takes payments, your customers enter their card details on your payment processor's own secure page, never on a form we built. We never see, store, or transmit card numbers, and we're never in the money flow.

If you collect information from your own customers, you're the one responsible for what you collect and why — you'll need your own privacy policy for your site. We'll help you understand what your site does; we can't be your legal advisor.

10. How long we keep it

An enquiry that goes nowhere: we keep it while it's useful to reply and remember the conversation, and we're not precious about deleting it after that. Ask and it's gone.

Customer records — what we agreed, invoices, the project itself: as long as we're working together, and afterwards for as long as we need them for tax, accounting, and the possibility of a dispute. That's a few years, not forever, and it's the same rule any business runs on.

Access to your accounts: removed when we no longer need it, and you can revoke it yourself at any time without asking us.

Backups are the honest caveat. Copies can sit in ordinary email and system backups for a while after deletion, until those roll over on their own. Nobody is reading them; they just take time to age out.

11. How we protect it

We use reasonable safeguards, sized to a small business handling a small amount of information: multi-factor authentication on the accounts that matter, a password manager rather than a notes file, access limited to what a job needs, and access removed when it's done.

We use account invitations rather than asking you for passwords. If anyone ever emails you asking for your password and claims to be us, it isn't us.

We're not going to claim perfect security, because nobody can. Email, devices, and websites can all be compromised, and a policy that promises otherwise is lying to you. If something did go wrong with information we hold, we'd tell you — promptly, and with what we actually know rather than a press release.

12. Do Not Track and Global Privacy Control

Some browsers send a "Do Not Track" or "Global Privacy Control" signal asking sites not to track you or sell your information.

We don't change anything when we receive one, for the simplest possible reason: we already don't do those things. We don't follow you across other websites, we don't sell personal information, and we don't disclose it for targeted advertising. There's nothing for the signal to switch off.

We also don't let anyone else collect your activity across other sites through this one — there's nobody else here to do it.

13. Your data, your call

Ask us what we have about you and we'll tell you. It won't be a long list.

Ask us to correct something and we'll fix it. Ask us to delete it and we will.

Two honest limits. We may need to check you're you first — handing your information to whoever asks for it would be a strange way to protect it. And we may need to keep some things: invoices and tax records, or anything caught up in a live dispute. If that happens we'll tell you exactly what we kept and why, rather than hiding behind the word "legal".

There's no form for this and no ticket system. Send an email; a person reads it.

14. Children

This is a website for business owners. It isn't aimed at children, and we don't knowingly collect anything from anyone under 13. If you think a child has sent us something, tell us and we'll delete it.

15. Changes to this policy

If what we do changes, this page changes first — not months later. The date at the bottom tells you when it last moved.

The specific one we already know about: upgrading the assistant to a real AI model will mean your messages get sent off your device. That's a genuine change to this policy, and we'll make it here before we ship it, not after.

Want to know what we have about you?

Ask, and we’ll tell you. Ask us to delete it, and we will.

hello@bridgebuildersai.com

Last updated: July 17, 2026

Bridge Builders

hello@bridgebuildersai.com | Consultations by request

TermsPrivacy

Powered by RunaAI™