Turn conversations into clear notes — privately

Scribefy is a “bring your own key” (BYOK) Chrome extension. We do not run a server that sees, stores, or processes your audio, transcripts, or notes.

• Your audio and transcripts go directly from your browser to the AI provider whose API key you entered (Deepgram, OpenAI, Google, Anthropic, OpenRouter).
• Your settings, API keys, and meeting history are stored locally in your own browser (chrome.storage.local) — they are never uploaded to us.
• There is no Scribefy account, no Scribefy login, and no Scribefy backend in the middle of your data.
• Nothing “joins” your meeting. Capture happens locally in your browser.

Because Scribefy has no server component, we (the developers) cannot read your conversations even if we wanted to. Your privacy posture is governed by your own browser and by the AI provider you choose.

“Scribefy”, “we”, “us”, and “our” refer to the developers and publisher of the Scribefy Chrome extension. “You” refers to the person who installs and uses the extension.

This policy explains what data the extension touches, where that data goes, how long it lives, and the controls you have over it.

The extension handles the following categories of data. Read carefully which ones stay on your device and which ones leave it (and to whom).

Scribefy is a client that talks to AI providers using your keys. The moment your audio or transcript reaches one of these providers, that provider’s own privacy policy and data-retention terms apply — not Scribefy’s.

Providers the extension can connect to (only the ones you configure are used):

You are responsible for reviewing and agreeing to the terms and privacy policy of each provider whose key you use, including:

• Whether that provider retains your inputs/outputs, and for how long.
• Whether that provider may use your data to train or improve models (this differs between consumer and business/API tiers — check your account).
• The billing, geographic, and compliance terms of your own account.

Scribefy has no visibility into and no control over what these providers do with the data you send them through your own account.

Because your data lives in your own browser, you are the primary administrator of it. Here is exactly how to view, manage, and delete each piece.

5.1 Where your data lives

All Scribefy data is held in chrome.storage.local for the extension. This is per-browser-profile storage on the device where you installed the extension. It is not part of Chrome Sync under Scribefy’s control, so it does not roam to your other devices via Scribefy.

5.2 Viewing your data

• Meeting history (transcripts, summaries, action items) is viewable inside the extension UI under your sessions / history.
• Settings and configured providers are viewable in the Settings screen.

5.3 Editing / updating your data

• Change providers, models, languages, or API keys at any time in Settings. Saving overwrites the previous values in local storage.
• Replacing an API key removes the old one from storage.

5.4 Deleting your data

You can remove your data at any time, and deletion is permanent:

• Delete a single session from your meeting history in the extension UI.
• Clear all meeting history from the extension UI (if a “clear history” control is provided in your version).
• Remove an API key by clearing the field in Settings and saving.
• Remove everything the extension stored by uninstalling the extension — Chrome clears the extension’s local storage on removal. You can also use Chrome’s “Clear browsing data” / per-site and per-extension storage tools.

Note: Deleting data inside Scribefy only affects the copy stored in your browser. It does not delete copies that an AI provider may have retained on their systems. To delete data held by a provider, use that provider’s own account dashboard, data controls, or support process.

5.5 Data retention

• Scribefy keeps your local data until you delete it or uninstall the extension. There is no automatic expiry and no server-side retention by us (because we have no server).
• Raw audio is held only transiently in memory during an active session and is not persisted by Scribefy after the session ends.

5.6 Data portability

Your notes are plain text/structured data stored locally. Where the UI offers copy or export, you can move your transcripts and summaries out of the extension. (Export integrations such as Google Docs and Notion are on the roadmap; when added, exporting will send the selected content directly to that destination using credentials you authorize.)

Scribefy requests the minimum permissions needed to record and process audio.

• tabCapture / desktopCapture / offscreen — Capture audio from a browser tab (active or running in the background) or your system/desktop audio, and combine it with microphone input. The offscreen document is used for audio processing that a Manifest V3 service worker cannot do directly.
• activeTab / tabs — Detect the meeting page you are on (Google Meet, Zoom, Teams) so the extension can integrate with it.
• storage — Save your settings, API keys, and meeting history locally in your browser.
• windows — Manage the extension’s UI surfaces (popup, side panel, options page).

Host access is limited to:

• Meeting platforms: meet.google.com, *.zoom.us, teams.microsoft.com
• AI provider APIs you use: Deepgram, OpenAI, Google, Anthropic, OpenRouter

The microphone is accessed only when you start a session that includes mic capture, and the browser will prompt you for microphone permission separately.

You are responsible for using Scribefy lawfully. Recording, transcribing, and storing conversations may be regulated where you live or where the other participants are located. Some jurisdictions require the consent of one party, all parties, or prior notice before a conversation may be recorded.

Before recording, make sure you have any consent required by law and by the meeting platform’s own terms. Scribefy provides a tool; it does not provide legal advice, and you assume responsibility for how you use it.

• No middle-man server: there is no Scribefy backend that could be breached to expose your conversations, because your data never reaches us.
• In transit: connections to meeting platforms and AI providers use HTTPS/WSS (encrypted transport).
• At rest: your data sits in your browser’s local extension storage. This is isolated to the extension within your browser profile, but it is not an encrypted secrets vault and is not protected by a separate passphrase. Anyone with access to your unlocked operating-system user account and browser profile could read it.
• Your responsibilities: protect your device with OS login, disk encryption, and a secure browser profile; do not install the extension on shared or untrusted machines if you store sensitive conversations or API keys; rotate or revoke a provider API key promptly if you believe it has been exposed.

Scribefy is not directed to children and is intended for general/professional use. We do not knowingly collect data from children.

Depending on where you live, you may have rights to access, correct, delete, port, or restrict processing of your personal data.

Because Scribefy stores your data locally and operates with no server-side collection, you can exercise most of these rights yourself, directly and immediately, using the controls in Section 5 (view, edit, delete, uninstall).

For data that an AI provider has retained, exercise your rights through that provider, who is the controller/processor for the data you sent to them under your own account.

We do not sell your personal information, and we do not share it for cross-context behavioral advertising.

We may update this policy as the extension evolves (for example, when export, translation, or chat-over-history features ship). Material changes will be reflected by updating the “Last updated” date above and, where appropriate, in the extension’s store listing or release notes. Continued use after an update means you accept the revised policy.

Questions about this policy or your data can be directed to the Scribefy developers via the support contact listed on the extension’s store page.