Ext Ops Panel
Open dashboard
Permissions and history

Is FullSnap - Full Page Screen Capture safe to install?

FullSnap - Full Page Screen Capture asks for 5 browser permissions and declares no blanket site access. 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.

FullSnap - Full Page Screen Capture

Chrome extension by mohan · Productivity · Workflow

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.

Data collection
Declares it collects none
Publisher
No store badges
Audience
40 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 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

No site access is declared in the manifest, so it cannot read the pages you open on its own.

Routine for an extension

Pages it runs its code on

It runs its own code on every page you open: the manifest declares a content script for all sites.

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 · Workflow, 19% of extensions ask for access to every site. This one: Runs its code on every site.

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

40 users

Users
+26 since 01.09
14-45 · 36 readings
2026-09-10: removed from the store2026-09-14: released 1.0.32026-09-14: back in the store2026-11-12: released 1.0.4
  1. 2026-09-0114
  2. 2026-09-0315
  3. 2026-09-0416
  4. 2026-09-0520
  5. 2026-09-0621
  6. 2026-09-0723
  7. 2026-09-0828
  8. 2026-09-1437released 1.0.3back in the store
  9. 2026-09-1538
  10. 2026-09-1735
  11. 2026-09-2037
  12. 2026-09-2136
  13. 2026-09-2538
  14. 2026-09-2837
  15. 2026-10-0835
  16. 2026-10-0937
  17. 2026-10-1036
  18. 2026-10-1338
  19. 2026-10-1636
  20. 2026-10-1839
  21. 2026-10-1938
  22. 2026-10-2039
  23. 2026-10-2142
  24. 2026-10-2237
  25. 2026-10-2339
  26. 2026-10-2440
  27. 2026-10-2842
  28. 2026-10-3045
  29. 2026-11-0141
  30. 2026-11-0440
  31. 2026-11-0641
  32. 2026-11-0743
  33. 2026-11-0941
  34. 2026-11-1039
  35. 2026-11-1140
  36. 2026-11-1440

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.

  1. Asked for fewer permissions (5, was 6)

Versions we have seen

  1. Version 1.0.4
  2. Version 1.0.3 · Asked for fewer permissions (5, was 6)

Who publishes it

mohan, who publishes 2 listings we track. This listing has been in the store since 2026-08-20 and was last updated on 2026-11-12.

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. Full Page Screenshot Capture by Sleekins No site access · 2 permissions 7 users ★ 5.0
  2. GetFullPage — Full Page Screenshot No site access · 4 permissions 515 users ★ 5.0
  3. PageSnap Pro - Full Page Screenshot No site access · 4 permissions 3 users ★ 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 FullSnap - Full Page Screen Capture access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 5 browser permissions.
What data does FullSnap - Full Page Screen Capture 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 FullSnap - Full Page Screen Capture asked for more permissions over time?
Its permissions changed once while we watched, on 2026-09-14.
Does FullSnap - Full Page Screen Capture 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-14.

Back to FullSnap - Full Page Screen Capture · Alternatives to FullSnap - Full Page Screen Capture

Where the data comes from: how the catalog is built