Chrome Extension Privacy Policy

The Outbound : Power Dialer extension helps you dial faster inside the CRM you already use. This policy explains exactly what the extension accesses, what it sends to Outbound, and what it never does. We aim to collect as little as possible.

Where the extension runs

The extension activates only on the sales platforms it is granted access to: salesloft.com, outreach.io, hubspot.com, salesforce.com and lightning.force.com, pipedrive.com, dynamics.com, and Zoho CRM (crm.zoho.com, crm.zoho.eu, crm.zoho.in, crm.zoho.com.au, crm.zoho.jp, crm.zoho.ca, and crmplus.zoho.com), plus app.outbound-crm.com and app.go-tarmac.com for sign-in. It does not run on, read, or track any other website you visit.

What it accesses

• Contact details on the CRM page you’re viewing (phone number, name, title, and company), only when you start a dialing session or dial a contact. Used to place or queue the call and to open research tabs.
• Your Outbound session: a sign-in cookie for app.outbound-crm.com, used to authenticate you and read your plan tier. The extension does not store your password.
• Your microphone, only during calls and recordings. When you place a call through Outbound, or record a clip in Setup, Chrome asks for microphone permission. Audio is captured only while a call or recording is in progress, never in the background.
• Your local settings (dial mode, research-tab preferences), stored in Chrome’s extension storage on your device.

What it sends to Outbound

• “Auto-dial in my CRM” mode: the extension automates your CRM’s own dialer on the page. Contact data stays in your CRM and your browser; it is not sent to Outbound.
• Outbound-dialer modes: when you choose to dial through Outbound, the contacts you queue (name, phone, title, company) are sent to Outbound’s servers to place the call and log the outcome to your workspace. Call audio travels through our telephony carrier (Telnyx) to connect the call.
• Call recordings and saved transcripts, only if your workspace turns them on: both are available on every plan that dials on an Outbound line and are off by default. A workspace owner or admin turns each one on after acknowledging a recording-law notice, and you are responsible for recording-consent compliance on every call, including in states that require the consent of all parties. When recording is on, Outbound records calls placed through its own dialer (the panel dialer or the web app) and inbound calls to your Outbound number, including ones forwarded to your mobile phone. Calls made through your CRM’s own dialer, including in “Auto-dial in my CRM” mode, are never recorded by Outbound; your CRM’s own dialer may record them under its own settings. Recordings are stored with Telnyx; Twilio, our previous voice carrier, may still hold recordings from before our move to Telnyx. They play back inside your own Outbound workspace (owners and admins: the whole team’s calls; reps: their own). Outbound staff never listen to or read your calls, including when support staff view your workspace. If an owner or admin turns on attaching recordings to your CRM, a link to the recording is placed on the CRM call record (HubSpot and Salesforce add it when the recording finishes; other CRMs get it only if the recording is ready when the call is logged). Anyone who has the link, including anyone with access to that record, can play it, and your CRM provider may then process that audio under its own terms. Turning off recording, or the attach option, disables those links.
• Model training (training contributions): this is a separate switch from recording and transcripts. For workspaces created on or after September 28, 2026, it is on by default, as described in our Terms of Service; workspaces created before that date are unaffected unless a workspace owner or admin turns it on. While it is on, the recordings and transcripts your workspace chooses to keep are used to improve Outbound’s call-detection and AI models; Outbound staff never listen to or read your calls, and training on them is automated (automated answering-machine detection learning, automated model fitting on derived measurements, and anonymous statistics) (voicemails callers leave are never contributed, and recording and transcripts stay off until you turn them on). A workspace owner or admin can turn model training off at any time in Settings or on the panel’s consent card (Setup → Call recording). Turning it off stops future calls from contributing immediately. Contributions already made are retained and may continue to be used to improve our models, including after the workspace is deleted. Only calls made while model training is on are ever contributed; turning it back on does not add calls made while it was off. If the law gives you a right to have contributed data deleted, contact us and we will handle the request as the law requires.
• Live transcription: calls through Outbound’s dialer, and inbound calls to your Outbound number, are transcribed live by Deepgram so the dialer can detect answering machines and show the transcript during the call. Live transcripts are used during the call and held only in our servers’ working memory; they are not written to disk or saved to your call history unless your workspace turns saved transcripts on. Transcripts of answered inbound calls are not saved. We opt out of Deepgram’s model improvement program on every request, so Deepgram does not use our call audio to train its models. We use an AI provider, Anthropic, only for AI features we have enabled. For workspaces that have both model training and saved transcripts on, a call’s text may be sent to Anthropic to classify whether a person or an answering machine answered; for other workspaces, call text is not sent to Anthropic for this. AI call summaries are currently limited to Outbound’s own internal workspaces. Under its commercial terms, Anthropic does not use that text to train its models.
• Voicemails: voicemails that callers leave for you, and their transcripts, are saved regardless of these settings, because the caller chooses to leave a message. The rep is notified of each one by email and, when the rep has a forwarding number and texting is active, by text message.
• Your account details, if you sign up in the panel: your name, email, and password are sent to Outbound over HTTPS to create your account. The extension itself never stores your password. If you visited our website before installing, your browser also sends the short campaign tag and the first page of our website you visited, which our website saved when you arrived. We store them with your account only to count sign-ups by campaign; they are never sent to any advertising platform. If our website also saved a Google ad click identifier, your browser may send it too; for sign-ups in the panel we ignore it and never store it.
• Voice clips you record in Setup: your voicemail-drop message and call-screen intro are uploaded to your Outbound workspace so they can play on your calls. Deepgram may transcribe each clip once so the dialer can show its text during calls. You can re-record or replace them at any time.
• Feedback you choose to send: text you type into the panel’s feedback bar (a bug report, feature request, or comment) is sent to Outbound with the panel view you sent it from. Nothing is sent unless you press Send.
• An anonymous install count. When the extension is first installed, and when it updates, it sends two values: the reason (install or update) and the extension’s version number. That is the entire payload. It carries no identifier, no account, no email, no IP-derived profile, no URL, and no page content, and it is sent without cookies, so it cannot be linked to you or to any other request. We use it only to count how many people install the extension, because the Chrome Web Store does not report that number to developers below a display threshold.

What it never does

• We do not sell or rent your data, or share it with advertisers.
• The use and transfer of information received through the extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
• We do not track your browsing outside the supported CRMs listed above.
• We do not read pages, history, passwords, or autofill data unrelated to dialing.
• We do not use analytics or advertising SDKs inside the extension, and the install count described above is not tied to any profile of you.

Permissions, and why

• activeTab / scripting: detect phone numbers and drive the dialer on the CRM tab you’re actively using.
• tabs: open LinkedIn / company-website research tabs when you dial.
• storage: remember your dial-mode and research preferences.
• sidePanel: show the dialer panel alongside your CRM.
• offscreen: hold the audio connection for calls placed through Outbound, which requires a persistent document the side panel cannot provide.
• Host access to the CRM domains and sign-in domains listed under “Where the extension runs”: the only sites the extension operates on.

Data retention

Call activity, voice clips, and feedback you create through the extension are retained in your Outbound workspace under the main Terms of Service & Privacy Policy. Install counts are stored as an anonymous total with a timestamp and version, with nothing to tie a row to a person. Local settings live on your device until you remove the extension. Removing the extension stops all access immediately.

Contact

Questions about this policy or your data: luigi@outbound-crm.com.