Privacy

Privacy policy

Last updated: 23 September 2026

AnyChat has no server, no analytics, no telemetry, and no account. Nothing you type is sent to us, because there is no “us” to send it to. This document exists because the Chrome Web Store requires a posted privacy policy from every extension that handles user data, including extensions that only ever store it on your own machine.

What AnyChat does with your data

Ollama sends messages to the server address you configure, which may be on this computer or another machine. With Web search enabled in Ollama settings, Ollama may also send search queries to its online search service. Search is on by default and can be disabled in Ollama settings.

Data	Where it goes	Where it is kept
The message you type	The provider you selected, by being typed into their composer	Browser session storage as a draft, so closing the popup does not lose it
Your preferences — default provider, surface, provider order	Nowhere	`chrome.storage.local`, on your machine
Prompt templates you write	Included in the message when you use one	`chrome.storage.local`, on your machine
Page text, when you attach a page	The provider, as part of that message	Held in memory for that one send, then discarded
A screenshot, when you take one	The provider, as part of that message	Held in memory for that one send, then discarded
Tab titles and URLs, if you grant tab access	Used to build `@mentions`; the referenced page’s text is included in the message when you mention it	Not stored
Your browsing history, if you turn on new tab suggestions	Nowhere. It is matched against what you are typing inside the page itself	Not stored — read for that keystroke and discarded
The last six things you asked through AnyChat — what you typed, including the name and hostname of any template or tab you referenced in it — and the link to each conversation	Nowhere. They are drawn as cards on your new tab, and clicking one opens that conversation at the provider	`chrome.storage.local`, on your machine. Settings → New tab → Clear recent chats empties it
A message you send to Ollama, including attached context and the response	The configured Ollama server; enabled Web search may also send queries to Ollama’s online search service	Chat history in `chrome.storage.local` on this device. Delete individual conversations from Ollama’s History menu. Server-side retention is controlled by the server
Why you uninstalled, if you choose to say	A Google Form, if you submit it	Not kept by AnyChat, which no longer exists by then. Chrome opens the form after the extension is gone. Nothing is attached to the link — no identifier, no version, no install date — and closing the tab sends nothing
How many messages you have sent, on which days, and which services you have used	Nowhere	`chrome.storage.local`, on your machine. Counts, dates and up to four provider names — never a message, a link, or anything from a page. It exists so AnyChat can tell whether it has been useful enough to be worth asking you for a Web Store review, and so a “no” only has to be given once. Settings → About → Don’t show again ends it

What AnyChat never does

No collection. Nothing is transmitted to any server operated by this project. There are none. The one thing that leaves your machine at our request is not automatic and is not ours: uninstalling opens a feedback form, and only what you choose to type into it and submit reaches anybody. Named here rather than left to be discovered — a third-party page opening on the way out would read badly next to the sentence above.
No keystroke forwarding. What you type in the new tab’s box is never sent to a suggestion service. Suggestions are built from your own history, locally, or not at all.
No analytics, telemetry, crash reporting, or advertising. None are sent by the extension. AnyChat does keep the small on-device tally described in the last row above — how much you have used it, so it knows whether asking you for a review would be reasonable. It is not analytics: it is never sent anywhere, there is nowhere for it to be sent, and nothing about your usage is knowable to this project from it or from anything else.
No reading of your credentials. AnyChat never reads, copies, or stores cookies, authentication tokens, or session keys from any provider. It relies on the browser to carry your existing session, exactly as it does when you visit the site yourself.
No selling or unrelated sharing. AnyChat does not sell data. It sends content only to the provider you choose, the Ollama server you configure, and (when enabled) Ollama’s online search service as described above.
No history of the pages you visit. The recent-chat cards on the new tab keep the conversations you started through AnyChat — its own output, so you can get back to one — and nothing else. Tab titles and URLs from your browsing are still never written down: @mentions read your open tabs live, and new tab suggestions match against your history for one keystroke and discard it. A card is labelled with what you typed, never with the message that was composed from it. The line is: a card may name what you pointed AnyChat at, and never what that page said. So a card can carry “Explain” and the name of the tab or page you aimed it at — those are words you put in your own sentence — along with that page’s hostname, which is the same fact in a form a favicon can be looked up from, so the card draws the mention with the site’s own icon and colour. The page’s text, the passage you selected and the composed message stay out. A send with nothing typed at all, such as an attached page on its own, records no card rather than a card made out of that page.

