Ext Ops Panel
Open dashboard
Permissions and history

Is Netmediablog safe to install?

Netmediablog declares no browser permissions and no site access in its manifest, which is as narrow as an extension gets. 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.

Netmediablog

Chrome Web Store listing by inetmediablog · Lifestyle · Social

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.

Site access
No permissions at all
Audience
35 users · 2.0/5

What data it declares

The listing carries no declaration about the data it collects.

The listing does not link to a privacy policy.

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.

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.

How usual this is for its category

In Lifestyle · Social, 8% of extensions ask for access to every site. This one: No permissions at all.

The typical extension there declares 2 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
+1 since 31.08
26-37 · 28 readings
  1. 2026-08-3134
  2. 2026-09-0436
  3. 2026-09-0634
  4. 2026-09-0730
  5. 2026-09-0931
  6. 2026-09-1029
  7. 2026-09-1531
  8. 2026-09-2036
  9. 2026-09-2134
  10. 2026-09-2536
  11. 2026-09-2637
  12. 2026-09-2836
  13. 2026-10-0531
  14. 2026-10-0828
  15. 2026-10-0931
  16. 2026-10-1333
  17. 2026-10-1632
  18. 2026-10-1831
  19. 2026-10-1927
  20. 2026-10-2126
  21. 2026-10-2227
  22. 2026-10-2329
  23. 2026-10-2431
  24. 2026-10-2532
  25. 2026-10-2829
  26. 2026-11-0134
  27. 2026-11-0335
  28. 2026-11-0435

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

inetmediablog. This listing has been in the store since 2014-02-17 and was last updated on 2014-09-05.

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

Back to Netmediablog · Alternatives to Netmediablog

Where the data comes from: how the catalog is built