Our Commitment
Your privacy is the cornerstone of BrowserLock. We believe that your security tools should protect your data, not collect it. This policy explains how we handle information and why we require certain permissions to keep your browser profile safe.
Data Collection & Usage
BrowserLock is designed to operate entirely within your local Chrome environment. We do not use any tracking pixels, analytics, or remote logging services.
- PIN Protection: Your access PIN is hashed and stored locally using the Chrome Storage API. We never see it, and it never leaves your device.
- Settings: All configuration choices (auto-lock timers, quarantine settings, etc.) are saved locally for your convenience.
- Browsing History: If you enable the "Clear History on Quarantine" feature, the extension will clear your local history during a security event. We do not read or record your history.
Permissions Explained
To provide professional-grade security, BrowserLock requires specific permissions. Here is exactly why we need them:
- Storage: To save your encrypted PIN hash and security preferences locally on your computer.
- Idle: To detect when you are away from your computer so we can automatically lock the browser for you.
- Notifications: To alert you before an auto-lock occurs, giving you a chance to stay active.
- History: Only used if you enable the security feature to wipe history after multiple failed PIN attempts.
- Tabs: To ensure the lock screen overlay covers every open window and tab consistently.
- Alarms: To manage precise timing for quarantine periods and pre-lock notifications.
Third-Party Sharing
We do not share, sell, or trade your information with third parties. Since no data is collected in the first place, there is no data to share. BrowserLock does not communicate with any external APIs or servers.
Contact Us
If you have any questions about this Privacy Policy or the security of BrowserLock, please contact us at: