Chrome Profile Locker does not collect, transmit, sell, or share any personal data. The complete source is published under the MIT license so you can verify that claim yourself.
What is stored
All data is stored locally in your browser profile via chrome.storage.local and
chrome.storage.session:
- Salted password/PIN hash and recovery-code hash (never the plaintext secrets)
- Settings (idle timeout, Incognito coverage toggle, optional TOTP secret, optional unlock with authenticator alone flag)
- A local audit log of recent lock/unlock events (timestamps and event types only)
- Short-lived per-tab resume URL entries in session storage (cleared once used or when the tab closes)
Session rate-limit counters and unlock state clear when the browser closes.
What is not collected
- No analytics or telemetry
- No crash reporting to third parties
- No advertising identifiers
- No remote servers of any kind
- No network requests initiated by this extension for its own operation
Optional authenticator-only unlock (when you turn it on) still verifies codes entirely on-device. Nothing is transmitted.
Third parties
No remote third-party services. A MIT-licensed QR encoder is bundled inside the extension package; it is not fetched from a CDN at runtime. There are no analytics SDKs or remote fonts.
Contact
- Primary: GitHub Issues
- Email: extensions@talhajaved.com