Is Lockbox — API Key Wallet safe to install?

What data it declares

The developer declares that it collects these kinds of data:

• Authentication information such as passwords, credentials or PIN codes

The developer also certifies that your data is not sold to third parties outside approved uses, not used for purposes unrelated to the extension's core function, and not used to decide creditworthiness or lending.

The listing links to a privacy policy.

This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

What Chrome asks you to allow

When you add it, Chrome asks you to allow it to:

• Read and change your data on a number of websites
• Modify data you copy and paste

Derived from the manifest by Chrome's documented rules; the dialog's exact wording depends on your Chrome version and language. Chrome asks again if an update requests more.

What it can reach

Specific sites only: 21 match patterns.

• https://platform.openai.com/* only platform.openai.com
• https://console.anthropic.com/* only console.anthropic.com
• https://dashboard.stripe.com/* only dashboard.stripe.com
• https://console.aws.amazon.com/* only console.aws.amazon.com
• https://github.com/* only github.com
• https://vercel.com/* only vercel.com
• https://supabase.com/* only supabase.com
• https://console.firebase.google.com/* only console.firebase.google.com
• https://dashboard.clerk.com/* only dashboard.clerk.com
• https://railway.app/* only railway.app
• https://console.cloud.google.com/* only console.cloud.google.com
• https://dash.cloudflare.com/* only dash.cloudflare.com
• and 9 more

Routine for an extension

• Act on the current tab, but only after you click it activeTab
• Schedule work to run later alarms
• Put data on your clipboard clipboardWrite
• Add items to the right-click menu contextMenus
• Open a panel beside the page sidePanel
• Store data in your browser storage

Pages it runs its code on

It runs its own code on specific pages only: 20 site patterns.

• https://platform.openai.com/* only platform.openai.com
• https://console.anthropic.com/* only console.anthropic.com
• https://dashboard.stripe.com/* only dashboard.stripe.com

A content script is code the extension injects into pages matching these patterns. On those pages it can read and change what you see, whether or not a host permission is listed above.

What it may ask for later

Not granted when you add it: Chrome asks you the moment the extension requests one of these, and you can refuse. It may later ask for access to every site.

• <all_urls> every site

Sites that can connect to it

Web pages matching these patterns can open a messaging channel to it: 1 site pattern.

• https://dashboard.yourlockbox.dev/* only dashboard.yourlockbox.dev

Declared as externally connectable in the manifest: a page on these sites can exchange messages with the extension, for example to tell it you have signed in. It does not give the page access to your browser.

How usual this is for its category

In Productivity · Developer, 30% of extensions ask for access to every site. This one: Access to specific sites only.

The typical extension there declares 3 browser permissions; this one declares 6 browser permissions.

Counted over the live extensions of the same category after our latest full pass of the store. A share is context, not a verdict: what is normal depends on what the extension is for.

Who uses it and how it is kept up

14 users

• Last updated in the store 225 days ago, on 2026-03-19.
• No new version in the last 90 days.

What the store shows

The store shows none of its badges on this listing. Most listings carry none.

Has it asked for more over time?

This is the question a permission list on its own cannot answer. An extension that shipped narrow and widened later is a different proposition from one that always asked for the same thing.

The permissions this extension requests have not changed since we started watching it.

Who publishes it

The store lists no publisher name. This listing has been in the store since 2026-03-04 and was last updated on 2026-03-19.

Similar extensions that ask for less

Listings close to this one in what they say they do, which declare less reach. Less reach is not a verdict on either: compare what each needs for the job.

1. API Ring No site access · 2 permissions 3 users
2. VaultPass Runs its code on every site · 5 permissions 656 users ★ 4.2
3. Vibe Vault Importer Access to specific sites only · 2 permissions, 18 site patterns 4 users

How to check or remove it in Chrome

1. Type chrome://extensions in the address bar and find the extension in the list.
2. Open its details. The site access setting shows where it can run; set it to run only on click and it reaches a page only after you press its icon.
3. To uninstall it, choose Remove on the same page.

Questions people ask

What can Lockbox — API Key Wallet access?

Specific sites only: 21 match patterns. It declares 6 browser permissions.

What data does Lockbox — API Key Wallet collect?

The developer declares that it collects these kinds of data: Authentication information. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

Has Lockbox — API Key Wallet asked for more permissions over time?

The permissions this extension requests have not changed since we started watching it.

Does Lockbox — API Key Wallet publish a privacy policy?

Yes, the store listing links to a privacy policy.