Bridge AI

Privacy Policy

Last updated: 14 September 2026

This Privacy Policy explains how Bridge AI Talent (“Bridge AI Talent”, “we”, “us”) collects, uses, stores, shares and protects information when you use the Bridge AI operating system (the “OS”), including any Google account you choose to connect to it. If you do not agree with this policy, do not connect your account or use the OS.

1. Who we are

The OS is operated by Bridge AI Talent. It is a lead-generation and client-workflow platform used by independent experts and their operators to research prospects, prepare and send outreach, schedule calls, and manage replies. You can reach us about privacy at leonard@bridgeaimena.com.

2. Google data we access

When you connect a Google account, you grant the OS access to the following Google data through Google's official OAuth flow. We request the narrowest scopes needed to provide the features you use:

• Gmail, send (gmail.send): to send outreach and follow-up emails from your account, only when you or your operator explicitly trigger a send.
• Google Calendar events (calendar.events): to read your existing events to find free time, and to create or update events when a prospect books a discovery or debrief call with you.
• Google Calendar events, read only, from the Bridge Recorder app (calendar.events.readonly): if you connect a Google account inside the Bridge Recorder desktop app, the app reads your upcoming events to show what is coming up and to name a recording after the call it belongs to. It never creates, changes or deletes events.
• Basic account identity (your Google account email address and, where provided, your name; userinfo.email in the Bridge Recorder app): to identify the connected account and associate it with your workspace or your computer.

3. Why we access it and how it is used

We use Google data only to provide and improve the specific features you use in the OS:

• Sending your outreach and follow-up emails when you initiate them.
• Drafting suggested replies from CRM fields, assessments, notes, transcripts, and manual context that you review, edit and approve before anything is sent.
• Applying manual writing style instructions or samples that you provide.
• Reading your calendar availability and creating booking events for discovery and debrief calls.
• Showing your upcoming calls in Bridge Recorder and, when you ask it to, sending a note's share link or a team invitation from your Gmail.

We do not use Google data for advertising, we do not sell it, and we do not use it to build independent profiles of you for any purpose unrelated to the features above.

4. AI processing of your content

To provide the features above, the OS sends relevant assessment, note, transcript, CRM, manually provided, and calendar content to third-party AI providers (currently Anthropic, accessed through OpenRouter, and an embeddings provider used to match similar content). This happens, for example, when the OS creates a brief or drafts a suggested reply.

This content is sent to these providers solely to generate the output of the feature you requested. Under those providers' API terms, your content is not used to train their generalized AI models. We do not transfer your Google data to any AI provider for any purpose other than providing you the requested feature.

5. Bridge Recorder, the call recording app

Bridge Recorder is a desktop application for macOS and Windows that records calls you choose to record and turns them into a transcript and notes. It is built so that the audio never leaves your control and so that you can see, at every step, what stays on your computer and what reaches your workspace.

• Recording is always your action. Nothing joins your call and nothing records on its own. You press Record, or you switch on “Start a note automatically” in the app's settings, in which case a recording starts when a call app is detected and a visible indicator shows while it runs. You are responsible for telling the other participants and for obtaining any consent that the laws applying to you and to them require.
• What is captured. Your microphone and the audio your computer plays during the recording (the other side of the call), kept as two channels so the transcript can tell your words from theirs. The app does not capture your screen, your keyboard, or anything outside the recording.
• Audio stays on your computer. The recording file is written only to a folder on your computer. Bridge never receives, stores or listens to the audio. To produce the transcript, the audio is streamed to Deepgram, our speech-to-text provider (or to your own Deepgram account if you entered your own key in the app), and, when “Re-check after the call” is on, the recording is sent to Deepgram once more for a higher quality pass. Deepgram processes the audio only to return the text; its own privacy terms apply to that processing. With “Keep audio and transcript on this computer” switched off, the audio file is deleted from your computer as soon as the transcript has reached your workspace.
• What reaches your workspace. When the app is connected to a Bridge workspace, it sends the transcript text, the title, the time and duration, the name of the call app, the participants (taken from your calendar event when you started the note from one), the folder and the notes you typed yourself. This is stored in our managed database (Section 8) and indexed for search, including as numerical embeddings. AI notes, summaries, translations and answers to your questions are produced from that text by the AI providers described in Section 4. Without a workspace (using only your own Deepgram key), nothing reaches Bridge: the transcript and your notes stay on your computer.
• Calendar. “Coming up” reads events from the Google Calendar connected to your workspace or, if you connect a Google account inside the app, directly from Google with read only access (Section 2). In that case the app keeps the Google token on your computer only, never sends it to Bridge, and you can disconnect from the app's settings or at myaccount.google.com/permissions.
• Sharing is yours to decide. A note is private to your workspace until you share it: a share link lets anyone holding the link read the notes and transcript until you turn the link off; a team sees a note only when you share that note in the team; API keys, the MCP server and webhooks send your notes to the tools and endpoints you register yourself, with keys you create and can revoke at any time.
• Deleting. Deleting a note in the app deletes the audio and transcript from your computer and removes the note from your workspace and from search at once; the database record is purged within 30 days and then expires from encrypted backups. Disconnecting a computer in Bridge (Integrations, Bridge Recorder) revokes its key immediately.
• Permissions. macOS asks for Microphone and Screen & System Audio Recording; Windows asks for Microphone. The app uses them only while a recording runs.

