Ext Ops Panel
Open dashboard
Permissions and history

Is Web Highlighter safe to install?

Web Highlighter asks for 5 browser permissions and declares no blanket site access. 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.

Web Highlighter

Chrome extension by vaishak.k.nair · Productivity · Workflow

Open in the Chrome Web Store
What the developer says, and 5 screenshots

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.

Data collection
Declares it collects none
Audience
41 users · 5.0/5

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

No site access is declared in the manifest, so it cannot read the pages you open on its own.

Reaches your browsing data or every site

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.

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.

How usual this is for its category

In Productivity · Workflow, 19% of extensions ask for access to every site. This one: Runs its code on 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

41 users

Users
+30 since 01.09
11-41 · 24 readings
2026-09-02: released 0.0.0.92026-09-09: released 0.0.1.02026-09-11: released 0.0.1.12026-09-17: released 0.0.1.22026-09-18: released 0.0.1.32026-10-11: released 0.0.1.42026-10-16: released 0.0.1.52026-10-22: released 0.0.1.62026-10-24: released 0.0.1.7
  1. 2026-09-0111
  2. 2026-09-0312
  3. 2026-09-0614
  4. 2026-09-0713
  5. 2026-09-0816
  6. 2026-09-1315
  7. 2026-09-1514
  8. 2026-09-2020
  9. 2026-09-2219
  10. 2026-09-2529
  11. 2026-09-2830
  12. 2026-10-0434
  13. 2026-10-0936
  14. 2026-10-1035
  15. 2026-10-1336
  16. 2026-10-1634released 0.0.1.5
  17. 2026-10-1735
  18. 2026-10-1836
  19. 2026-10-1935
  20. 2026-10-2037
  21. 2026-10-2439released 0.0.1.7
  22. 2026-10-2539
  23. 2026-10-2940
  24. 2026-10-3041

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.

  1. Asked for fewer permissions (5, was 9) (changed: browser permissions, optional permissions)

Versions we have seen

  1. Version 0.0.1.7
  2. Version 0.0.1.6 · Asked for fewer permissions (5, was 9) (changed: browser permissions, optional permissions)
  3. Version 0.0.1.5
  4. Version 0.0.1.4
  5. Version 0.0.1.3
  6. Version 0.0.1.2
  7. Version 0.0.1.1

Who publishes it

vaishak.k.nair, who publishes 2 listings we track. This listing has been in the store since 2026-04-27 and was last updated on 2026-10-24.

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 Web Highlighter access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 5 browser permissions.
What data does Web Highlighter 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 Web Highlighter asked for more permissions over time?
Its permissions changed once while we watched, on 2026-10-22.
Does Web Highlighter 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-30.

Back to Web Highlighter · Alternatives to Web Highlighter

Where the data comes from: how the catalog is built