Privacy Policy

Emma is an AI sales engineer: a Chrome extension and web app that lets a sales rep ask product questions during a live call and get answers grounded in their company's own documentation. Emma is installed and configured by a company for its own sales team — the only credential involved is a shared workspace code, not a personal account or login.

Workspace binding. When a rep pastes in a workspace code, the extension stores the resolved workspace (an internal ID, company name, and domain) inchrome.storage.local, on-device. This is not sent anywhere except back to our own API to identify which workspace's knowledge to answer from.

Questions you ask Emma. The text of each question you type, and Emma's answer, are sent to our production API (emmalabs.ai) and logged server-side against your workspace, so a team can see what prospects are asking in aggregate. This log is workspace-scoped, not tied to an individual rep's identity — we don't collect names, emails, or any personal login for the extension.

Meet call presence. The extension checks whether your currently-focused browser tab's URL matches a live Google Meet call pattern (meet.google.com/xxx-xxxx-xxx), purely to show a "listening" indicator in the side panel. This is a URL-pattern check only — there is no reading of the Meet page's content, no DOM scraping, and no screen or audio capture in this check. It never leaves your device; it only changes what the side panel displays locally.

Call audio, when you turn listening on. Starting audio capture is a manual action — you click Emma's toolbar icon while on a live Meet call. When it's on, Emma captures the other call participants' audio directly from the browser tab (not your own microphone — this version does not listen to your own voice) and streams it in short real-time chunks to Deepgram, a third-party speech-to-text provider, so it can be transcribed live. We do not write this audio to disk or store it as a file; it exists only as a live stream and is discarded once transcribed.

Questions asked on the call. While listening is on, transcribed segments that look like a question are sent to our own API, which uses Anthropic's Claude to decide whether it is a question Emma should answer and to clean up transcription noise. We store the text of those questions in your workspace. That includes questions Emma answered, and questions she did not — for example commercial ones about pricing, timelines, references or contract terms — so that after the call your team has a record of everything that was asked and a follow-up list of what still needs an answer. We store the cleaned-up question text, the time it was asked, and whether Emma answered it. Where Emma answered, we also store her answer and which of your documents she used.

What we do not keep from the call. We keep questions, not conversation. We do not store a transcript of the call, we do not store the speech around a question, and we do not store audio — audio is streamed for live transcription and discarded, as described above. Utterances the filter decides are not questions at all — small talk, thinking aloud, colleagues talking to each other — are not stored.

Who can see it. Stored questions are scoped to your workspace and are never combined with, or visible to, another customer's workspace. They are readable by members of your own workspace who hold its access key, and by Emma Labs staff through an internal, credential-protected dashboard, and we use them to operate and improve the product. We do not sell them, and we do not use them for advertising.

Separately from the above, a narrowly-scoped debug log of raw candidate text remains available to us and is off by default: it can only be switched on for named individual workspaces, never for everyone at once, and doing so requires a code deployment rather than a setting someone can toggle. It is not switched on for any customer workspace. This is a diagnostic tool and is distinct from the question record described above, which is a product feature.

Security telemetry. When someone enters a wrong access key for a workspace ledger, we record that a failed attempt happened, so we can limit how many times a credential can be guessed. That record contains the workspace, the time, and a one-way keyed hash of the requesting IP address — not the address itself, which we do not store and cannot recover from the hash. It exists only to bound guessing, is kept per-day, and is never used to identify or profile anyone.

• No audio or video recordings saved as a file, ever — call audio is streamed for live transcription only (see below) and discarded once transcribed.
• No capture of your own microphone in this version — only the other call participants' audio from the shared tab.
• No browsing history outside Google Meet call tabs — the extension cannot see the URL of any other tab.
• No DOM content, chat, or participant data from your Meet call.
• No advertising identifiers, analytics trackers, or third-party pixels.
• No personal login — the workspace code is a shared team credential, not tied to you individually.

This is live, not upcoming: when you turn on listening (see "What we collect" above), Emma's extension requests Chrome's tabCapturepermission for your current Meet tab only, and streams the other participants' audio to Deepgram for real-time transcription. Our commitment: audio is never written to disk or stored as a recording by us, and it is discarded once transcribed. Transcribed text that looks like a question is then checked against our own API (using Anthropic's Claude) before any card appears — see "Detected question text" above for what that step does and what we do and do not log.

The extension's own API lives at exactly one destination: https://emmalabs.ai, hosted on Vercel. From there, two third-party processors are used, only for the purposes described above: Deepgram (live speech-to-text on call audio, while listening is on) and Anthropic's Claude API (answering typed/detected questions from your company's compiled documentation, and classifying detected candidates). No third-party sale of data, no data brokers, no ad networks.

Questions, answers, and the documents Emma was trained on are retained for as long as your workspace exists, so your team can review what prospects are asking. We do not currently apply a shorter automatic expiry, and we would rather say so plainly than publish a period we do not enforce.

Deleting a workspace deletes its stored data — every question, every answer, and every compiled document held under that workspace — and there is no undo. To delete a workspace, to request a copy of what is stored for you, or to ask any question about it, email us at the address below and we will action it.

• storage — to remember your workspace binding and mute state on-device.
• sidePanel — to show the Emma panel next to your browser window.
• tabCapture — to capture the other call participants' audio directly from a live Meet tab so Emma can detect spoken questions. This only activates when you click Emma's toolbar icon on that tab (Chrome requires this direct action before the permission can be used) — it cannot capture any other tab's audio.
• offscreen — Chrome's Manifest V3 requires audio processing to happen in a hidden offscreen document rather than the extension's background script; this is an internal processing detail, not an additional data source.
• activeTab — confirms Emma was directly invoked on your current tab (by clicking its toolbar icon), which is what makes the tabCapture permission usable for that tab, per Chrome's own security model. It does not grant access to any other tab.
• Host access to meet.google.com — scoped narrowly so the extension can tell when your focused tab is a live Meet call, for the presence indicator described above. No other site's tab URL is visible to this extension.
• Host access to emmalabs.ai — the only server this extension ever talks to.

Questions about this policy or your data: emma.sebuild@gmail.com.