Is Stork Verify safe?

Clean risk

Stork Verify connects users to the Stork oracle network, transmitting account data and image-labeling answers to Stork's API servers.

When the popup opens, the extension authenticates with Stork's API using a JWT stored in chrome.storage.local and fetches the user's account stats and verification tasks. For each labeling task, a bounding-box image is retrieved and the user's answer coordinates are posted back to Stork's servers. OAuth tokens are stored unencrypted in local extension storage and refreshed automatically before each API call.

developersv1.2.0Chrome Web Store
0Risk

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.2.0. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.

  • Schedule its own background tasks

    alarms

  • Sign you in with your Google account

    identity

  • Store data in your browser

    storage

Where it sends data

Destinations our analysis observed Stork Verify 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.

  • app-api.jp.stork-oracle.network

    Stork Verify sends data to app-api.jp.stork-oracle.network. No other extension we have analysed sends data here.

  • app-auth.jp.stork-oracle.network

    Stork Verify sends data to app-auth.jp.stork-oracle.network. No other extension we have analysed sends data here.

Updated 30 September 2026knnliglhgkmlblppdejchidfihjnockl