Ext Ops Panel
Open dashboard
Permissions and history

Is Wikidocs Enhancer safe to install?

Wikidocs Enhancer asks for no browser permissions and 1 site pattern. 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.

Wikidocs Enhancer

Chrome extension by 박재형 · Productivity · Tools

Open in the Chrome Web Store
What the developer says, and 2 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 specific sites only
Data collection
Declares it collects none
Publisher
No store badges
Audience
35 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 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

Specific sites only: 1 match pattern.

We have not read this listing's manifest since we started keeping permission names. The counts on the card come from the last time we did.

Pages it runs its code on

It runs its own code on specific pages only: 2 site patterns.

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 · Tools, 20% of extensions ask for access to every site. This one: Access to specific sites only.

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

35 users

Users
+3 since 01.09
28-36 · 29 readings
  1. 2026-09-0132
  2. 2026-09-0233
  3. 2026-09-0434
  4. 2026-09-0536
  5. 2026-09-0935
  6. 2026-09-1034
  7. 2026-09-1330
  8. 2026-09-1631
  9. 2026-09-2034
  10. 2026-09-2528
  11. 2026-09-2629
  12. 2026-10-0432
  13. 2026-10-0831
  14. 2026-10-0930
  15. 2026-10-1031
  16. 2026-10-1333
  17. 2026-10-1635
  18. 2026-10-1836
  19. 2026-10-1935
  20. 2026-10-2034
  21. 2026-10-2131
  22. 2026-10-2233
  23. 2026-10-2335
  24. 2026-10-2532
  25. 2026-10-2634
  26. 2026-10-2833
  27. 2026-10-2931
  28. 2026-10-3035
  29. 2026-10-3135

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

박재형, who publishes 16 listings we track. This listing has been in the store since 2024-01-12 and was last updated on 2024-03-20.

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. MD Document Hub No permissions at all · No permissions declared 10 users
  2. mdEdit Runs its code on every site · 1 permission 10 users
  3. MD WYSIWYG Editor No site access · 2 permissions 97 users

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 Wikidocs Enhancer access?
Specific sites only: 1 match pattern. It declares no browser permissions.
What data does Wikidocs Enhancer 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 Wikidocs Enhancer asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Wikidocs Enhancer 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 Wikidocs Enhancer · Alternatives to Wikidocs Enhancer

Where the data comes from: how the catalog is built