Hivey AI — Privacy Policy

Last updated: 25 October 2026

1. Who operates this extension

Hivey AI is an open-source browser extension developed by Florian Martins. The full source code is available at github.com/FlorianMartins/HiveyAI-Sidebar.

2. Data the extension handles (all stored locally)

The following is kept only in your browser (storage.local and IndexedDB). It is never synced to any account or sent to us — we have no server to send it to:

• API keys / credentials you enter (or obtain via OpenRouter sign-in).
• Your settings (chosen provider/model, language, layout, toggles, etc.).
• Conversation history — saved by default, on this device only; you can turn it off or clear it at any time in the settings.
• Wisebase collections (your documents, their text chunks and their embedding vectors), if you create any.
• Pages you ask to watch (their address and a fingerprint of their text).
• Services you connect in the MCP tab (their address) and their sign-in tokens (OAuth access and refresh tokens, or the personal token you paste), kept apart from the settings so that an export never carries them.

2 bis. Anonymisation before a cloud provider

Requests to a local model (Ollama, LM Studio, a server on your network) or to your own gateway are sent as they are. Before a request leaves for a cloud provider — including the small side requests (titles, summaries, the suggested next request, the yes/no « does this need the web? » question) — the extension replaces sensitive values — credentials, e-mail addresses, phone numbers, IBANs, card numbers, company and VAT numbers, company names, amounts you write, and any terms you list — with markers such as ⟨EMAIL_1⟩, and puts the real values back in the answer on your device. You choose the mode in the settings or from the « Cloud » badge under the message box: Anonymised (strict or balanced — the values above leave as markers, nothing to approve), Keys masked (only credentials and passwords are hidden; before one leaves, the extension shows you where it is and you choose to mask it, always mask, never mask for this conversation, or cancel), or Not anonymised (nothing is hidden). The mapping between markers and values lives in memory on your device only and is never sent or logged. Images (screenshots) are not anonymised.

3. Page, tab and element content

When you ask for it — by adding the current page or a tab with @, turning on « The AI sees the current page » in the settings (off by default), picking tabs, capturing an area, picking an element, the right-click actions, or giving a task to the Agent — the extension reads text (and, for a captured area or a picked element, a screenshot of it) from the page so the AI can act on it. This content is included in the request to your chosen AI provider for that conversation. It is not stored by us and not sent anywhere else.

In Agent mode, the request also carries your browser's language and time zone (for example « fr-FR / Europe/Paris »), so the AI can suggest services available in your region. No precise location, GPS data or IP address is read by the extension.

Watching a page (« Watch this page », only when you ask): the extension fetches that page every 15 minutes from your browser, without your cookies, and compares a fingerprint of its text locally to notify you of a change. Nothing is sent to an AI provider for this.

4. Where your data goes

Your prompts go only to the AI provider endpoint you configured (e.g. Anthropic, OpenAI, Google Gemini, Mistral, Groq, DeepSeek, xAI, Perplexity, OpenRouter, or a local server such as Ollama / LM Studio, or your own gateway), authenticated with your key. When « Web » search is on and a question needs it, the search is made by that same provider (its web search feature). Those providers are independent third parties and process your prompts under their own privacy policies and terms. Please review the policy of whichever provider(s) you connect. We are not a party to that processing and never receive a copy.

The only other network requests, each made only when you use the feature concerned:

• Wisebase downloads its embedding model (Xenova/all-MiniLM-L6-v2, about 23 MB) once from the Hugging Face CDN; your documents are embedded in the browser and never uploaded.
• Services you connect in the MCP tab (Gmail through Zapier, Notion, Jira, Linear…): when you ask something in that tab, the AI calls their tools, so your request and the data they return (an e-mail, a page, a ticket) travel between that service, your browser and your AI provider. Reading runs by itself; anything that sends, creates, changes or deletes is shown to you and runs only if you allow it. You sign in on the service's own page (OAuth); each service processes your data under its own privacy policy.
• Artifacts (small apps the AI writes) are displayed by a static page, hivey.be/artifact-runner.html, inside an isolated frame. The artifact's code is handed to that page in the address fragment (after #), which browsers never send to the server: only the static page itself is downloaded. A React artifact also loads React and Babel from unpkg.com, inside that frame only.
• The Web tab shows the chat site you pick (Claude, ChatGPT, Gemini…) with your own session on that site; the extension does not read those conversations.
• The Hivey Code icon of the tab bar opens the Hivey Code workshop (app.hivey.be by default, configurable) in a separate tab. Only your OpenRouter key (so you do not have to enter it again) and your theme's colours are handed over, in the address fragment, which is never sent to the server; no other setting and no conversation is shared with it.
• A watched page is fetched as described in section 3.

5. What we do NOT do

• No analytics, no telemetry, no tracking pixels, no advertising IDs.
• No operator server receives your data. The extension's own code all ships inside the extension; the only things loaded from outside are the static artifact page and, for a React artifact, React/Babel — inside the artifact's isolated frame, never in the extension.
• No collection, sale, rental or sharing of your data with anyone.
• No background reading of your browsing (a page you asked to watch excepted).

6. Permissions and why they are used

• storage — save your keys, settings and history locally.
• tabs, activeTab, scripting, host access (<all_urls>) — read the page/tab/element you point at, and let the optional Agent mode act on the page you ask it to.
• identity — sign-in windows (OAuth): the optional OpenRouter sign-in, and the services you connect in the MCP tab.
• contextMenus — right-click actions (translate, summarize, improve, reply…).
• clipboardWrite — copy AI output when you ask.
• declarativeNetRequest — let the Web tab show chat sites that refuse to be framed, only in frames loaded by the extension itself.
• alarms, notifications — check the pages you asked to watch, and tell you when one of them changed.
• sidePanel (Chromium) / sidebar_action (Firefox) — display the sidebar.

7. Microphone / camera

The microphone is used only when you click the dictation button 🎤, after your browser asks for your permission. The browser's own speech recognition is used when it has one (Chrome, Edge — it may rely on the browser vendor's service); otherwise the recording is transcribed by a provider you connected (Groq or OpenAI Whisper, or an audio-capable model through OpenRouter). Nothing is recorded outside a dictation. The extension does not use your camera.

8. Children

Hivey AI is a general-purpose developer/productivity tool and is not directed at children under 13.

9. Changes to this policy

If this policy changes, the “Last updated” date above will change and the new version will be published at this URL and in the repository.

10. Contact

Questions or requests: open an issue at github.com/FlorianMartins/HiveyAI-Sidebar/issues, or email florian.martins@gmail.com.