Privacy Policy

What the extension does with data

When you ask the agent about a page, the extension reads the current page's content and sends your prompt (plus that page context) to whichever AI backend you have chosen. That is the only outbound flow, and you choose where it goes. Nothing is sent anywhere until you type a message.

Data the extension reads

• The active page's content - URL, title, visible text, and HTML of the docs page you are viewing, plus any text you have selected. Read only when you send a message, only for the active tab, and only to answer or edit that page.
• Your settings and credentials - the API keys and GitHub sign-in tokens you enter, your chosen backend/model, and appearance preferences. Stored in your browser via chrome.storage (synced across your own Chrome profile and kept as a local fallback). They are never transmitted to Glassdocs except, in Managed mode, the GitHub sign-in token used to authenticate you (below).
• Per-repo chat history - stored locally in your browser so a conversation persists between sessions. Optionally mirrored into your own GitHub repository if you enable that.

Where data goes (you choose the backend)

• Bring-your-own-key backends (Claude, OpenAI, GitHub Models) - your prompt and page context go directly from your browser to the provider you configured (Anthropic, OpenAI, or GitHub), authenticated with your own key. Glassdocs is not in the path and never sees this data.
• Managed backend - if you use the “Managed (no key)” option, your prompt and page context pass through the Glassdocs managed backend at app.glassdocs.site. It verifies your identity using your GitHub sign-in token, records usage counts to enforce fair-use limits, and forwards the request to an AI provider using Glassdocs' own key. It does not sell your data, show ads, or use your content to train models. Switch to a bring-your-own-key backend to keep everything browser-to-provider.
• GitHub - to read source files, open pull requests, or push commits, the extension calls the GitHub API with the token you signed in with. Commits and PRs are attributed to your GitHub identity.

Enterprise-managed configuration

If your organization deploys the extension via Chrome enterprise policy (e.g. Google Workspace), an administrator may push a shared configuration - such as the backend to use - through Chrome's read-only managed storage. This config is set by your organization, not collected by Glassdocs. Your GitHub sign-in remains per-user, so your commits stay attributed to you.

What the extension does not do

• No analytics, telemetry, tracking pixels, or advertising.
• No selling or sharing of your data with third parties for their own purposes.
• No use of your content to train AI models by Glassdocs.
• No background collection - data is read only when you actively send a message.
• No cloud text-to-speech - in the extension, “Read aloud” and the speak control on an assistant reply both use a speech voice installed on your own device, so the page text and the message text never leave your machine. If no on-device voice is available they refuse to speak rather than falling back to a remote speech service.

Play controls inside a published knowledge base

A published knowledge base carries its own play controls in the page itself, for readers with no extension installed - which is every reader on a phone. There are up to two, and they are different in kind:

• “Listen” - always present. It asks your browser for a speech voice installed on your own device, exactly as the extension does, and refuses to speak if there is none rather than falling back to a remote speech service. The audio is produced entirely by your browser and your operating system, and Glassdocs is not in that path.
• “AI” - present only when that knowledge base has published a recording of that page, and only while the recording matches the page you are reading. This audio was not made by your browser: an administrator of that knowledge base generated it, in their own browser, and published it into their own site. Pressing the control fetches the recording from that knowledge base's own origin - the same site, under the same access control as the page itself - and nothing else. Nothing is fetched until you press it, and nothing about which page you are reading is sent anywhere in order to play it: whether a recording exists is stated in the page you already loaded, not asked of us.

The admin console (organization admins)

• Org shared AI key - an admin may store one shared AI provider key for their GitHub organization. It is held AES-encrypted at rest on the Glassdocs backend, is never sent back to browsers, and the admin can replace or remove it at any time.
• Organization membership - to enforce who the shared key covers, the backend keeps a member roster synced from the GitHub organization by an admin.
• Usage statistics - per-organization token counts for fair-use enforcement and admin visibility. Token counts only; never prompts, page content, or documents.

Optional local debug channel

For developers, an off-by-default diagnostics option can stream events to a local collector. It is restricted to loopback addresses (localhost / 127.0.0.1); a non-loopback destination is ignored so page content cannot be exfiltrated. It stays off unless you turn it on.

Your control

• Clear your keys, tokens, and history any time from the extension's Options page, or by removing the extension.
• Choose a bring-your-own-key backend to avoid the managed backend entirely.
• Data handled by the AI providers and by GitHub is governed by their own privacy policies.

Contact

Questions about this policy? Email hello@rocketlab.com.au.