Privacy Policy

Amie Chrome Extension  ·  Last updated: June 2026

Who we are

Amie is a Chrome extension that provides a private AI assistant powered by Gemini Nano, Chrome's on-device AI model. This policy explains what data Amie accesses and how it is handled.

Data Amie accesses

To provide its features, Amie may access:

• Page content — the text of the current web page, when you use the "Summarise this page" or related context menu actions.
• Selected text — text you have highlighted on a page, when you invoke a context menu action on it.
• Your chat messages — the messages you type into Amie's chat interface.
• Microphone audio — only while voice mode is active. Audio is transcribed locally and the audio buffer is discarded after transcription. See the Voice mode section below.
• Attached images — images you paste, drag, or upload into a chat for multimodal conversation.
• Screenshots you capture — when you use the "Discuss this view" or "Discuss a region" context menu actions, Amie captures the visible tab so you can discuss it with the model.
• Preferences — your chosen response style (Focused, Balanced, or Creative), colour theme, appearance (light/dark/auto), selected voice, voice volume/speed/pitch, "always speak responses" setting, and follow-up suggestions setting.
• Conversation history — your chats, both the messages visible in the side panel and the full raw transcript kept in local storage so that search and recall work across chats.
• Memories you pin — replies you explicitly mark with the bookmark icon. Pinned memories apply across all chats so Amie can reference them in future conversations.
• Auto-generated profile facts — when you mention durable facts about yourself in conversation ("I'm a vegetarian", "I work as a designer"), Amie may extract these and store them locally as a short profile so future replies can take them into account. Right-click actions (Translate, Summarise, Explain, Fix grammar) are excluded from this extraction — text you ask Amie to process is never mined as personal facts. You can review and edit these facts at any time in Settings → Memory, or turn the feature off entirely.
• Auto-generated summaries — when a chat becomes long enough that older turns can't fit in the model's context window, Amie creates a short summary of the older content locally and uses it in place of the raw turns. These summaries are stored on your device alongside your chats.

How that data is used

All data listed above is passed directly to Gemini Nano (or to Chrome's other on-device AI APIs described below), which run entirely on your device inside Chrome. It is used solely to generate AI responses within the extension.

None of this data is:

• Sent to Amie's developer or any third party
• Stored on any external server
• Used for advertising, analytics, or profiling
• Shared with data brokers or resellers

Network access

Amie's manifest sets a Content Security Policy of connect-src 'none', which means the browser itself blocks the extension from making any network requests — to Amie's developer, to Google, or to any other server. This is a guarantee enforced by Chrome, not by the extension's own code.

The only network activity associated with Amie is the one-time download of Chrome's built-in AI model files (Gemini Nano, and translation language packs when you first use a new language pair), performed by Chrome itself when you first use a Chrome built-in AI feature. After the model files are on your device, no further network traffic is required.

Voice mode (speaking with Amie)

Voice mode lets you have a spoken conversation with Amie. When you start a voice call:

• Amie requests access to your microphone via the browser's standard permission prompt. You can deny this at any time and the rest of the extension continues to work.
• While the call is active, Amie listens for your voice and uses Chrome's on-device speech model (the Prompt API's audio input) to transcribe what you say. The transcription happens locally.
• The audio buffer used for transcription is discarded as soon as the text is produced. Amie does not store recordings of your voice.
• Replies are spoken back to you using your operating system's built-in voices (see "Voice output" below).

Voice output (text-to-speech)

When you ask Amie to read a reply aloud, or enable "Always speak responses", Amie uses your operating system's built-in voices via the browser's Web Speech API. Amie filters this list to on-device voices only — voices that synthesise audio locally on your machine. Network-backed voices that some operating systems also expose are intentionally excluded so that the text being read never leaves your device.

Images and screenshots

Amie supports two ways to bring images into a conversation:

• Attachments you provide — images you paste, drag, or upload via the composer's attach button.
• Screenshots you capture — when you use the right-click "Discuss this view" or "Discuss a region" actions, Amie captures the visible browser tab so the model can see what you're looking at.

Both go to Gemini Nano's on-device multimodal session for analysis. Captured images are stored locally in IndexedDB so the chat continues to show them on reload, and they are removed when the chat (or the extension itself) is deleted. Images are never sent off the device.

Local storage

Amie keeps all of its data on your own device using two browser-provided storage mechanisms:

• chrome.storage.local — your preferences, the list of chats you've started, the visible message history of each chat, and your pinned-chat selection.
• IndexedDB (database name amie_memory) — the full raw message archive used for search, the auto-generated summaries described above, your pinned memories, your profile facts, and any images attached to or captured into chats.

Both stores live entirely on your device. None of this data ever leaves your computer, and all of it is removed when you uninstall the extension. You can also manage and delete this data at any time from Settings → Memory and Settings → Storage inside the extension.

Chrome's built-in AI APIs

AI processing is performed by Chrome's built-in AI APIs, which run locally on your device and do not require an internet connection to function:

• Prompt API (Gemini Nano) — powers text chat, voice mode transcription, and image / screenshot analysis.
• Summarizer API — generates page and selection summaries and is used internally to compress long conversations.
• Translator API — used by the "Translate" context menu action to translate selected text into English on your device.
• Language Detector API — identifies the source language of selected text so the Translator can pair it with the right translation model.

All four are part of Chrome and operate fully on-device. For information about how Google handles these built-in AI features, refer to Google's Privacy Policy.

Permissions

Amie requests the following Chrome permissions, each used only for the purpose described:

• sidePanel — to display the chat interface in Chrome's side panel.
• storage — to save your preferences, chats, memories, profile facts, and summaries locally on your device.
• activeTab — to access the current tab's content when you explicitly request a summary, a translation, or capture a view. Amie never reads tabs you haven't acted on.
• scripting — to extract the readable text of a page when you request a summary or use a context menu action.
• contextMenus — to provide right-click actions such as "Summarise this page", "Summarise selection", "Explain in simple terms", "Fix grammar", "Translate", "Discuss this view", and "Discuss a region".
• offscreen — to host the microphone permission prompt for voice mode. Chrome's side panel can't directly hold a microphone grant, so a small hidden document does it on behalf of voice mode. The offscreen document is created only when voice mode is active.

Amie does not request host_permissions or any "all sites" access. The extension can only read a page's contents at the moment you act on it from the side panel or right-click menu.

Children's privacy

Amie is not directed at children under the age of 13 and does not knowingly collect any information from them.

Changes to this policy

If this policy changes, the updated version will be published at this URL with a revised date. Continued use of Amie after a change constitutes acceptance of the updated policy.

Contact

If you have questions about this policy, please open an issue on the extension's support page or contact the developer directly via the Chrome Web Store listing.

This policy applies to the Amie Chrome Extension. It does not apply to any third-party services, including Chrome or Google's own services.