Is Scrive Go safe?
Scrive Go sends the active page snapshot or selected PDF to Scrive's printer API when you start signing.
When you use Scrive Go to start signing, it captures the active page as MHTML or fetches the selected PDF and uploads it as a file. The upload goes to Scrive's printer API with session and extension metadata so Scrive can open the signing flow.
Who publishes itScrive - no other listings under this identity
Scrive - 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.1.22. 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 site you visit
<all_urls>
Watch every request your browser makes
webRequest
Act on the current tab, but only after you click the extension
activeTab
Run its own code inside the pages you visit
scripting
Store data in your browser
storage
Store an unlimited amount of data in your browser
unlimitedStorage
Sign you in with your Google account
identity
Save the full contents of any page you visit
pageCapture
Where it sends data
Destinations our analysis observed Scrive Go contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- go-auth-proxy.scrive.com
Scrive Go sends data to go-auth-proxy.scrive.com. No other extension we have analysed sends data here.