Privacy. The short version:

1. We don't use tracking cookies or behavioral profiles

No ad tracking, pixels, heatmaps, session recording, advertising networks, or cross-session visitor profiles.

The public pages do not set tracking cookies. BridgeView is a private owner dashboard; when an authorized owner signs in, Supabase sets essential authentication cookies so the session can stay secure. Those cookies are not advertising or behavioral tracking.

We don't use Google Analytics, heatmaps, session recording, or tools that build a visitor profile. The site records first-party aggregate page views and approved email, phone, and contact-page actions so the owner can see whether the website is being used. These events are not joined into a visitor or cross-session profile. We may also use aggregate search-performance reports supplied by search engines; those reports describe our pages rather than following you around the site.

The browser loads the site's application assets from our Vercel deployment. Website activity, Assistant events, and forms post only to same-origin Bridge Builders routes; those server routes use the providers named below. The site does not embed third-party chat scripts, ad tags, tracking pixels, or remote fonts.

Website activity events contain a random event ID, sanitized route ID, event type, optional approved contact-action ID, and timestamp. They do not contain a name, email, phone number, query string, referrer, form content, cookie, or visitor/session identifier. The Assistant separately records bounded operational events so we can see whether approved topics were answered or handed off. Those events contain an event ID, session ID, approved topic IDs, outcome, optional thumbs-up or thumbs-down rating, and timestamps. They never contain the visitor's question, the Assistant's answer, or a transcript.

2. When you chat with our AI assistant

Your free-form conversation stays in your browser; only privacy-bounded operational events are recorded.

The RunaAI-powered Assistant runs in your browser and answers from Bridge Builders-approved information downloaded with the page. If it cannot match a confident answer, it asks one clarification and then offers a human handoff rather than guessing. The website does not transmit the words you type or the answers it generates to Bridge Builders or to an AI model provider.

We record the bounded event fields listed above to operate and improve the approved knowledge. We do not record free-form question text, answer text, or conversation history. A connection address is used transiently to enforce abuse limits; only a one-way keyed hash is stored, and it is deleted after two days.

Our code doesn't save a transcript, and closing the tab ends the conversation. Browser extensions, accessibility tools, browser sync, or other software on your device remain outside our control, as on any website.

If you choose the Assistant's Share my details form, the name, email, optional phone, and note you submit follow the form process below. The chat transcript is not attached.

3. When an AI receptionist answers a call

Press 1 first. Until then, the call is not recorded, transcribed, or sent to an AI model.

This section applies when a phone number is configured to use our AI Receptionist. Basic telephony transport and call-detail metadata exist when the call connects, but recording, transcription, speech recognition, AI streaming, automated intake, and call-content storage remain off while the fixed notice plays.

The notice names the business, identifies the system as an AI receptionist, explains recording/transcription/service-provider processing, and requires the caller to press 1. Pressing 2, speaking, staying silent, entering another key, or timing out does not consent and does not unlock protected processing. The caller is offered the configured non-recorded alternative or may hang up. After consenting, the caller may press 9 to revoke consent; protected processing must stop and remain blocked.

After consent, the system may process the caller's phone number, call audio, transcript, call summary, message, appointment request, routing choice, and whatever details the caller voluntarily provides for the request. Callers should not provide passwords, complete payment-card numbers, government identification numbers, medical details, or other information the business did not ask for.

The provider chain is split. Twilio is the client's own account: it carries the call and, when enabled, holds the recording. ElevenLabs generates the receptionist's voice and the AI provider named in the client's proposal processes the consented conversation to respond and summarize; both of those run in Bridge Builders accounts. The voice provider processes the call audio as the call happens in order to understand and reply, but does not store it. What it keeps is the transcript, and that transcript sits in a Bridge Builders workspace, not the client's. We say so plainly rather than imply otherwise: the transcript is the record of the conversation, we hold it for as long as the business is a client of ours, and when that relationship ends we provide it to them and delete it from our side. We apply that configuration per client and read it back to confirm it took effect.

The consent audit keeps the provider call ID, exact notice text and version, language, notice start and completion times, consent or revocation response, and response time. It does not contain pre-consent audio or a pre-consent transcript. Before activation, the client accounts must be configured and tested so that call content is kept only on the schedule published here, unless the client's published policy and signed proposal document a lawful reason for a different period. For this deployment that configuration is in place and verified: the 30-day boundary is applied in the operational store, audio storage is switched off at the voice provider so no recording is kept there, and both the deletion job and the provider configuration are covered by automated checks. Provider security logs and rolling backups follow the applicable provider contract.

