Last updated: September 27, 2026
This Privacy Policy explains how IChat handles information when you use the extension.
IChat is a Chrome extension that captures context from the current web page only when you explicitly trigger it, then sends the resulting prompt to the AI provider you selected in the extension settings.
IChat is designed as a local-first, bring-your-own-key product:
Depending on how you use the extension, IChat may handle the following categories of information:
Stored locally in extension storage:
Auto-send is off by default for new installs or when no value is saved. Captured context waits for you to send it manually unless you enable auto-send. Existing saved preferences are preserved.
When you explicitly trigger capture, IChat may collect:
When you click Capture selected text with IChat in the selection context menu, Chrome supplies the selected text and available page/frame metadata directly to IChat. This also supports text selections supplied by Chrome’s PDF viewer. This path does not read or write the clipboard, take screenshots, or extract surrounding text. It stores the selection locally as FlowContext and follows the existing auto-send setting when sending to the selected provider. The contextMenus permission is used to provide this explicit capture action.
If the current target includes an image, IChat may process:
If direct media resolution is not available, IChat may use screenshot-based fallback for the visible area needed to complete the requested capture.
For online PDFs opened in Chrome’s native PDF viewer, triggering capture with the extension action or keyboard shortcut takes an image of the currently visible tab area, including visible PDF viewer controls. It does not extract the full PDF or the exact text selection. This image follows the same local IndexedDB storage and selected-provider image sending flow, including your auto-send setting. The screenshot fallback uses existing permissions and no remote PDF processing service.
Stored locally:
With MOSS selected, the same in-memory recording flow sends a 16 kHz mono WAV directly to https://api.mosi.cn/v1/audio/transcriptions as a multipart file, using model moss-transcribe-1.0. Only the recording and transcription options are sent, without page context or chat history. The MOSS key stays in local extension storage and is sent only to MOSS for authentication. Recording limits, cancellation, and local cleanup match the Fun-ASR flow below. IChat does not create a separate hosted file through the MOSS files API.
Clicking the microphone starts the selected speech input flow after microphone access is allowed. Chrome built-in recognition is the default and may send audio to the browser’s speech service (for example, Google’s service in Chrome). Alternatively, you can choose Alibaba Cloud Fun-ASR-Flash or MOSS and supply its separate API key locally in Settings → STT Provider.
With Fun-ASR-Flash, IChat records up to three minutes of microphone audio into memory. Clicking Send or the microphone again, pressing Escape in the input, or reaching the recording limit stops recording and submits the audio as a 16 kHz mono WAV to Alibaba Cloud’s Beijing DashScope HTTPS endpoint for transcription. The request contains this recording and a language hint, not page context or chat history. Recordings are not saved to extension storage or IndexedDB and are released after processing or cancellation. Transcription can be cancelled; cancellation cannot undo audio already transmitted. Leaving the chat, hiding the document, switching providers, or closing the page cancels capture and outstanding requests. Listening never restarts automatically.
Recognized text is inserted into the unsent draft. If you click Send during recording, IChat first stops dictation and completes transcription, then sends the merged draft to the selected chat provider. Stopping with the microphone button alone does not send the draft; recognition failure or cancellation prevents the pending send. Sending the draft follows the same chat provider request and local chat storage flow as typed messages. Speech and chat providers are configured independently; this implementation uses no project-owned relay.
If the side panel cannot obtain microphone permission, an optional extension tab lets you grant access. The permission button briefly opens the microphone and immediately stops all audio tracks. A separate, user-triggered microphone test measures sound levels locally for up to ten seconds and displays the input device name. The test does not record, persist, or upload audio or device information; stopping it or leaving the tab releases the microphone. No additional manifest or host permissions are added for dictation. You can revoke microphone access in Chrome or system settings.
The browser’s speech service, Alibaba Cloud, or MOSS handles audio under its own terms, privacy policy, and retention rules. All modes depend on their respective service availability; offline recognition is not guaranteed.
IChat does not continuously monitor all browsing activity for remote processing.
IChat handles page context only when you explicitly trigger extension behavior, for example:
In the current implementation, IChat stores data locally in the browser:
IChat does not currently provide cloud sync or a project-owned account system.
When you send a request, IChat may send relevant content to the provider you selected in settings, such as:
Depending on your configuration, this may include direct requests to:
Those providers process requests under their own terms and privacy policies.
In the current implementation, IChat does not:
You control whether to use IChat and what to send.
Current controls include:
If broader delete or reset controls are added later, this policy should be updated to reflect them.
Locally stored data remains on your device until you change it, overwrite it, or remove it through extension controls or browser-level extension data removal.
Third-party provider retention is governed by the provider you selected, not by IChat.
IChat is not intended for children under 13.
IChat uses local browser extension storage for settings and state. However, no browser extension can guarantee absolute security. You should avoid using IChat with highly sensitive information unless you understand the risks of local storage and third-party AI provider processing.
This Privacy Policy may be updated when the product behavior changes, especially if storage, permissions, networking, or data flows change.
At this stage, the project does not yet publish a dedicated support contact address. When the public repository and project contact channels are finalized, this section should be updated with a stable contact method.