Privacy Policy

Effective date: August 6, 2026

AI Hub is a browser-based tool and a browser extension for chatting with multiple AI models side by side. It has no server and no backend. Everything you type, and every key you enter, stays on your own device — except for the requests your browser makes directly to the AI provider you chose.

The short version: we operate no backend, we run no analytics or telemetry, we collect no personally identifiable information, and we have no ability to see your API keys or your conversations. There is no account to create and nothing for us to store.

1. Who operates AI Hub

AI Hub ("we", "us") publishes the AI Hub website at aihubdash.com and the AI Hub browser extension. Both are distributed as static files that run entirely inside your browser.

2. We operate no server

AI Hub has no backend of any kind. There is no application server, no database, and no logging infrastructure under our control. We do not proxy, intercept, relay, or record your requests. Because no data reaches us, there is no data for us to retain, analyze, or disclose.

3. What is stored, and where

Nothing described below is ever transmitted to us. Some of it is never written to disk at all.

Data type	What it is	Where it lives
Authentication information provider API keys	The keys you enter for OpenAI, Anthropic, Google, or xAI	Held in memory only, for the current session. Never written to disk, never persisted.
Authentication information Memstore key	Your Memstore key, if you choose to connect Memstore	Persisted — `chrome.storage.local` in the extension, `localStorage` on the website. Removable with the disconnect control.
Website content	Your memory text, memory templates, saved prompt library entries, and pinned messages	Persisted in local browser storage on your device.
Website content conversations	Your prompts and the AI responses in each panel	In the extension, not persisted at all — the conversation is discarded when the popup closes. On the website it stays in the page for the session.
User activity	Panel modes, memory label, Ollama settings, saved view, workflows, theme, and the message counts and response times shown in the analytics panel	Persisted in local browser storage on your device. Never sent anywhere.

Provider API keys are not stored

The API keys you enter for OpenAI, Anthropic, Google, and xAI are authentication information, and AI Hub keeps them in memory for the duration of the session only. They are never written to disk and never persisted in any form. Closing the extension popup or refreshing the website page discards them, which is why you enter them again each session. While a session is running, a key is attached only to requests your browser sends directly to that key's own provider, so the provider can authenticate you — never to any other host, and never to us. We have no technical means of receiving them.

The Memstore key is stored

The one key AI Hub does persist is your Memstore key, because the feature would be useless if you had to paste it every session. It is written to chrome.storage.local in the browser extension, or to localStorage on the website, and it stays on your device. The disconnect control in the memory drawer deletes it.

4. Where your messages go

When you send a message, your browser makes the API request directly to the provider you selected. Your message content — website content under Google's data-type vocabulary — travels from your browser to that provider and back. It does not pass through us.

OpenAI — api.openai.com, when a ChatGPT panel is active
Anthropic — api.anthropic.com, when a Claude panel is active
Google — generativelanguage.googleapis.com, when a Gemini panel is active
xAI — api.x.ai, when a Grok panel is active
Your own local Ollama instance — http://localhost:11434, when you turn Ollama on. These requests never leave your computer.

Each provider handles the data it receives under its own privacy policy and terms. Your use of a provider through AI Hub is subject to that provider's policy, and we encourage you to read it. AI Hub contacts a provider only when you have supplied a key for it and enabled its panel. If Ollama is switched off, AI Hub makes no request to localhost at all.

5. Memstore (optional)

Memstore is a separate, optional third-party service that gives AI Hub memory that persists across sessions and devices. It is off by default and is used only if you choose to connect it with your own Memstore key.

If you connect it, conversation summaries and memory context are sent from your browser directly to memstore.dev, authenticated with your own Memstore key. That data is held in your Memstore account, not by us. Memstore's handling of that data is governed by its own privacy policy — see memstore.dev.

Auto-save is automatic: when a Memstore key is connected, a short summary of each exchange is uploaded automatically after every AI response, without further prompting. Disconnect the key to stop this.

The uploaded summary is a single short line of text: the model's name, the first 50 characters of your message, and the first 150 characters of the reply. It is sent only after a response arrives successfully. AI Hub also queries Memstore when the app launches and when you press the recall button, to retrieve memories you previously stored.

Pasted images are never uploaded to Memstore. Images you attach are sent only to the AI provider you are chatting with, as part of that request; they are held in memory while you compose the message and are never included in a Memstore summary and never written to browser storage.

If no Memstore key is connected, AI Hub makes no request to memstore.dev at all. You can stop uploads at any time using the disconnect control in the memory drawer, which deletes the stored key.

One consequence worth stating plainly: anything you type into a chat may end up in a Memstore summary. Do not paste secrets, credentials, or API keys into a conversation while Memstore is connected.

6. What we do not collect

No analytics and no telemetry of any kind.
No personally identifiable information — no names, email addresses, or account identifiers. There are no accounts.
No browsing history or web history. The extension does not request Chrome's tabs permission, so it cannot see your open tabs or the sites you visit. It can ask Chrome only whether a tab is currently open at one of four addresses — chatgpt.com, claude.ai, gemini.google.com, or grok.com — so it can focus that tab instead of opening a duplicate. That check happens locally, in the moment, and is never recorded or transmitted.
No location, health, financial, or payment information.
No keystroke logging and no monitoring of other websites you visit.

7. Selling and sharing

We do not sell, rent, trade, or share your data with third parties. We do not transfer data for advertising, credit scoring, or any purpose unrelated to AI Hub's single function. We could not do so even if we wanted to: your data never reaches us.

The only outbound transfers are the ones you initiate — to the AI provider whose panel you enabled, and to Memstore if you chose to connect it.

8. Newsletter emails

If you voluntarily submit your email address to the "Stay in the loop" form on our website, that address is sent to Memstore's newsletter endpoint and used solely to notify you about AI Hub releases. It is never sold or shared. Every message includes an unsubscribe option, and the form is entirely optional — nothing about AI Hub requires an email address.

9. Deleting your data

Because everything lives on your device, you are in full control of removing it:

Provider API keys — nothing to delete. They are discarded automatically when the popup closes or the page is refreshed.
In the app — use the disconnect and clear controls: disconnect Memstore in the memory drawer to delete the stored Memstore key, and clear a panel's history with its "clear" button.
Browser extension — removing the extension deletes its chrome.storage.local and localStorage data, including the stored Memstore key, your memory text and templates, and saved workflows.
Website — clearing your browser's site data or local storage for aihubdash.com erases the stored Memstore key, memory, templates, prompt library, pinned messages, usage stats, and preferences.
Data already sent to a provider — because we never hold it, deletion requests for data processed by OpenAI, Anthropic, Google, xAI, or Memstore must go to that company directly, under its own policy.

10. Children

AI Hub is not directed at children under 13, and we knowingly collect no data from anyone — including children — because we collect no data at all.

11. Security

AI Hub ships no remotely hosted code: the extension bundles every library it uses, so nothing is fetched from a third-party CDN at runtime. Responses are sanitized with DOMPurify before being displayed. Because your keys never leave your device, they are never exposed to a server breach on our side — there is no server to breach.

Your provider API keys are held in memory only and are gone as soon as the session ends, so there is no stored copy of them to steal. The Memstore key and your saved memory text are stored unencrypted in browser storage, as browser extensions and web apps normally do, so anyone with access to your device profile could read them; treat your device profile accordingly.

12. Changes to this policy

If this policy changes, the effective date above will be updated and the revised version will be published at this URL. Material changes will also be noted in the extension's release notes.

13. Contact

Questions about this policy or about privacy in AI Hub can be sent to:

hello@aihubdash.com

We respond to privacy inquiries as promptly as we can.