6. Anonymous website activity

Tenant websites that use the Bridge SDK may record first-party anonymous activity such as a page view, active viewing time, a link or button label and destination, reaching a Book a call section, or clicking its call-to-action. The event contains the page path without its query string, page title, referrer without its query string, time, and a random session id held only in the current browser tab's session storage. Activity events do not contain your name, email address, raw IP address, cookie, device fingerprint, or user-agent string. A visitor becomes known to the OS only after explicitly submitting a form or making a booking.

7. Product analytics and session replay

We use PostHog and Contentsquare to understand feature usage, diagnose errors, and improve the OS. Tenant users are represented by an opaque identifier rather than their email address. Assessment invitation tokens and full URL query strings are not sent to analytics. Session replay masks form inputs and text in CRM, inbox, and assessment surfaces, and automatic click capture is restricted to explicitly tracked controls. You may request deletion of analytics data by contacting us at the address above.

8. How your data is stored and retained

We store the OAuth tokens needed to keep your account connected, and we cache or index the specific message and calendar content required to provide the features (for example, the text of a reply so we can classify and display it). This data is stored in our managed database (hosted with reputable infrastructure providers such as Neon and Vercel) and is retained only while your account is connected and the data is needed for the feature. Call transcripts and notes from Bridge Recorder are retained in your workspace until you delete them (Section 5). When you disconnect your Google account, or on request, we delete the stored Google-derived content and revoke the stored tokens.

When you send product feedback, any screenshot, voice note, or screen recording you choose to attach is stored with the feedback ticket in our managed database so our team can investigate the issue. These attachments may contain information visible on your screen, so include only what is needed. They are retained while the ticket is active. After the ticket is deleted, the attachment is removed through our 30-day deletion process. During that period it may also remain in encrypted database backups or recovery branches and expires with those copies.

9. Sharing with third parties

We share data only with the service providers that operate the OS on our behalf, under agreements that limit their use of the data to providing their service to us. These include our hosting and database providers (e.g. Vercel, Neon), the AI providers described in Section 4 (Anthropic via OpenRouter, and an embeddings provider), the speech-to-text provider used by Bridge Recorder (Deepgram, audio only, Section 5), and, where you use those features, providers unrelated to your Google data such as LinkedIn automation (Unipile) and public web research (Apify). We may also disclose data if required by law. We never sell your data or share Google user data for advertising.

10. Disconnecting Google and deleting your data

You can remove our access to your Google account at any time in either of two ways:

• Inside the OS, use the “Disconnect” control on your Google connection. This revokes the stored tokens.
• In your Google account, visit myaccount.google.com/permissions and remove access for this application.

To request deletion of the Google-derived data we hold about you, email leonard@bridgeaimena.com. We will delete the stored Google user data within 30 days of a verified request, except where we are required to retain it by law.

11. Security

We protect your data with industry-standard measures: all traffic is encrypted in transit with TLS/HTTPS; OAuth tokens are stored server-side and are never exposed to the browser; access to production data is restricted to authorized personnel; and we request the least-privilege Google scopes needed for the features you use. We never ask for or store your Google password, connection is by OAuth only.

12. Compliance with the Google API Services User Data Policy

The OS's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular, we use Google user data only to provide or improve the user-facing features described here; we do not transfer it except as needed to provide those features, to comply with applicable law, or as part of a merger or acquisition; we do not use it for advertising; and we do not allow humans to read it except with your explicit consent for a specific message, where necessary for security or to comply with the law, or on data that has been aggregated and anonymized.

13. Changes to this policy

We may update this policy from time to time. When we do, we will change the “Last updated” date above and, for material changes, take reasonable steps to notify you.

14. Contact

Questions about this policy or your data can be sent to leonard@bridgeaimena.com.

Terms of Service