Locksy
Locksy
Back to HomeBack
Last Updated: January 29, 2026

Privacy Policy

Complete transparency on how we handle your data. Your privacy is our top priority.

The Bottom Line

All data stays on YOUR device only
PBKDF2 with 600k iterations
Zero tracking or analytics
No third-party services
Open source & verifiable
Overview

Our Commitment to Your Privacy

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.

Data Collection

What We Collect

Stored locally on your device only

πŸ”

Master Password (Hashed)

Your password is hashed using PBKDF2 with 600k iterations before storage. Military-grade security with 120 years crack resistance.

βš™οΈ

Extension State

Whether the extension is currently active or inactive. That's it.

πŸ“‘

Locked Tab IDs

Temporary list of which tabs are locked. Automatically cleared when tabs close.

πŸ”’

Session Data

Failed login attempts and lockout timestamps for brute-force protection.

What We DO NOT Collect

Browsing history
Website URLs
Personal information
Payment data
Cookies
Page content
Analytics
Device info
Security

Storage & Security

Local Storage Only

  • All data on YOUR device
  • No cloud uploads
  • No external servers
  • Works 100% offline

Security Measures

  • PBKDF2 with 600k iterations
  • No plain text storage
  • Chrome secure APIs
  • Rate limiting & brute-force protection
Transparency

Permissions Explained

storage

Purpose: Store your hashed password and settings locally

Note: Never leaves your device

tabs

Purpose: Identify which tabs you want to lock

Note: We don't read page content

activeTab

Purpose: Lock the current tab with one click

Note: Only tab ID, no content

notifications

Purpose: Confirm lock/unlock actions

Note: Just visual feedback

webNavigation

Purpose: 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.

Zero Data Sharing

βœ“ We do NOT sell your data
βœ“ We do NOT share with anyone
βœ“ We do NOT transmit online
βœ“ We do NOT use analytics
Your Control

Delete Your Data Anytime

πŸ—‘οΈ

Uninstall Extension

  • 1Right-click icon
  • 2Remove from Chrome
  • 3Data auto-deleted
🧹

Clear Storage

  • 1chrome://extensions/
  • 2Find Locksy
  • 3Clear storage
πŸ’Ύ

Clear Browser Data

  • 1Settings
  • 2Clear browsing data
  • 3Hosted app data

Legal Compliance

πŸ‡ͺπŸ‡Ί GDPR Compliant

For users in the European Union:

  • Local processing only
  • Minimal data collection
  • Easy data deletion
  • Complete transparency

πŸ‡ΊπŸ‡Έ CCPA Compliant

For California residents:

  • No selling of data
  • No third-party sharing
  • Instant deletion
  • Full disclosure

Open Source & Verifiable

Don't take our word for it. Review our source code, audit our security, and verify every claim we make.

View Source Code

Questions? Contact Us

GitHub Issues

github.com/vansh-121/Locksy/issues

Developer

vansh-121

Security Vulnerabilities

Report privately via GitHub Security Advisories. Do not disclose publicly until patched.

By installing and using Locksy, you acknowledge that you have read and understood this Privacy Policy.

Effective as of October 20, 2025

We built this to protect your privacy, not invade it. ❀️

LocksyLocksyβ€’ Privacy-First Security
HomeGitHub

Β© 2025 Locksy. Open source and privacy-focused.