In short
  • EZGPT.APP has no account, no analytics and no telemetry.
  • Everything you store stays in your browser. Nothing is uploaded to us, because there is no "us" server.
  • The only network requests go to the model servers you add yourself, when you send a message, discover models or test a connection.
  • Page text is read only when you click "Attach page" or use the context menu on a selection.

What the extension stores, and where

DataWhereWhy
Provider settings: name, server URL, optional API key, system prompt, context windowchrome.storage.local on your deviceTo send your messages to the server you chose
Chats and messages, including any page text you attachedchrome.storage.localChat history
Images you attachIndexedDB in your browser profileTo show them in the chat and send them to vision models
Prompt snippets and appearance settingschrome.storage.localYour preferences

None of this is synced through your Google or Microsoft account. Uninstalling the extension deletes it. You can also delete chats, or reset everything, from Settings → Data.

What is sent, and to whom

When you send a message, EZGPT.APP sends the conversation (the messages in that chat, the system prompt for that provider, any attached images or page text, and your chosen parameters) to the server URL of the provider you selected. If you entered an API key for that provider it is sent as an Authorization header to that server only.

When you click "Discover models" or "Test connection" the extension calls that server's models or chat endpoint once.

If that server is a cloud service such as OpenAI, OpenRouter, Anthropic or Google, that service's own privacy policy governs what happens to the data you send it. If it is LM Studio, Ollama or another server on your machine or LAN, the data never leaves your network.

Page content

The extension can read the text of the page you are looking at, but only in two situations: when you click "Attach page" in the panel, or when you right-click selected text and choose "Ask EZGPT.APP about…". Where the extension already has access to that site, the browser asks about that one site the first time. On a fresh install it cannot see which site you are on until you allow it, so it reads the page under the one-off access your own click grants, and if that is refused it shows you a short explanation before the browser asks for access to all sites. You can decline, and page attach simply will not work. The text becomes part of your message and is stored with the chat like any other message. The extension never reads pages in the background.

Permissions

storage, unlimitedStorage keep your settings and chats locally. sidePanel shows the chat in the side panel. activeTab and scripting read the page only after you ask. contextMenus adds the "Ask EZGPT.APP about…" item. Access to a server address is requested for that one address when you add a provider. Access for reading pages is requested for the one site when the extension can see which site you are on, and otherwise, once, for all sites after it has explained why. You can revoke any of it at any time from the extension's details page in your browser.

Analytics, tracking and third parties

There are none. The extension contains no analytics library, no crash reporter, no advertising and no remote code. Fonts are bundled with the extension, so no font requests are made either.

Backups you export

Settings → Data can export a backup file. It contains your settings, providers, snippets, chats and images. API keys are left out unless you tick "Include API keys". The file is saved by your browser; the extension does not send it anywhere.

Changes

If this policy changes, the new version ships with the extension update and the effective date above is updated.

Contact

Questions about privacy or the extension: use the report form at ezgpt.app/report-issues.html, which is also the support link on the Chrome Web Store listing.