1. What we collect

BizBee collects exactly six kinds of data. Each row below maps directly to what the code actually does, alongside the category name used in the Chrome Web Store disclosure form.

2. What we don't collect

• No ongoing collection of your browsing history. Page content is read only at the instant you press the shortcut.
• No keystroke logging. Detecting the trigger key (keydown/keyup) happens entirely locally in the browser — that detection is never transmitted.
• We never sell what we collect, or use it for advertising.
• We never use it for credit or lending decisions, or anything outside generating your reply.

3. Where generation requests go

Reply/translation generation, and the AI processing used to organize what you add to your knowledge base (extracting key facts, converting text into search embeddings, etc.), go to different places depending on your plan.

• Free trial · Lite · Pro · Max: requests pass through our server to an external generative-AI provider. The provider actually used is either Google (Gemini) or OpenAI, and which one it is can change depending on your plan and our server-side configuration. If that configuration changes, we update this document. Whichever provider is in use, bizbee does not separately store the request or response content.
• BYOK: every piece of AI processing — not just reply generation but also knowledge-base embedding and organizing — goes out through the OpenRouter API key you registered yourself. Which model handles it depends on the type of processing: reply/translation generation and knowledge-base organizing use the model you chose, but converting text into search embeddings always goes to a dedicated embedding model (OpenAI text-embedding-3-small), regardless of the model you picked — embeddings are a separate capability that chat models cannot serve. In this case the content is handled by OpenRouter and the provider of that model, not by the bizbee server.

What's sent along, in either case, is the text described as "Website content" and "Personal communications" in the table above, plus anything you've added to your knowledge base. Once it reaches a given provider, handling is governed by that provider's own privacy policy. If which providers we use changes, we'll update this section.

4. Where it's stored, and for how long

• Voice samples and settings (like your trigger key) live only in your browser's extension storage (chrome.storage.local) — never copied to anyone else's browser or to our server outside of a generation request.
• Your knowledge base (chunked text and its search embeddings) is stored in your browser's extension storage (IndexedDB), not on our server. It only passes through our server during scraping or AI processing, and isn't retained there once that's done. You can point the dashboard at a folder to keep an automatic local backup file on your own computer, and export/import to move it to another device. Removing the extension deletes the knowledge base stored on that device, so use the backup file or export if you want to keep it.
• Account email, usage record, and payment info (subscription identifier and amount charged) are stored in our server's Postgres database.
• If you signed up before August 2026 and had a knowledge base stored on our server, it's automatically moved to your device the next time you launch the extension, and the server copy is deleted.
• Profile photos uploaded to your hive avatar are stored on our server's file storage, not in the database — the database keeps only the filename.
• Whatever is stored on our server is retained until you delete it or ask us to, per section 5 — there's no separate automatic expiry. The knowledge base on your device is retained until you remove the extension or delete it from the dashboard.

5. How to delete your data

• Delete a knowledge-base document: removing a document from the dashboard deletes just that document immediately from your device's extension storage. If you've set up a backup folder, its backup file is updated too.
• Log out: signing out from the extension popup clears the session token stored on your device and invalidates any session still active on the server. Your knowledge base stays on your device after logging out.
• Delete all account data: email the contact below and we'll delete whatever's tied to your account on our server, such as your usage record. Your knowledge base lives on your device, so delete it from the dashboard or remove the extension to clear it.

6. Store privacy-practices certifications

All three of these are true:

• We do not sell the personal data we collect.
• We do not use or transfer it for any purpose beyond the single purpose of generating replies.
• We do not use it to determine creditworthiness or for lending purposes.

7. Contact

For privacy questions or to request deletion of your account data, email:
san846698@gmail.com

This document was first published on August 2, 2026. If it changes, we'll update the date shown on this page. Last updated: August 7, 2026 (refreshed facts on where generation requests go, payment info, where profile photos are stored, and the knowledge base moving from server Postgres to your device's extension storage).

Also see our Terms of Service & Refund Policy.