Ext Ops Panel
Open dashboard
Permissions and history

Is App Store Meta Editor safe to install?

App Store Meta Editor asks for 2 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.

App Store Meta Editor

Chrome extension · Productivity · Developer

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
Access to specific sites only
Data collection
Declares it collects none
Publisher
No store badges
Audience
456 users · 4.6/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 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

Specific sites only: 1 match pattern.

Worth knowing

Routine for an extension

How usual this is for its category

In Productivity · Developer, 30% 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 2 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

456 users

Users
+19 since 31.08
418-468 · 35 readings
  1. 2026-08-31437
  2. 2026-09-02428
  3. 2026-09-04418
  4. 2026-09-07423
  5. 2026-09-08425
  6. 2026-09-10432
  7. 2026-09-13446
  8. 2026-09-15456
  9. 2026-09-16451
  10. 2026-09-21445
  11. 2026-09-25447
  12. 2026-09-27439
  13. 2026-09-28445
  14. 2026-10-04461
  15. 2026-10-08465
  16. 2026-10-09463
  17. 2026-10-10461
  18. 2026-10-13468
  19. 2026-10-16461
  20. 2026-10-18455
  21. 2026-10-19458
  22. 2026-10-21468
  23. 2026-10-23467
  24. 2026-10-24466
  25. 2026-10-25458
  26. 2026-10-29460
  27. 2026-11-01448
  28. 2026-11-03453
  29. 2026-11-06456
  30. 2026-11-07458
  31. 2026-11-08456
  32. 2026-11-09452
  33. 2026-11-11451
  34. 2026-11-14456
  35. 2026-11-15456

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

The store lists no publisher name. This listing has been in the store since 2024-03-23 and was last updated on 2025-06-27.

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. Locale Hotkeys for App Store Connect No permissions at all · No permissions declared 3 users
  2. Multi-language Release Notes Copier for Apple App Store Connect No site access · 2 permissions 6 users (last published figure) ★ 5.0
  3. What's New Auto-Translate Access to specific sites only · 1 permission, 2 site patterns 10 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 App Store Meta Editor access?
Specific sites only: 1 match pattern. It declares 2 browser permissions.
What data does App Store Meta Editor 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 App Store Meta Editor asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does App Store Meta Editor 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-15.

Back to App Store Meta Editor · Alternatives to App Store Meta Editor

Where the data comes from: how the catalog is built