Your content and how we use AI

1. How we use AI

We do use AI, but only to help build what we deliver — never to train anything.

It writes first drafts. A person reviews every one before anyone else sees it — someone at Bridger, or a manager in your workspace for the drafts they start. Nothing about your content makes any AI model smarter: we do not use your material to train, fine-tune, develop or improve any model.

We would rather you checked than took our word for it, so we name every service that touches your content and link its terms below.

AI drafts four things in the Portal. A person starts each one and reviews what comes back.

• A short description of a presentation, for when its link is shared. It is drafted from that presentation’s title, goal, audience, key message and call to action, and your workspace’s name. A Bridger team member saves it; until then it exists only on their screen.
• A sample of Practice content, so you can see the shape of it before you send us anything. It is drafted from your workspace’s name, the text of up to five pages of your public website, and the model’s general knowledge of your market. The model is told not to name real customers or state their results, and customer stories are removed from the draft automatically. The draft stays hidden from your workspace until a Bridger team member releases it.
• Your Practice content: stages, plays, buyers and ramp plans. The first draft reads the links, files and decks on your workspace’s Sources list, your voice guide, and the model’s general knowledge of your market. Later additions read only new files and decks your team sends, never your website. Call recordings and transcripts, and anything your team unticks, are never read. None of it is visible to your workspace until a Bridger team member reviews it and releases it.
• Objections and customer proof, when a Sales Academy manager in your workspace asks for them. They are drafted from your plays, your voice guide and your customer stories. Proof is a summary of what customers say, in your team’s words, or a quote copied word for word from one of your customer stories: the model picks the story and never writes a customer’s words itself. Everything stays a draft that no rep sees until the manager approves it.

Before you’re a client, we draft that sample from your public website. Once your Practice content has been released, it is never drafted from your website again: the material your team sends is the only source.

Each request carries material from one workspace only. Nothing from another client’s workspace ever goes into a draft for yours. The draft that comes back is stored in your workspace and nowhere else, and we do not keep the requests we send.

The drafting is done by Anthropic’s Claude models, through Anthropic’s API.

Anthropic does not train its models on the text we send. Its commercial terms (anthropic.com/legal/commercial-terms) say so directly: “Anthropic may not train models on Customer Content from Services.” We send that text through Anthropic’s API, and Anthropic deletes API inputs and outputs within 30 days. The exceptions are Anthropic’s, not ours: if its systems flag a request as a possible violation of its usage policy, it may keep that request for up to two years, and it keeps anything the law requires it to keep. We do not have a zero-data-retention arrangement with Anthropic, so these standard terms apply to what we send.

2. Who can see your workspace

Your workspace is visible to your own team and to Bridger’s Portal team, all of whom are under written confidentiality agreements. Bridger’s access is granted at the team level rather than per client workspace.

On your side, each person sees what their role allows; your workspace owner sets the roles. On Bridger’s side, changing a workspace is limited to Bridger’s owners and administrators and to team members assigned to it as editors. No other client can see anything in your workspace: database row-level security and a workspace check on every request keep each one separate.

3. Where it is stored

The Portal’s database, application and files are all in the United States.

• The database and sign-in: Supabase, US East (North Virginia).
• The application: Vercel, Washington, D.C. Pages are delivered through Vercel’s global network.
• Files: Cloudflare R2, Eastern North America. That covers each presentation’s published files, the images and media uploaded to your workspace, files submitted through forms in a presentation, and screenshots of presentations.

A presentation’s published files are public at their address; that is how a shared link works.

Files submitted through a form are stored at a unique, unguessable address. They are not listed or indexed anywhere, and the address is generated per file. They are not individually access-controlled today.

The source of your presentations is kept in a private GitHub repository that Bridger creates for you.

4. The companies that touch your content (our subprocessors)

These are the companies that store or process your content for us, what each one does, and its terms.

• Supabase — the database and sign-in. Terms
• Vercel — hosting the application. Vercel KV holds rate-limit counters: IP addresses, no content. Terms
• Cloudflare — R2 file storage, and Browser Run, which opens a published presentation to take its thumbnail. Terms
• GitHub — the private repository that holds your presentations’ source. Terms
• Anthropic — AI drafting (section 1). Terms
• ElevenLabs — speaking the buyer’s lines in Practice aloud. It receives each line’s text and the voice to say it in, once per line; the audio is stored with us. Terms
• Resend — sending email: sign-in codes, invitations, notifications and digests. Terms
• Sentry — error monitoring. It is set not to send personal data by default. Terms
• Google — Bridger staff calendars, for Bridger’s own time tracking. None of your workspace’s content goes to Google. Terms

We will tell your workspace owner before we add a company to this list that would receive your content.

Your workspace can also send notifications to Slack, Zapier, email or a webhook. Those go wherever your workspace’s settings send them. You choose them, or we set them up at your request, so they are your destinations rather than our subprocessors.

5. How long we keep it, and deleting it

Your content is kept while your workspace exists. A record that someone ran a Practice play is deleted after 24 months.

Deleting a workspace takes two steps by a Bridger owner or administrator: archive it, then delete it. Deleting it removes the workspace’s database records — people, projects, content, Practice records and settings — its uploaded images and media, and its presentation screenshots.

Three things are removed on request rather than by the delete: your GitHub repository, your presentations’ published files, and the files submitted through your forms. Ask, and we remove them.

6. What Practice records about people

What we don’t record:

• No score, no rating and no ranking. Nothing a person does in Practice adds up to a number.
• The criteria a person ticks during a run are not stored at all.
• Self-recordings stay on the person’s own device, unless they choose to send one (below).
• Only the person grades their own answer. A manager reviews a take only when the person keeps it (below).

What we do record:

• That a person ran a play, and when. Kept 24 months.
• That the step is complete, in any learning path that includes the play. Kept while the workspace exists.
• Their own answer to “What was hardest?” on that run. Their managers see it, and so does Bridger’s Portal team.
• Their feedback on the play itself. The play’s owner sees it without their name.
• A take they keep, when their workspace shares keepers: their Sales Academy managers can hear it, and are told nothing of their own grade. It is deleted when they unkeep or replace it, when they leave the workspace, or when the workspace stops sharing keepers.
• A take they send for coaching: the coach they chose hears it for 30 days.
• A manager’s review of a kept take: Approved or Try again, with an optional note. It marks a step of their path as field ready. It is a status, not a score, and it is never ranked against anyone else.
• A take shared with the team: a manager can ask to add a kept take to What’s working or post it as a win, and it reaches the team only if the person says yes. A clip in What’s working names the person and can be seen by everyone in the workspace’s Sales Academy. It stays as the team’s record if they leave, unless they ask for it to be removed; a manager or Bridger can remove it.
• Clips a manager uploads: recordings of reps, named, shown in What’s working. The workspace is responsible for having the rep’s permission.
• Customer proof, of two kinds. A summary of what several customers say, in the workspace’s own words, which names no one and is never shown as a quote. Or a customer’s own words, which reps see once a manager adds or approves them; doing so confirms they are real and the workspace may share them. A quote can be shown without the customer’s name. AI drafts of either stay hidden from reps until a manager approves them.
• Clips a person saves: private to them. Managers don’t see what anyone saves, and nothing is counted.

7. Questions

Questions about this page, or a request to remove something: legal@bridgercreative.com.