Ext Ops Panel
Open dashboard
Permissions and history

Is Codeforces Better Comments safe to install?

Codeforces Better Comments 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.

Codeforces Better Comments

Chrome extension by Ishan Joshi · Productivity · Workflow

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
Featured
Audience
625 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.

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 · Workflow, 19% of extensions ask for access to every site. This one: No site access.

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

625 users

Users
+45 since 01.09
580-643 · 43 readings
  1. 2026-09-01580
  2. 2026-09-03585
  3. 2026-09-04594
  4. 2026-09-06604
  5. 2026-09-07613
  6. 2026-09-08611
  7. 2026-09-10606
  8. 2026-09-13602
  9. 2026-09-15606
  10. 2026-09-16599
  11. 2026-09-20625
  12. 2026-09-21613
  13. 2026-09-25598
  14. 2026-09-26593
  15. 2026-09-28592
  16. 2026-10-05599
  17. 2026-10-08584
  18. 2026-10-09595
  19. 2026-10-10609
  20. 2026-10-11608
  21. 2026-10-13623
  22. 2026-10-16622
  23. 2026-10-17625
  24. 2026-10-18632
  25. 2026-10-19631
  26. 2026-10-21639
  27. 2026-10-22643
  28. 2026-10-23635
  29. 2026-10-24621
  30. 2026-10-26620
  31. 2026-10-28611
  32. 2026-10-29613
  33. 2026-10-30615
  34. 2026-11-01612
  35. 2026-11-02614
  36. 2026-11-04603
  37. 2026-11-06610
  38. 2026-11-07617
  39. 2026-11-08619
  40. 2026-11-09623
  41. 2026-11-10618
  42. 2026-11-11625
  43. 2026-11-12625

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

Ishan Joshi. This listing has been in the store since 2023-08-15 and was last updated on 2024-12-30.

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. cfLikeDislike No permissions at all · No permissions declared 7 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 Codeforces Better Comments 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 Codeforces Better Comments 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 Codeforces Better Comments asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Codeforces Better Comments 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-12.

Back to Codeforces Better Comments · Alternatives to Codeforces Better Comments

Where the data comes from: how the catalog is built