Ext Ops Panel
Open dashboard
Permissions and history

Is ByeAI: Block AI on the Web safe to install?

ByeAI: Block AI on the Web asks for 5 browser permissions and 2 site patterns. 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.

ByeAI: Block AI on the Web

Chrome extension by Elsama · Productivity · Workflow

Open in the Chrome Web Store
What the developer says, and 3 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 every site
Data collection
1 kind of data declared
Publisher
No store badges
Audience
220 users · 3.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

Every site you visit. This extension can read and change the content of any page you open. What access to every site means

Worth knowing

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.

Show the remaining 3
  • *://*.duckduckgo.com/* duckduckgo.com and all its subdomains
  • *://*.search.brave.com/* search.brave.com and all its subdomains
  • *://*.ecosia.org/* ecosia.org and all its subdomains

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: Access to 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

220 users

Users
+157 since 31.08
63-220 · 40 readings
2026-10-19: released 1.2.12026-10-23: released 1.3.02026-10-26: released 1.4.1
  1. 2026-08-3163
  2. 2026-09-0270
  3. 2026-09-0672
  4. 2026-09-0770
  5. 2026-09-0872
  6. 2026-09-1069
  7. 2026-09-1370
  8. 2026-09-1575
  9. 2026-09-1774
  10. 2026-09-2088
  11. 2026-09-2189
  12. 2026-09-2591
  13. 2026-09-2892
  14. 2026-10-0495
  15. 2026-10-0897
  16. 2026-10-1093
  17. 2026-10-1392
  18. 2026-10-16103
  19. 2026-10-18104
  20. 2026-10-19103released 1.2.1
  21. 2026-10-20102
  22. 2026-10-21108
  23. 2026-10-22103
  24. 2026-10-23114released 1.3.0
  25. 2026-10-24127
  26. 2026-10-25130
  27. 2026-10-26136released 1.4.1
  28. 2026-10-28139
  29. 2026-10-29137
  30. 2026-10-30136
  31. 2026-11-01131
  32. 2026-11-02129
  33. 2026-11-04149
  34. 2026-11-06169
  35. 2026-11-07176
  36. 2026-11-09181
  37. 2026-11-11185
  38. 2026-11-14213
  39. 2026-11-15216
  40. 2026-11-17220

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. Asked for more permissions (7, was 6) (changed: browser permissions)
  2. Asked for fewer permissions (6, was 7) (changed: browser permissions)

Versions we have seen

  1. Version 1.4.1
  2. Version 1.3.0 · Asked for more permissions (7, was 6) (changed: browser permissions)
  3. Version 1.2.1 · Asked for fewer permissions (6, was 7) (changed: browser permissions)

Who publishes it

Elsama. This listing has been in the store since 2026-06-01 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. AI Content Blocker No permissions at all · No permissions declared 213 users (last published figure)
  2. AI Blocker Runs its code on every site · 2 permissions, 50 site patterns 4 users
  3. AI Content Shield - Hide AI Overviews & AI Mode | AI Content Blocker Runs its code on every site · 4 permissions, 3 site patterns 20k users ★ 4.5

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 ByeAI: Block AI on the Web access?
Every site you visit. This extension can read and change the content of any page you open. It declares 5 browser permissions.
What data does ByeAI: Block AI on the Web collect?
The developer declares that it collects these kinds of data: Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has ByeAI: Block AI on the Web asked for more permissions over time?
Its permissions changed 2 times while we watched, most recently on 2026-10-23.
Does ByeAI: Block AI on the Web 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-17.

Back to ByeAI: Block AI on the Web · Alternatives to ByeAI: Block AI on the Web

Where the data comes from: how the catalog is built