Privacy policy
Effective October 8, 2026 · Version 1.3.3
Focused access
Reads issue/PR URLs, authors, dates, avatars and comment bodies on GitHub and explicitly authorized Gitea sites. The displayed signed-in username separates accounts and marks mentions. Requests use the existing same-origin browser session; authentication cookie or token values are not read.
Your data, your control
Up to 80 recent results per tab are retained in chrome.storage.session, scoped by tab, installation and observed account. The cache is bounded globally to 16 tab buckets and 1,000,000 serialized characters. It is not synced or written to chrome.storage.local. Back navigation reuses results until manual or opted-in automatic refresh. Clear caches, observed account/site changes, tab closure, extension disable/reload/update, and browser restart discard cached data. Settings, explicitly saved notes and site/account-specific Gitea-login/GitHub-name display links remain in chrome.storage.local. Name links are excluded from diagnostics and can be removed individually or with their site.
Personal note
Personal notes are stored locally under hashed issue keys until deleted or the extension is removed. They are not synced, encrypted by this extension, or included in diagnostics or usage exports. Notes are shared within this Chrome profile and are not GitHub comments. Like other displayed page content, notes rendered on GitHub are not a secure secrets vault.
Access & privacy
Comment requests go only to the page’s GitHub or authorized Gitea origin. GitHub preview images use the existing allowlist; Gitea avatars and images are restricted to the same origin. HTTP Gitea traffic is unencrypted. No developer telemetry, remote scripts, tracking pixels, or advertising.
Support & feedback
Exports occur only when you explicitly download a file. You decide whether to share it. Support tickets and voluntary attachments are handled by GitHub under GitHub’s privacy policy. Do not put confidential information in public support issues.
Private by design. No developer telemetry.
Use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including Limited Use requirements. Data is used only for the extension’s single purpose and user-facing functionality, never sold or used for advertising.
Source code
Maintainer: eddy961206. Contact the maintainer through the repository support channel. This policy must be updated before changing data practices.