Ext Ops Panel
Open dashboard
Permissions and history

Is Yapee safe to install?

Yapee asks for 6 browser permissions 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.

Yapee

Chrome extension by JeromeSoyer · Productivity · Workflow

Open in the Chrome Web Store
What the developer says, and 1 screenshot

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.

Data collection
Declares it collects none
Upkeep
Updated 230 days ago
Publisher
No store badges
Audience
40 users

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 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

No site access is declared in the manifest, so it cannot read the pages you open on its own.

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.

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.

What it may ask for later

Not granted when you add it: Chrome asks you the moment the extension requests one of these, and you can refuse.

Sites that can connect to it

Web pages matching these patterns can open a messaging channel to it: the first 50 site patterns we keep.

Show the remaining 47
  • *://*.4shared.com/* 4shared.com and all its subdomains
  • *://alfafile.net/* only alfafile.net
  • *://*.alfafile.net/* alfafile.net and all its subdomains
  • *://alldebrid.com/* only alldebrid.com
  • *://*.alldebrid.com/* alldebrid.com and all its subdomains
  • *://clicknupload.com/* only clicknupload.com
  • *://*.clicknupload.com/* clicknupload.com and all its subdomains
  • *://cloud.mail.ru/* only cloud.mail.ru
  • *://debrid.it/* only debrid.it
  • *://*.debrid.it/* debrid.it and all its subdomains
  • *://debrid.link/* only debrid.link
  • *://*.debrid.link/* debrid.link and all its subdomains
  • *://depositfiles.com/* only depositfiles.com
  • *://*.depositfiles.com/* depositfiles.com and all its subdomains
  • *://dfiles.eu/* only dfiles.eu
  • *://*.dfiles.eu/* dfiles.eu and all its subdomains
  • *://dropbox.com/* only dropbox.com
  • *://*.dropbox.com/* dropbox.com and all its subdomains
  • *://drive.google.com/* only drive.google.com
  • *://docs.google.com/* only docs.google.com
  • *://easyupload.io/* only easyupload.io
  • *://*.easyupload.io/* easyupload.io and all its subdomains
  • *://fboom.me/* only fboom.me
  • *://*.fboom.me/* fboom.me and all its subdomains
  • *://fileboom.me/* only fileboom.me
  • *://*.fileboom.me/* fileboom.me and all its subdomains
  • *://filecloud.io/* only filecloud.io
  • *://*.filecloud.io/* filecloud.io and all its subdomains
  • *://filefactory.com/* only filefactory.com
  • *://*.filefactory.com/* filefactory.com and all its subdomains
  • *://filejoker.net/* only filejoker.net
  • *://*.filejoker.net/* filejoker.net and all its subdomains
  • *://fshare.vn/* only fshare.vn
  • *://*.fshare.vn/* fshare.vn and all its subdomains
  • *://gofile.io/* only gofile.io
  • *://*.gofile.io/* gofile.io and all its subdomains
  • *://k2s.cc/* only k2s.cc
  • *://*.k2s.cc/* k2s.cc and all its subdomains
  • *://keep2share.cc/* only keep2share.cc
  • *://*.keep2share.cc/* keep2share.cc and all its subdomains
  • *://krakenfiles.com/* only krakenfiles.com
  • *://*.krakenfiles.com/* krakenfiles.com and all its subdomains
  • *://mega.nz/* only mega.nz
  • *://mega.co.nz/* only mega.co.nz
  • *://mediafire.com/* only mediafire.com
  • *://*.mediafire.com/* mediafire.com and all its subdomains
  • *://mp4upload.com/* only mp4upload.com

We keep the first 50 patterns of a list; the manifest may declare more.

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

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

40 users

Users
+20 since 01.09
17-42 · 35 readings
  1. 2026-09-0120
  2. 2026-09-0321
  3. 2026-09-0417
  4. 2026-09-0618
  5. 2026-09-0720
  6. 2026-09-1021
  7. 2026-09-1324
  8. 2026-09-1527
  9. 2026-09-1629
  10. 2026-09-2025
  11. 2026-09-2526
  12. 2026-09-2628
  13. 2026-09-2829
  14. 2026-10-0433
  15. 2026-10-0835
  16. 2026-10-0937
  17. 2026-10-1034
  18. 2026-10-1336
  19. 2026-10-1637
  20. 2026-10-1835
  21. 2026-10-1938
  22. 2026-10-2139
  23. 2026-10-2240
  24. 2026-10-2341
  25. 2026-10-2440
  26. 2026-10-2539
  27. 2026-10-2936
  28. 2026-11-0137
  29. 2026-11-0335
  30. 2026-11-0539
  31. 2026-11-0741
  32. 2026-11-0840
  33. 2026-11-0942
  34. 2026-11-1040
  35. 2026-11-1240

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.

The permissions this extension requests have not changed since we started watching it.

Who publishes it

JeromeSoyer. This listing has been in the store since 2026-03-28 and was last updated on 2026-03-28.

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 Yapee access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 6 browser permissions.
What data does Yapee 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 Yapee asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Yapee 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-12.

Back to Yapee · Alternatives to Yapee

Where the data comes from: how the catalog is built