Ext Ops Panel
Open dashboard
Permissions and history

Is Applitools Eyes browser extension SDK safe to install?

Applitools Eyes browser extension SDK asks for 5 browser permissions and 1 site pattern. We do not audit code and we do not judge intent; what we can show is what the listing declares and whether that has changed while we have been watching.

Applitools Eyes browser extension SDK

Chrome extension by Applitools · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 1 screenshot

Loading from the Chrome Web Store. Open the listing if it does not appear.

At a glance

Facts, not a score: an ad blocker needs every page and a theme needs nothing, so one number would be wrong about both. Each fact links to its detail.

Site access
Access to every site
Data collection
Declares it collects none
Publisher
Trader
Audience
75 users

What data it declares

The developer declares that it does not collect or use your data.

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 does not link 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:

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

Worth knowing

Routine for an extension

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.

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.

How usual this is for its category

In Productivity · Developer, 30% 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 5 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

75 users

Users
+8 since 01.09
63-84 · 31 readings
2026-10-28: released 0.11.12
  1. 2026-09-0167
  2. 2026-09-0265
  3. 2026-09-0366
  4. 2026-09-0463
  5. 2026-09-0665
  6. 2026-09-0764
  7. 2026-09-0966
  8. 2026-09-1065
  9. 2026-09-1368
  10. 2026-09-1571
  11. 2026-09-2073
  12. 2026-09-2274
  13. 2026-09-2571
  14. 2026-09-2772
  15. 2026-10-0877
  16. 2026-10-0980
  17. 2026-10-1077
  18. 2026-10-1178
  19. 2026-10-1379
  20. 2026-10-1677
  21. 2026-10-1782
  22. 2026-10-1881
  23. 2026-10-1982
  24. 2026-10-2184
  25. 2026-10-2283
  26. 2026-10-2381
  27. 2026-10-2480
  28. 2026-10-2577
  29. 2026-10-2779
  30. 2026-10-2983
  31. 2026-10-3175

What the store shows

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.

Versions we have seen

  1. Version 0.11.12

Who publishes it

Applitools, who publishes 2 listings we track. This listing has been in the store since 2026-04-03 and was last updated on 2026-10-28.

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. BrowserStack Access to specific sites only · 3 permissions, 1 site pattern 100k users ★ 2.7
  2. Bugsmash Access to specific sites only · 5 permissions, 5 site patterns 2 users (last published figure)
  3. AutoQAI: AI Browser Testing via MCP Runs its code on every site · 5 permissions, 1 site pattern 14 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 Applitools Eyes browser extension SDK access?
Every site you visit. This extension can read and change the content of any page you open. It declares 5 browser permissions.
What data does Applitools Eyes browser extension SDK collect?
The developer declares that it does not collect or use your data. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Applitools Eyes browser extension SDK asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Applitools Eyes browser extension SDK publish a privacy policy?
No, the store listing does not link to a privacy policy.

We read the public store listing up to 2 times a day and keep what it declared. We do not install the extension, do not audit its code, do not judge its intent and publish no contact details for its developer. Last read on 2026-10-31.

Back to Applitools Eyes browser extension SDK · Alternatives to Applitools Eyes browser extension SDK

Where the data comes from: how the catalog is built