Ext Ops Panel
Open dashboard
Permissions and history

Is MSU Theme 1600X900 safe to install?

MSU Theme 1600X900 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.

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
No permissions at all
Publisher
No store badges
Audience
294 users · 4.8/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.

Who uses it and how it is kept up

294 users

Users
+14 since 31.08
272-304 · 41 readings
  1. 2026-08-31280
  2. 2026-09-02286
  3. 2026-09-05285
  4. 2026-09-06283
  5. 2026-09-07273
  6. 2026-09-08272
  7. 2026-09-09276
  8. 2026-09-13275
  9. 2026-09-15286
  10. 2026-09-17287
  11. 2026-09-21300
  12. 2026-09-25286
  13. 2026-09-26282
  14. 2026-09-28281
  15. 2026-10-05296
  16. 2026-10-08304
  17. 2026-10-09302
  18. 2026-10-10293
  19. 2026-10-13285
  20. 2026-10-14285
  21. 2026-10-16280
  22. 2026-10-18284
  23. 2026-10-19291
  24. 2026-10-20298
  25. 2026-10-21294
  26. 2026-10-22295
  27. 2026-10-23290
  28. 2026-10-24287
  29. 2026-10-25292
  30. 2026-10-28294
  31. 2026-10-29292
  32. 2026-10-30299
  33. 2026-11-01293
  34. 2026-11-04282
  35. 2026-11-06287
  36. 2026-11-07291
  37. 2026-11-08297
  38. 2026-11-10294
  39. 2026-11-11291
  40. 2026-11-14296
  41. 2026-11-15294

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

benblaut, who publishes 3 listings we track. This listing has been in the store since 2011-01-26 and was last updated on 2012-01-31.

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 MSU Theme 1600X900 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 MSU Theme 1600X900 collect?
The listing carries no declaration about the data it collects.
Has MSU Theme 1600X900 asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does MSU Theme 1600X900 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-15.

Back to MSU Theme 1600X900 · Alternatives to MSU Theme 1600X900

Where the data comes from: how the catalog is built