Is Full Page Screenshot safe?

Clean risk

Full Page Screenshot accepts auth-sync messages from any visited site and stores supplied login tokens.

Its all-pages content script accepts AUTH_SYNC postMessage events from the current page and saves the supplied access token, refresh token, expiry, and user object in chrome.storage.local. Any HTTP or HTTPS page can also ask the fallback detector for the extension ID and version because the same script is injected broadly. The confirmed behavior writes page-supplied auth state locally; no specific remote data recipient is identified.

Horacev1.20.1Chrome Web Store
2Risk
Who publishes it

Horace - no other listings under this identity

What this publisher told the store about itself, and the other listings that told it the same thing.

AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.

Publishers can request a review.

What it can do

Permissions this extension asks for, as declared in version 1.20.1. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.

  • Read and change your data on every secure site you visit

    https://*/*

  • Read and change your data on every site you visit

    http://*/*

  • Store data in your browser

    storage

  • See the address and title of every tab you have open

    tabs

  • Act on the current tab, but only after you click the extension

    activeTab

  • Run its own code inside the pages you visit

    scripting

  • Schedule its own background tasks

    alarms

Updated 30 September 2026llagkaomccnfgbalehoaojiiplacggcd