Is Akeyless SA 2.0 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
• Personal communications such as emails, texts or chat messages
• Website content such as text, images or links on the pages you open

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 all your data on all websites
• Read your browsing history
• Modify data you copy and paste
• Manage your downloads
• Block content on any page
• Manage your apps, extensions, and themes
• Read 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

Every site you visit. This extension can read and change the content of any page you open. What access to every site means

Reaches your browsing data or every site

• Read what you have copied clipboardRead
• Attach to pages the way developer tools do debugger
• See, enable and disable your other extensions management
• Change which proxy your browser connects through proxy
• See the address and title of every tab you have open tabs
• Handle security-key sign-ins on your behalf webAuthenticationProxy
• Watch the network requests your browser makes webRequest

Worth knowing

• Block or redirect requests by rules it declares in advance declarativeNetRequest
• Block or redirect requests on the sites it can access declarativeNetRequestWithHostAccess
• Manage your downloads downloads
• Run its own code on the pages it can access scripting
• See when you navigate between pages webNavigation

Routine for an extension

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

Pages it runs its code on

It runs its own code on every page you open: the manifest declares a content script for all sites.

• https://auth.akeyless.io/* only auth.akeyless.io
• https://auth.us.akeyless.io/* only auth.us.akeyless.io
• https://auth.eu.akeyless.io/* only auth.eu.akeyless.io

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.

Sites that can connect to it

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

• http://localhost/* only localhost
• http://127.0.0.1/* only 127.0.0.1
• https://console-pwm.akeyless.dev/* only console-pwm.akeyless.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 Make Chrome Yours · Privacy, 42% of extensions ask for access to every site. This one: Access to every site.

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

• Read what you have copied (clipboardRead): 2% of extensions in this category ask for it.
• Attach to pages the way developer tools do (debugger): under 1% of extensions in this category ask for it.
• See, enable and disable your other extensions (management): 4% of extensions in this category ask for it.
• Change which proxy your browser connects through (proxy): 14% of extensions in this category ask for it.
• See the address and title of every tab you have open (tabs): 32% of extensions in this category ask for it.
• Handle security-key sign-ins on your behalf (webAuthenticationProxy): under 1% of extensions in this category ask for it.
• Watch the network requests your browser makes (webRequest): 14% of extensions in this category ask for it.

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

139 users

• Last updated in the store 2 days ago, on 2026-10-31.
• We have seen 9 new versions 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.

1. 2026-10-15Asked for more permissions (44, was 42) (changed: browser permissions)

Versions we have seen

1. 2026-11-01Version 1.30.141
2. 2026-10-28Version 1.30.139
3. 2026-10-26Version 1.30.138
4. 2026-10-25Version 1.30.137
5. 2026-10-25Version 1.30.136
6. 2026-10-22Version 1.30.135
7. 2026-10-20Version 1.30.134
8. 2026-10-19Version 1.30.133

Who publishes it

akeyless.io, who publishes 2 listings we track. This listing has been in the store since 2026-04-13 and was last updated on 2026-10-31.

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. OpsTools SecretVault Runs its code on every site · 3 permissions, 4 site patterns 3 users
2. SatisVAULT Runs its code on every site · 4 permissions, 4 site patterns 12 users ★ 5.0
3. Azure Key Vault Password Manager Runs its code on every site · 4 permissions, 2 site patterns 7 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 Akeyless SA 2.0 access?

Every site you visit. This extension can read and change the content of any page you open. It declares 19 browser permissions.

What data does Akeyless SA 2.0 collect?

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

Has Akeyless SA 2.0 asked for more permissions over time?

Its permissions changed once while we watched, on 2026-10-15.

Does Akeyless SA 2.0 publish a privacy policy?

Yes, the store listing links to a privacy policy.