LeakLock

LeakLock privacy policy

Last updated: 27 October 2026

LeakLock is made by BAB Studios. This policy covers the LeakLock browser extension and the LeakLock extension for VS Code.

The short version

LeakLock checks text for things that look like passwords, API keys and tokens, and it does all of that on your own device. It makes no network requests, has no account, collects no analytics and sends nothing to BAB Studios or anyone else.

Browser extension

• Where it runs: only on github.com and gist.github.com. It is not active on any other website.
• What it reads: text you paste or type into text fields on those pages, so it can check it for credentials before you post it. The check happens inside the page, in memory.
• What it stores: one number, the count of warnings it has shown, kept in your browser's local extension storage so the popup can display it. It never stores the text you paste or type, and it never stores a detected secret.
• What it sends: nothing. The extension has no network access and requests only the storage permission.

VS Code extension

• What it reads: the files you open in the editor, so it can underline possible credentials and offer to redact them.
• What it stores: nothing beyond your own LeakLock settings, which VS Code keeps like any other extension setting.
• What it sends: nothing. The extension makes no network requests and has no telemetry.

Sharing and sale of data

LeakLock does not collect personal data, so there is nothing to share, sell or transfer.

Changes

If this policy changes, the new version will be posted at this address with a new date at the top.

Contact

Questions or a privacy concern: email babstudios.app@gmail.com.