Ext Ops Panel
Open dashboard
Permissions and history

Is Hover Debug Overlay safe to install?

Hover Debug Overlay 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.

Hover Debug Overlay

Chrome extension by aman_lakhuja · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 4 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.

Site access
No site access
Data collection
Declares it collects none
Publisher
No store badges
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 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:

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.

Worth knowing

Routine for an extension

How usual this is for its category

In Productivity · Developer, 30% of extensions ask for access to every site. This one: No site access.

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
+16 since 01.09
25-42 · 28 readings
  1. 2026-09-0125
  2. 2026-09-0232
  3. 2026-09-0431
  4. 2026-09-0532
  5. 2026-09-0633
  6. 2026-09-0731
  7. 2026-09-0932
  8. 2026-09-1333
  9. 2026-09-1536
  10. 2026-09-2033
  11. 2026-09-2132
  12. 2026-09-2734
  13. 2026-10-0436
  14. 2026-10-0833
  15. 2026-10-0934
  16. 2026-10-1033
  17. 2026-10-1332
  18. 2026-10-1634
  19. 2026-10-1736
  20. 2026-10-1839
  21. 2026-10-2040
  22. 2026-10-2239
  23. 2026-10-2342
  24. 2026-10-2440
  25. 2026-10-2841
  26. 2026-10-3040
  27. 2026-11-0141
  28. 2026-11-0241

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

aman_lakhuja. This listing has been in the store since 2025-08-21 and was last updated on 2025-08-21.

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. Element Inspect Runs its code on every site · 1 permission 202 users ★ 5.0
  2. CSS Debugger Runs its code on every site · 2 permissions 36 users
  3. CSS Debugger Runs its code on every site · 2 permissions 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 Hover Debug Overlay 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 Hover Debug Overlay 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 Hover Debug Overlay asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Hover Debug Overlay publish a privacy policy?
Yes, the store listing links 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-11-02.

Back to Hover Debug Overlay · Alternatives to Hover Debug Overlay

Where the data comes from: how the catalog is built