Common questions about privacy, security, and permissions
This page addresses common privacy and security questions about the ThinkReview browser extension. For more detailed information, see our Privacy Policy and Zero Code Retention pages.
ThinkReview requires host permissions to function properly. These permissions are necessary for the following reasons:
https://gitlab.com/* - Used to inject content scripts and fetch patch files from GitLab merge request pageshttps://github.com/* - Used to inject content scripts and UI elements into GitHub pull request pageshttps://patch-diff.githubusercontent.com/* - Used by the background script to fetch GitHub diff/patch files (required to avoid CORS restrictions)https://dev.azure.com/* - Used to inject content scripts and make API calls to Azure DevOps pull request pageshttps://*.visualstudio.com/* - Used for Azure DevOps Visual Studio domains (same purpose as dev.azure.com)https://us-central1-thinkgpt.cloudfunctions.net/* - Backend service for AI reviews, user authentication, and subscription managementhttp://*:*/* and https://*:*/* - Used only for custom/self-hosted GitLab instances. Users must explicitly grant these permissions for their custom domains.Why These Permissions Are Necessary:
chrome.scripting API to dynamically register content scripts for custom GitLab domains.patch files directly using fetch() with credentials.diff files through the background script from patch-diff.githubusercontent.com (to avoid CORS restrictions)ThinkReview ONLY reads code diffs from PRs/MRs that you explicitly open and request reviews for. The extension never writes, modifies, or changes any code.
Technical Details:
document.createElement() and appendChild() - it does not modify existing page content or codedocument_idle (after page load) and only add review UI componentsNo. ThinkReview has a zero code retention policy. For detailed information, see our Zero Code Retention page.
How Zero Code Retention Works:
This means your source code is processed in real-time for AI code reviews and immediately discarded—never stored, cached, or retained in any form on our servers.
Yes! ThinkReview is open source and publicly available on GitHub.
Open Source Details:
Open-source availability enables transparency and community audits. You can review the codebase to verify all privacy and security claims, including:
For more detailed information about privacy and security:
If you have additional questions about privacy, security, or permissions, please contact us:
Email: support@thinkode.co.uk
Subject Line: "Privacy Inquiry"
Company: ThinkReview trading as Thinkode LTD
Company Registration Number: 12850972
Website: https://thinkreview.dev
We're committed to transparency and are happy to discuss our privacy practices with you.