Review Guard for GitHub Privacy Policy

Effective August 18, 2026 · Version 0.1.0

Review Guard for GitHub has one purpose: on a GitHub pull request's Files changed page, warn before you submit an Approve review while any changed file is still marked "Not Viewed," and offer to jump to the first one instead.

Data processed

The extension reads two things already visible in GitHub's own page: which review option (Comment, Approve, or Request changes) is selected in GitHub's own review dialog, and the "Viewed" / "Not Viewed" state GitHub already displays next to each changed file. Both are website content already rendered by GitHub for the signed-in user; the extension does not request, decode, or infer anything beyond what is on the page.

The extension does not read file contents, diffs, comments, commit data, account identity, cookies, or login state.

Storage, transmission, and sharing

All processing happens locally in the active browser tab. Review Guard does not collect, transmit, sell, share, or retain the review selection, file names, viewed state, or any other page data. It has no developer-operated server, analytics, advertising, account system, OAuth integration, network requests, or remote code.

What the warning does

When it detects an Approve submission with unreviewed files, the extension shows a local on-page warning with two choices: "Review remaining files," which clicks GitHub's own Cancel control and scrolls to the first unreviewed file, or "Approve anyway," which resubmits the same review GitHub was about to process. Both actions only replay GitHub's own controls; the extension never submits a review, comment, or approval on its own.

Site access

The extension runs only on github.com pull request pages (URLs matching github.com/*/*/pull/*). It requests no other site access, no activeTab, and no background or storage permissions.

Retention and deletion

The extension keeps no database, history, or stored settings. Its only state is an in-memory flag that exists for a fraction of a second while it lets a user-confirmed "Approve anyway" click through; nothing is written to disk. Closing the tab or navigating away discards everything.

Changes

If a future version changes how data is processed, this policy and Chrome Web Store disclosures will be updated before that version is distributed.

Contact

For privacy or support questions, use the developer contact address shown on the extension's Chrome Web Store listing.