We do not create voiceprints, identify callers by the sound of their voice, make consequential eligibility decisions, or use call content to train AI models as part of the standard service. Outbound automated calls and texts are disabled unless separately scoped with the required consent, opt-out, suppression, and recordkeeping controls.

4. When you contact us, send an order, or share your details

Submitted forms are saved to the private BridgeView lead store and send an email alert to Bridge Builders.

The contact form, order form, and Assistant details form send the fields you deliberately submit to a same-origin server route. Draft text is not sent. After validation and abuse controls, the submission is stored in a Bridge Builders Supabase project and appears in the authenticated BridgeView dashboard. Bridge Builders operates that project and holds the contact details you submit in it as a processor, on behalf of the business whose form you used.

The stored lead can include your name, email, optional phone, source, topic, message, business name, order selections and estimate when applicable, submission time, and notification status. The free-form Assistant conversation is not included.

Resend delivers the initial notification. When the synchronized BridgeView inbox is active, business replies and your email responses also pass through Resend and are stored as text in the private conversation record. HTML and attachments are not retained there. Direct business email may still be held in the Google-hosted inbox. If email delivery is delayed, the durable BridgeView record remains available.

A one-way keyed hash derived from the connection address is used only to enforce submission limits and is automatically deleted after two days. We do not use it for advertising or visitor profiling.

Please don't submit passwords, full card numbers, government ID numbers, medical details, or other information we did not ask for.

5. 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.

6. 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 site runs in a Bridge Builders Vercel project dedicated to you, and we process those host logs on your behalf rather than pooling them with anyone else's. If you leave, that project transfers to an account you name.

7. Who else is involved

The provider list is short and specific.

Vercel delivers and secures the website. Supabase holds the lead, Inbox, task, Website-event, and Assistant-event stores in a Bridge Builders Supabase project, along with the authenticated BridgeView session, row-level access controls, rate limiting, and scheduled retention. Resend sends new-lead notifications and, when activated, synchronizes business email replies; Google hosts the ordinary Bridge Builders inbox.

Using the Assistant: no model provider receives the free-form chat. The bounded event metadata goes to Supabase through our same-origin server route.

If you email us directly, Porkbun forwards mail for our domain and Google holds the inbox. Ordinary invoicing, payment, accounting, or legal providers may become involved when you become a customer.

We do not sell your information to any of these providers, and none is used here for targeted advertising.

8. 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.

9. 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.

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

The accounts that could be used against you are in your name — your domain, your phone number, your payment processor, and the account your email is sent from. The website and database we run for you sit in Bridge Builders projects dedicated to you, and transfer to an account you name if you leave. We also keep the ordinary things: our emails with you, invoices, and working copies of your content while we build.

Your customers' data belongs to you. Where we hold it we hold it on your behalf, as your processor, and it comes with you if you leave.

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.

11. How long we keep it

Website and Assistant operational events are automatically deleted after 90 days. Website events contain only the bounded fields listed above; Assistant events do not contain question text, answer text, or a transcript.

Submitted lead records and synchronized Inbox message records are automatically deleted from their operational stores after 730 days. Archived Inbox threads and completed or cancelled tasks are also removed after the documented 730-day operational window. If an inquiry becomes a customer relationship, contracts, invoices, project records, and necessary correspondence may be retained separately for tax, accounting, support, and dispute-resolution obligations.

AI Receptionist call records and message content are automatically deleted from our operational store after 30 days. The voice provider stores no call audio at all: audio is processed while the call is happening and is never kept. The transcript is retained there as the record of the conversation for as long as the business is a client of ours, and when that relationship ends the transcript is provided to them and deleted from our side.

One-way rate-limit hashes are automatically deleted after two days. Supabase scheduled jobs run the deletion policy daily, and job execution records are reduced after 30 days.

We may suspend scheduled deletion where we are required to preserve records for a legal claim, investigation, or similar obligation. A suspension is recorded, applies only for as long as the obligation lasts, and scheduled deletion resumes when it ends.

You can ask us to delete an inquiry sooner, subject to records we must keep for legal or accounting reasons. Copies in ordinary email or provider backups may remain until those backup cycles expire.

12. How we protect it

We use reasonable safeguards: multi-factor authentication on provider accounts, server-only service credentials, same-origin and size validation, idempotent submissions, abuse limits, an allowlisted BridgeView owner account, Supabase row-level security, and access limited to what a job needs.

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.

13. 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.

14. 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.

15. 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.

16. 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.

One future change we already know how to treat: connecting a private RunaAI escalation service would make messages leave your browser. That would be a genuine change to this policy, and we'll make it here before we ship it, not after.