Complete transparency on how we handle your data. Your privacy is our top priority.
Locksy ("the Extension") is built with privacy at its core. This policy explains exactly what data we collect (spoiler: almost nothing), where it's stored (on your device only), and how you maintain complete control. We believe in radical transparency and your right to privacy.
Stored locally on your device only
Your password is hashed using SHA-256 before storage. We never see or store your actual password.
Whether the extension is currently active or inactive. That's it.
Temporary list of which tabs are locked. Automatically cleared when tabs close.
Failed login attempts and lockout timestamps for brute-force protection.
storagePurpose: Store your hashed password and settings locally
Note: Never leaves your device
tabsPurpose: Identify which tabs you want to lock
Note: We don't read page content
scriptingPurpose: Show the lock overlay on locked tabs
Note: Only when you lock a tab
activeTabPurpose: Lock the current tab with one click
Note: Only tab ID, no content
notificationsPurpose: Confirm lock/unlock actions
Note: Just visual feedback
webNavigationPurpose: Keep lock active when tab refreshes
Note: Prevents bypass attempts
<all_urls>Host Permissions: Allows locking any tab. Only activates on tabs YOU explicitly lock. No automatic monitoring.
For users in the European Union:
For California residents:
Don't take our word for it. Review our source code, audit our security, and verify every claim we make.
View Source Codevansh-121
Report privately via GitHub Security Advisories. Do not disclose publicly until patched.
Effective as of October 20, 2025
We built this to protect your privacy, not invade it. β€οΈ