CollectMind
Privacy Policy
Last updated: September 18, 2026
CollectMind is a Chrome extension for organizing bookmarks into topics, summarizing saved pages, and chatting with your collection using AI. This policy explains what data the extension touches, where it goes, and where it never goes.
What data CollectMind processes, and where it stays
| Data | What it's used for | Where it's stored |
|---|---|---|
| Bookmark topics, saved page URLs/titles/icons | Organizing your collection | Locally, in your browser's IndexedDB |
| Extracted page text | Generating summaries and enabling chat about a page | Processed on-device; only the resulting summary and search index are kept |
| Page summaries | Displaying summaries, powering topic-level chat | Locally, in IndexedDB |
| Text embeddings (search index) | Retrieving relevant content when you chat | Locally, in IndexedDB |
| Chat messages you send and receive | Showing your conversation history | Locally, in IndexedDB |
None of the above is transmitted anywhere unless you explicitly use the Google Drive backup feature described below. Uninstalling the extension, or clearing its site data from Chrome, deletes all of it.
AI processing is entirely on-device
Summaries and chat responses are generated by Gemini Nano, a model built
into Chrome itself and run locally by the browser (see
Chrome's built-in AI documentation).
Search relies on a small local embedding model (Xenova/multilingual-e5-small,
via Transformers.js)
that also runs entirely inside your browser. Neither of these sends your page content,
summaries, or questions to any server — including CollectMind's developer, who has no
server to send them to.
Optional: backing up to Google Drive
If you choose to connect a Google account (Settings → Cloud sync), CollectMind can back up your topics, saved pages, summaries, and chat history to your Drive. Specifics:
- What's sent: the same data listed in the table above. Search embeddings are not included — they're large, derived data that gets rebuilt locally on whichever device restores a backup.
- Where it goes: directly from your browser to a hidden, app-specific folder in your own Google Drive (the
drive.appdatascope), created by and only accessible to CollectMind acting on your behalf. It is not visible in your regular Drive file list, and it is not accessible to CollectMind's developer or anyone else — Google's OAuth infrastructure only lets the extension read and write files it created, in your account. - Your control: you can create any number of backups, delete individual backups, or disconnect the Google account entirely, all from Settings. Disconnecting revokes the extension's access token; you can also revoke access at any time from your Google Account permissions page.
- What CollectMind's developer can see: nothing. There is no server in this flow that the developer operates or has access to.
Permissions this extension requests, and why
- Website access +
scripting: to read the title, URL, and text content of the page you're currently viewing, so it can be saved, summarized, or discussed in chat. This only happens when you take an explicit action (saving a page, or asking to chat about the current page) — it never reads pages in the background. offscreen: runs summarization and the local embedding model in a background document so the visible UI stays responsive.unlimitedStorage: the on-device search index (embeddings) can grow past the default browser storage quota for a large collection.identity/identity.email: used only for the optional Google Drive backup feature described above, to sign you into your own Google account and show which account is connected.
Children's privacy
CollectMind is not directed at children and does not knowingly collect data from anyone.
Changes to this policy
If this policy changes, the "Last updated" date above will change accordingly, and the current version will always be available at this URL.
Contact
Questions about this policy can be filed as an issue on the CollectMind GitHub repository.