Ext Ops Panel
Open dashboard
Permissions and history

Is Multi-Email/App Taskbar/Dock PWA Unread Badge safe to install?

Multi-Email/App Taskbar/Dock PWA Unread Badge 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.

Multi-Email/App Taskbar/Dock PWA Unread Badge

Chrome extension by Ocfinity (Jared) · 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
No site access
Data collection
Declares it collects none
Upkeep
Updated 242 days ago
Publisher
Featured
Audience
407 users · 3.7/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: 10 site patterns.

Show the remaining 7
  • *://outlook.office365.com/mail/* only outlook.office365.com
  • *://outlook.office.com/mail/* only outlook.office.com
  • *://outlook.cloud.microsoft/mail/* only outlook.cloud.microsoft
  • *://outlook.live.com/calendar/* only outlook.live.com
  • *://outlook.office365.com/calendar/* only outlook.office365.com
  • *://outlook.office.com/calendar/* only outlook.office.com
  • *://app.slack.com/* only app.slack.com

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

407 users

Users
+26 since 01.09
380-418 · 32 readings
  1. 2026-09-01381
  2. 2026-09-02382
  3. 2026-09-03383
  4. 2026-09-04382
  5. 2026-09-06381
  6. 2026-09-07385
  7. 2026-09-08386
  8. 2026-09-09390
  9. 2026-09-13380
  10. 2026-09-15384
  11. 2026-09-17397
  12. 2026-09-20394
  13. 2026-09-25401
  14. 2026-09-26391
  15. 2026-09-28394
  16. 2026-10-04400
  17. 2026-10-08404
  18. 2026-10-09401
  19. 2026-10-10388
  20. 2026-10-13389
  21. 2026-10-16403
  22. 2026-10-18407
  23. 2026-10-19403
  24. 2026-10-20405
  25. 2026-10-21404
  26. 2026-10-22415
  27. 2026-10-23410
  28. 2026-10-24417
  29. 2026-10-25418
  30. 2026-10-28414
  31. 2026-10-29407
  32. 2026-10-31407

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

Ocfinity (Jared), who publishes 3 listings we track. This listing has been in the store since 2023-01-02 and was last updated on 2026-03-03.

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. Gmail Taskbar Unread Badge No permissions at all · No permissions declared 3k users ★ 4.8

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 Multi-Email/App Taskbar/Dock PWA Unread Badge 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 Multi-Email/App Taskbar/Dock PWA Unread Badge 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 Multi-Email/App Taskbar/Dock PWA Unread Badge asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Multi-Email/App Taskbar/Dock PWA Unread Badge 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-10-31.

Back to Multi-Email/App Taskbar/Dock PWA Unread Badge · Alternatives to Multi-Email/App Taskbar/Dock PWA Unread Badge

Where the data comes from: how the catalog is built