Ext Ops Panel
Open dashboard
Permissions and history

Is Web Apps safe to install?

Web Apps 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.

Web Apps

Chrome extension by Pothos · Make Chrome Yours · Functionality

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
No site access
Data collection
Declares it collects none
Audience
505 users · 4.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

From the permissions it declares, Chrome shows no permission warning when you add it.

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

Sites that can connect to it

Web pages matching these patterns can open a messaging channel to it: 1 site pattern.

Declared as externally connectable in the manifest: a page on these sites can exchange messages with the extension, for example to tell it you have signed in. It does not give the page access to your browser.

How usual this is for its category

In Make Chrome Yours · Functionality, 12% of extensions ask for access to every site. This one: No site access.

The typical extension there declares 2 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

505 users

Users
+67 since 01.09
438-561 · 35 readings
  1. 2026-09-01438
  2. 2026-09-02443
  3. 2026-09-03442
  4. 2026-09-04447
  5. 2026-09-06467
  6. 2026-09-07461
  7. 2026-09-10463
  8. 2026-09-13461
  9. 2026-09-15460
  10. 2026-09-16463
  11. 2026-09-21516
  12. 2026-09-22527
  13. 2026-09-25548
  14. 2026-09-26545
  15. 2026-09-28540
  16. 2026-10-05561
  17. 2026-10-08539
  18. 2026-10-09531
  19. 2026-10-10504
  20. 2026-10-13513
  21. 2026-10-16494
  22. 2026-10-17500
  23. 2026-10-18506
  24. 2026-10-19507
  25. 2026-10-20499
  26. 2026-10-21504
  27. 2026-10-22507
  28. 2026-10-23521
  29. 2026-10-24515
  30. 2026-10-25511
  31. 2026-10-28524
  32. 2026-10-29522
  33. 2026-10-30510
  34. 2026-11-01505
  35. 2026-11-02505

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

Pothos, who publishes 19 listings we track. This listing has been in the store since 2026-03-04 and was last updated on 2026-08-28.

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. Assistive Button Runs its code on every site · No permissions declared 3 users (last published figure)

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 Web Apps 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 Web Apps 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 Web Apps asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Web Apps 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-02.

Back to Web Apps · Alternatives to Web Apps

Where the data comes from: how the catalog is built