gitlab-mr-approval-extension

Privacy Policy for GitLab MR Approval Guard

Last Updated: April 8, 2026

GitLab MR Approval Guard does not collect, store, or transmit any personal data or user information.

This extension operates entirely locally in your browser and:

Reads approval counts from GitLab merge request pages
Detects protected branch names (main, master, production, development, staging, nightly)
Modifies the merge button behavior based on approval status
Displays warning banners for protected branches

GitLab MR Approval Guard uses your browser’s sync storage (chrome.storage.sync) solely to save your customized settings, which include:

This data remains securely tied to your browser profile and is not transmitted to our servers or any third parties. The extension does not use:

This extension does not communicate with any third-party services or external servers. All functionality is self-contained within the extension.

activeTab: To inject scripts into GitLab pages you’re currently viewing
Host permissions (*://gitlab.com/* and similar): To access GitLab domains and read page content to enforce approval rules
scripting: To modify the merge button state and display warning banners
storage: To save your custom extension preferences (e.g., critical branches, required approvals, and actions)

All processing happens locally in your browser. No data leaves your machine.

Any updates to this privacy policy will be reflected in the extension’s repository and updated in the Chrome Web Store listing.

For questions or concerns about this privacy policy, contact: emad.ehsanrad@gmail.com

This extension complies with:

This site is open source. Improve this page.