What the extension sends: the actor identifiers of the cards on the apify.com page you are looking at (username/name slugs or actor ids), in batches of up to 40, to https://apifystats.com/api/ext/. That is the whole request. It carries no page content, no search query, no cookies from apify.com, no browsing history and no identifier for you.
What comes back: apifystats' public census data for those actors — the same numbers the actor's page on apifystats.com shows.
No account, no sign-in. The extension has no notion of who you are. The requests it makes carry no cookies (credentials: omit) and no token. The "Watch" and "Rivals" buttons are ordinary links to apifystats.com, tagged utm_source=extension so the site can count them; what happens there is the site's business, under its own privacy policy.
What is stored on your machine: your settings (overlay on/off, strip density, filter chips) in chrome.storage.local, and the current census day's card data in chrome.storage.session, which Chrome clears when the browser closes.
No analytics, no telemetry, no third parties. The extension contains no tracking code and never contacts any host other than apifystats.com.
Permissions, and why each one: - storage — settings and the per-session card cache. - host https://apifystats.com/* — the data API. - content scripts on apify.com and console.apify.com — to draw the strips. This is a content-script match, not a host permission: the extension cannot read apify.com from the background.
apifystats is independent and not affiliated with Apify. Questions: [email protected].