Ext Ops Panel
Open dashboard
Permissions and history

Is Font Detector safe to install?

Font Detector asks for 1 browser permission 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.

Font Detector

Chrome extension by fontfindertool · 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.

Data collection
Declares it collects none
Publisher
Featured
Audience
73 users · 1.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.

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: Runs its code on every site.

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

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

73 users

Users
+2 since 31.08
71-81 · 40 readings
  1. 2026-08-3171
  2. 2026-09-0277
  3. 2026-09-0479
  4. 2026-09-0581
  5. 2026-09-0679
  6. 2026-09-0877
  7. 2026-09-1076
  8. 2026-09-1374
  9. 2026-09-1575
  10. 2026-09-2072
  11. 2026-09-2273
  12. 2026-09-2574
  13. 2026-09-2678
  14. 2026-09-2877
  15. 2026-10-0578
  16. 2026-10-0874
  17. 2026-10-0977
  18. 2026-10-1077
  19. 2026-10-1379
  20. 2026-10-1776
  21. 2026-10-1879
  22. 2026-10-1977
  23. 2026-10-2073
  24. 2026-10-2175
  25. 2026-10-2276
  26. 2026-10-2377
  27. 2026-10-2479
  28. 2026-10-2579
  29. 2026-10-2877
  30. 2026-10-2975
  31. 2026-10-3079
  32. 2026-11-0177
  33. 2026-11-0476
  34. 2026-11-0674
  35. 2026-11-0779
  36. 2026-11-0877
  37. 2026-11-1076
  38. 2026-11-1177
  39. 2026-11-1476
  40. 2026-11-1573

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.

Who publishes it

fontfindertool, who publishes 4 listings we track. This listing has been in the store since 2023-04-18 and was last updated on 2023-05-01.

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. FontLab - Hover to Detect Fonts Properties Runs its code on every site · No permissions declared 18 users ★ 5.0

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 Font Detector access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 1 browser permission.
What data does Font Detector 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 Font Detector asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Font Detector 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-11-15.

Back to Font Detector · Alternatives to Font Detector

Where the data comes from: how the catalog is built