Ext Ops Panel
Open dashboard
Permissions and history

Is Codex Usage safe to install?

Codex Usage asks for 2 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.

Codex Usage

Chrome extension by Bro Extension · Productivity · Tools

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.

Site access
Access to specific sites only
Data collection
3 kinds of data declared
Publisher
No store badges
Audience
499 users · 5.0/5

What data it declares

The developer declares that it collects these kinds of 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

Specific sites only: 1 match pattern.

Routine for an extension

Pages it runs its code on

It runs its own code on specific pages only: 1 site pattern.

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 · Tools, 20% of extensions ask for access to every site. This one: Access to specific sites only.

The typical extension there declares 3 browser permissions; this one declares 2 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

499 users

Users
+448 since 31.08
51-499 · 38 readings
2026-09-03: released 1.6.12026-10-26: released 1.6.2
  1. 2026-08-3151
  2. 2026-09-0256
  3. 2026-09-0559
  4. 2026-09-0768
  5. 2026-09-0970
  6. 2026-09-1380
  7. 2026-09-1582
  8. 2026-09-1788
  9. 2026-09-20118
  10. 2026-09-21123
  11. 2026-09-25138
  12. 2026-09-27156
  13. 2026-09-28170
  14. 2026-10-04217
  15. 2026-10-08233
  16. 2026-10-09237
  17. 2026-10-10251
  18. 2026-10-13256
  19. 2026-10-16294
  20. 2026-10-18326
  21. 2026-10-19339
  22. 2026-10-21344
  23. 2026-10-22362
  24. 2026-10-23378
  25. 2026-10-24387
  26. 2026-10-25382
  27. 2026-10-28391
  28. 2026-10-29400
  29. 2026-11-01409
  30. 2026-11-03416
  31. 2026-11-06427
  32. 2026-11-07444
  33. 2026-11-08455
  34. 2026-11-09458
  35. 2026-11-10469
  36. 2026-11-14487
  37. 2026-11-16499
  38. 2026-11-18499

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. Changed where it works (changed: pages it runs its code on)

Versions we have seen

  1. Version 1.6.2 · Changed where it works (changed: pages it runs its code on)
  2. Version 1.6.1

Who publishes it

Bro Extension. This listing has been in the store since 2026-08-12 and was last updated on 2026-10-26.

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. Codex Usage Tracker No site access · 1 permission 541 users ★ 3.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 Codex Usage access?
Specific sites only: 1 match pattern. It declares 2 browser permissions.
What data does Codex Usage collect?
The developer declares that it collects these kinds of data: Personally identifiable information, Authentication information, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Codex Usage asked for more permissions over time?
Its permissions changed once while we watched, on 2026-10-26.
Does Codex Usage 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-18.

Back to Codex Usage · Alternatives to Codex Usage

Where the data comes from: how the catalog is built