Goose Glance runs in your browser. This page explains what data the extension uses and how it is stored.
Goose Glance itself does not collect any user data. If you use a cloud AI model, the provider may receive job description text extracted from the Waterloo Works Overview page. This depends on your chosen provider’s privacy policy.
Goose Glance stores analyzed job summaries in your browser’s IndexedDB to avoid re-analyzing the same job. You can view or delete this data via your browser DevTools → Application → IndexedDB → gooseGlanceDB. These entries are tiny and usually do not need cleaning.
When using a local AI model, WebLLM stores an approximately 4 GB model (Qwen3 4B Q4) in your browser cache. The model weights do not learn from your inputs. To remove it, open DevTools → Application → Storage to see the usage, and click “Clear site data”. The model will re-download next time you use local AI.
If you use a cloud AI provider, your API key is stored in Chrome Storage. When Chrome Sync is enabled, it will sync across devices signed in to the same Google account. The key is used only to authenticate requests you initiate. Goose Glance will never collect this key. You can always revoke it from your provider and clear it from the extension at any time.
Goose Glance does not extract any sensitive data. Goose Glance will never extract your name, resume, work history, or any other personally identifiable information (PII) from its users.
Goose Glance is open source under the MIT License and is provided as‑is, without warranties or conditions of any kind. Source code: github.com/lacser/Goose-Glance.
How to clear data: remove the extension, clear site data for the extension, or use Chrome’s developer tools to delete related IndexedDB entries.