Permissions, and why each exists

storage — keeps your preferences, prompt templates, the current draft, the last six chats you started, and the usage tally in the table above, on your machine.
sidePanel — renders the chosen provider in Chrome’s side panel.
declarativeNetRequestWithHostAccess — removes framing-related response headers on the chat domains listed below, and only there, so those pages can be displayed inside AnyChat’s own panel. The rules are static and apply to sub-frame requests only.
activeTab and scripting — read the current page’s text, only when you press the attach control or the keyboard shortcut. Access is granted by that gesture and does not persist.
favicon — shows a site’s own icon next to an @mention.
search — hands a query you typed on the new tab page to the search engine you have already configured in Chrome. AnyChat cannot read which engine that is, and does not change it.
tabs (optional, requested from onboarding or when you first use @mentions) — lists your open tabs so you can reference one by name.
history and topSites (optional, requested from onboarding or when you turn on “Suggest from your history” in Settings) — match what you type in the new tab’s box against pages you have already visited, so it can offer them. The matching happens in that page, on your machine. Nothing is sent anywhere: there is no third-party suggestion service in the path, and there could not be one, because Chrome does not tell an extension which search engine you use. Turning the switch off hands both permissions straight back, and neither is on the install prompt.
Host access to the chat domains — lets AnyChat type your message into the provider’s composer.
Access to the sites you visit (optional, and off until granted) — one grant shared by the selection bubble, the handle on the right edge, and open-tab references. Chrome asks when you enable one of these features and releases the grant when none still needs it. The bubble reads a selection only when you press one of its controls; the handle reads nothing; a referenced tab’s text is read when you attach it to a message. None of that text is stored or sent to this project.
file:///* — lets the composer open on a local file you have opened in a tab — a saved page, an exported document — the same way it opens on a website. Chrome does not grant this on install. It stays off until you switch on Allow access to file URLs on AnyChat’s entry in chrome://extensions, and until you do, AnyChat cannot see a local file at all. With it on, a local page is read on exactly the same terms as any other: only when you press attach, only the page you are looking at, and only for that one message. AnyChat has no access to your file system — it cannot list a folder, open a file you have not opened, or search your disk. It can read a document you have already opened yourself, and nothing else.

Standing host access is limited to the services AnyChat sends to: chatgpt.com, claude.ai, chat.deepseek.com, gemini.google.com, grok.com, perplexity.ai, copilot.microsoft.com, copilot.com, m365.cloud.microsoft, meta.ai, chat.mistral.ai, and openrouter.ai — plus local files, on the terms above, if you are the one who switches that on.

Your data at the providers

Once your message reaches ChatGPT, Claude, DeepSeek, Gemini, Grok, Perplexity, Copilot, Microsoft 365 Copilot, Meta AI, Mistral or OpenRouter, that provider’s own privacy policy governs it, exactly as though you had typed it on their site — because that is what happened. AnyChat is not affiliated with any of them.

Removing your data

Uninstalling AnyChat removes everything it stored, because everything it stored was in your browser. Short of that, Settings clears each store on its own: prompt templates from the Prompts page, and the new tab’s recent chats from the New tab card. Conversations already sent live in your account with the provider, and are removed there.

One page opens when you uninstall. Chrome is asked to open a Google Form (forms.gle) so there is somewhere to say why you left — the only channel that reaches anyone after the extension is gone. Nothing is appended to that address: no identifier, no version, no install date, nothing about how you used AnyChat. What arrives is what you choose to type, and closing the tab without typing sends nothing at all. The uninstall has already finished by the time the page opens, so nothing about removing AnyChat depends on answering. Google’s privacy policy governs the form, as it would any other page.

Changes

Material changes to this policy will be reflected here, with the date above updated.

Contact

Questions about this policy, or about anything AnyChat does with your data, can be sent to anychatsupport@gmail.com.