Last Updated: March 8, 2026
GitHub Devwatch is a Chrome extension for monitoring activity on GitHub repositories. This policy explains what the extension stores, when it makes network requests, and what is not collected.
GitHub Devwatch collects and stores the following data locally on your device only:
-
GitHub OAuth Session
- Created when you connect GitHub through the built-in device-flow sign-in
- Stored by the extension in Chrome session storage for the current browser session only
- Cleared when the browser session ends or when you disconnect GitHub in DevWatch
- Used only to authenticate with GitHub's API
- Not sent to third-party services operated by this project
- Never shared with anyone
-
Repository Watch List
- List of GitHub repositories you choose to monitor
- Stored in Chrome's sync storage for convenience across your Chrome browsers
- Only used to fetch activity from those repositories
-
Extension Settings
- Your preferences (check interval, notification settings, theme, etc.)
- Stored in Chrome's sync storage
- Synced across your Chrome browsers if you're signed into Chrome
-
Activity Data
- Recent activity from your watched repositories (up to 2000 items)
- Cached locally for offline viewing
- Trimmed automatically when the activity limit is reached or cleanup rules apply
- We do NOT collect personal information
- We do NOT track your browsing activity
- We do NOT use analytics or telemetry
- We do NOT share any data with third parties
- We do NOT transmit your data to external servers
All data collected is used exclusively to provide the extension's functionality:
- Your GitHub connection authenticates API requests to GitHub
- Your repository list determines which repositories to monitor
- Your settings customize how the extension behaves
- Activity data is displayed in the extension popup for your review
- The extension uses Chrome storage APIs for settings, cached activity, and GitHub sign-in handling
- Settings and repository lists can optionally sync across your Chrome browsers if you use Chrome Sync
- GitHub sign-in data uses session storage rather than Chrome sync and is not persisted across browser restarts
- You can clear all data at any time by uninstalling the extension or using Chrome's "Clear extension data" feature
This extension communicates with GitHub's API (api.github.com) to fetch repository activity. When you use this extension:
- API requests are made directly from your browser to GitHub
- Requests include your GitHub OAuth access token for authentication
- GitHub's privacy policy and terms of service apply to these interactions
- See GitHub's privacy policy at: https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement
When you add a repository by NPM package name, the extension communicates with the NPM registry (registry.npmjs.org):
- This is entirely optional and only happens when you use the "Add by NPM package" feature
- Used to look up the GitHub repository associated with an NPM package
- No authentication or personal data is sent to NPM
- NPM's privacy policy applies to these interactions
GitHub Devwatch does NOT:
- Use advertising networks
- Use analytics services
- Connect to any servers we operate
- Share data with any other third-party services
The extension requests the following Chrome permissions:
- storage: To save your settings, GitHub sign-in state, and activity data locally
- alarms: To periodically check for new repository activity
- notifications: To show you browser notifications for new activity
- Host permission for api.github.com: To fetch repository activity from GitHub's API
These permissions are used only for the stated functionality and nothing else.
You have complete control over your data:
- View Your Data: All settings are visible in the extension's options page
- Delete Your Data: Uninstall the extension to remove all data, or use the "Clear All Data" option in settings
- Export Your Data: Use the backup/restore feature to export your settings
- Revoke Access: Disconnect locally in DevWatch, and revoke the OAuth app in GitHub's authorized applications settings at any time
Current builds include several concrete safeguards:
- All API requests use HTTPS
- The GitHub auth session is kept in session storage for the current browser session only
- The codebase includes input sanitization and GitHub URL validation checks
- Extension pages use a Content Security Policy
These measures reduce risk in normal use, but they should not be read as a formal security certification or third-party audit.
We may update this privacy policy from time to time. Changes will be reflected in:
- The "Last Updated" date at the top of this document
- The extension's release notes in CHANGELOG.md
This extension is not directed at children under 13. We do not knowingly collect information from children.
If you have questions about this privacy policy or the extension:
- Open an issue on GitHub: https://github.com/jonmartin721/devwatch-github/issues
- Developer: Jonathan Martin
This extension is open source. You can review the code to verify these privacy claims: https://github.com/jonmartin721/devwatch-github
By installing and using GitHub Devwatch, you consent to this privacy policy.