Privacy Policy

Reviewable Diff for GitHub · Last updated 22 July 2026

Reviewable Diff for GitHub analyses GitHub pull requests so users can see how much of a change consists of product code, tests, documentation, generated files, vendor files, lockfiles, or other files.

Information the extension handles

To provide this feature, the extension accesses the current GitHub pull request's repository and pull-request identifiers, commit hash, changed file paths, line counts, and diff contents. Repository-provided .reviewdiff.json classification rules may also be read when present.

How information is used

This information is used only to classify changed files and calculate the breakdown displayed in the Reviewable Diff panel. Processing takes place locally in the user's browser.

GitHub requests and private repositories

Pull-request data is requested directly from GitHub over HTTPS. For private repositories, GitHub may use the user's existing authenticated browser session to authorise those requests. The extension does not read, store, or transmit passwords, authentication cookies, or access tokens.

Local storage and retention

Analysis results may be cached in Chrome's local extension storage to improve performance. Cached data can include repository and pull-request identifiers, commit hashes, changed file paths, line counts, and file classifications. The cache is limited in size, remains on the user's device, and can be removed by clearing the extension's data or uninstalling the extension.

Sharing and external services

Reviewable Diff does not send repository contents, pull-request contents, browsing activity, or analysis results to the developer. It does not use analytics or advertising services, sell user data, or allow humans to access user data. Information is not shared with third parties except for direct requests to GitHub that are necessary to provide the extension's stated functionality.

Limited Use

Reviewable Diff's use of information complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Information is used only to provide the extension's single, user-facing purpose.

Changes to this policy

This policy may be updated if the extension's functionality or data practices change. The latest version will remain available at this URL.

Contact

Questions can be submitted through the policy repository's issue tracker.