GitQuiet privacy policy

Last updated: 16 August 2026

GitQuiet improves GitHub pull request, issue and Actions pages. It comes as an extension for Chrome, Firefox and Safari, and as an app for macOS. This policy covers both. There is no GitQuiet account and no GitQuiet server.

What we process

The extension reads GitHub pages and API responses in your signed-in browser session so it can draw its review screens. That content stays in your browser.

The extension stores display settings and a local cache of GitHub payloads in your browser's extension storage, on your device, so pages open quickly.

The app reads the same GitHub API with your token, and keeps the same kind of cache on your machine.

Signing in, in the app

The app signs you in through GitHub's own page, opened in the browser you already use. GitHub hands the app a token afterwards.

That token is kept in your macOS keychain. It goes to GitHub and nowhere else. Signing out removes it from the keychain.

Before you sign in, the app can use a GITHUB_TOKEN you exported yourself, or the token the GitHub CLI already holds if you are signed in there. It reads those; it never writes to them.

Checking for a new version, in the app

On launch the app asks the GitHub release page whether a newer version exists. That request tells GitHub your IP address and which version you run, the same as downloading the app by hand would.

What we do not do

• We do not sell user data.
• We do not use your GitHub content for advertising.
• We do not use your data for credit or lending decisions.

Error reporting

There is none. GitQuiet has no error reporting service and no third-party endpoint of any kind. When something fails that GitQuiet carries on through, it writes a line to your own browser's console, where only you can see it. Nothing about a failure leaves your machine.

Contact

Questions: open an issue on GitHub.