Munin Assistant for Google Docs
Privacy policy: Munin Assistant for Google Docs
Last updated: 2026-10-16
What the extension is
Munin Assistant for Google Docs is a Chrome extension that adds an AI assistant panel to Google Docs. The assistant reads the open document and edits it, using the AI provider and the API key you choose (Munin, OpenAI or Anthropic). The extension has no server of its own and collects no data for its developer. This page describes what the extension accesses, what it sends and where, and what it keeps on your computer.
Data accessed through your Google account
Signing in with Google is optional. If you sign in, the extension requests these scopes:
https://www.googleapis.com/auth/documents, which Google shows as access to see, edit, create and delete all your Google Docs documents. The extension uses it to read the document open in the tab and to apply the edits the assistant makes (and Undo) to that document only. It reads another document only throughopen_document, and only after you click Allow on the card that names it (or when you put its link in your own message or the document instructions); such documents are only read, never edited. It does not create or delete documents.openid,emailandprofile. The extension asks Google's userinfo endpoint (openidconnect.googleapis.com) once per sign-in for your account's email address and name.
The Google Drive scope is not requested. Without signing in, the extension reads the document through Google Docs' own export link, with your existing Google session.
How the data is used
The document's text, title and outline are used only to answer your requests in the panel: the assistant reads them with its reading tools and changes the document when you ask it to (in Auto mode). Your account's email and name are used only to show which account is signed in and to renew the access for that account. The developer does not use the data for advertising, profiling, analytics or training AI models.
The use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Where data is stored
In the browser's extension storage (chrome.storage.local), on this computer only:
- your API keys and settings (provider, model, Auto/Manual, theme, panel size and open/collapsed state);
- your chats per document, including the information needed to undo the assistant's edits and the text it read from the document (long results of reading tools are replaced by a short note once an answer is finished);
- your document instructions per document;
- the cached model lists, the flag that you are signed in with Google, and the email address and name of the signed-in Google account.
The Google access token and its expiry are kept in memory and in the browser's session storage (chrome.storage.session: not written to disk, cleared when the browser closes, not readable by the Google Docs page). The developer has no server, so nothing is stored there.
What is shared and with whom
- The AI provider you choose (Munin at
api.muninai.org, OpenAI atapi.openai.comor Anthropic atapi.anthropic.com), with your own API key, only when you send a message: your messages and the chat history, the document's title, size and outline, the text the assistant reads from the document with its reading tools, your current selection, your document instructions for that document, and the text of any additional document you allowed it to open. For Munin's/research,/codeand/chatcommands, the first 30,000 characters of the document are sent instead. Each API key is sent only to its own provider. Nothing is sent to the providers you have not selected. How the provider handles this data is governed by its own terms and privacy policy; OpenAI requests are made withstore: false. - Web search. When you use
/researchwith OpenAI or Anthropic, the provider's server-side web search runs the search queries the model writes; those queries, which may be based on your document, go to the provider's search service. The model is instructed to treat document text, opened documents and search results as data, not as instructions, and to keep document text out of search queries beyond short topic phrases; this is a rule in the prompt, not a technical guarantee. Munin's/researchuses Munin's own search tools on Munin's servers. - Google, only if you sign in: the Docs API and userinfo requests described above. Requests go directly from your browser to Google.
The extension does not send document text, messages, keys or account data anywhere else. Nothing is sent to the developer of the extension, and the developer cannot see your documents, chats, keys or account. No analytics, no telemetry, no advertising, no tracking. No data is sold, and none is shared with third parties beyond the requests to the provider and to Google described above, which you start.
Retention and deletion
- Google access token: kept until it expires (usually after one hour; it is then renewed silently), until you sign out, or until the browser closes.
- Account email and name: kept until you sign out.
- Chats: kept until you delete them (open the chat list in the panel and click ✕). A document's chats are deleted automatically when none of them was used for 180 days.
- Document instructions: open them, clear the text and click Save.
- API keys: clear the key in the settings and click Save, and revoke the key on the provider's website.
- Everything: uninstall the extension (
chrome://extensions→ Remove). Chrome then deletes all of its stored data.
Data already sent to the AI provider is kept according to that provider's terms.
Revoking access
- In the panel: Settings → Google account → Sign out revokes the token at Google and forgets it and the account's email and name. The panel then reads the document through the export again.
- At Google: remove the extension's access at myaccount.google.com/permissions.
Changes to this policy
Changes are published on this page with a new "Last updated" date. A change in what the extension accesses or sends is also noted in the extension's changelog.
Contact
Ivan Iushin, iushin.ivan.chem@gmail.com.