Ext Ops Panel
Open dashboard
Permissions and history

Is Full Page Screenshot – Auto Screen Shooter safe to install?

Full Page Screenshot – Auto Screen Shooter asks for 8 browser permissions and 2 site patterns. 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.

Full Page Screenshot – Auto Screen Shooter

Chrome extension by amiplay · Productivity · Tools

Open in the Chrome Web Store
What the developer says, and 5 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
Upkeep
Updated 151 days ago
Audience
356 users · 5.0/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: 2 match patterns.

Reaches your browsing data or every site

Worth knowing

Routine for an extension

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

356 users

Users
+257 since 01.09
99-356 · 35 readings
2026-09-30: gained the good publisher record badge
  1. 2026-09-0199
  2. 2026-09-02101
  3. 2026-09-05105
  4. 2026-09-06107
  5. 2026-09-07114
  6. 2026-09-09134
  7. 2026-09-10153
  8. 2026-09-13186
  9. 2026-09-15204
  10. 2026-09-17219
  11. 2026-09-20234
  12. 2026-09-21242
  13. 2026-09-25245
  14. 2026-09-27253
  15. 2026-09-28255
  16. 2026-10-04285
  17. 2026-10-08295
  18. 2026-10-09300
  19. 2026-10-10303
  20. 2026-10-11302
  21. 2026-10-13306
  22. 2026-10-16310
  23. 2026-10-17318
  24. 2026-10-18323
  25. 2026-10-19327
  26. 2026-10-20330
  27. 2026-10-21335
  28. 2026-10-22336
  29. 2026-10-24341
  30. 2026-10-25340
  31. 2026-10-26345
  32. 2026-10-28349
  33. 2026-10-29352
  34. 2026-11-01356
  35. 2026-11-03356

What the store shows

The listing says it offers in-app purchases.

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

amiplay, who publishes 3 listings we track. This listing has been in the store since 2026-05-11 and was last updated on 2026-06-05.

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. Fullpage Screenshot No site access · 2 permissions 7 users
  2. FullShot Pro — Full Page Screenshot & PDF No site access · 3 permissions 10 users
  3. PageMuncher by MENDSTER No site access · 4 permissions 8 users (last published figure) ★ 5.0

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 Full Page Screenshot – Auto Screen Shooter access?
Specific sites only: 2 match patterns. It declares 8 browser permissions.
What data does Full Page Screenshot – Auto Screen Shooter 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 Full Page Screenshot – Auto Screen Shooter asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Full Page Screenshot – Auto Screen Shooter 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-03.

Back to Full Page Screenshot – Auto Screen Shooter · Alternatives to Full Page Screenshot – Auto Screen Shooter

Where the data comes from: how the catalog is built