Is Impact Factor Finder safe?
Impact Factor Finder sends Google Scholar profile details and paper metadata to two Supabase backends.
When the Ask IFF panel opens on Google Scholar, the extension sends a persistent client quota ID, Scholar profile identity, profile name, subscription status, and verified email domain to its AI summary backend. When a user runs the Open Access scan, it sends paper titles, years, citation counts, result/full-text/PDF URLs, DOIs, Scholar profile and page identifiers, version, and an install ID to its Open Access backend.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
Who publishes itAhmad Arsalan - no other listings under this identity, 2 shared hostnames
Ahmad Arsalan - no other listings under this identity, 2 shared hostnames
What this publisher told the store about itself, and the other listings that told it the same thing.
Shared hosts - 2 hostnames
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
Where it sends data
Destinations our analysis observed Impact Factor Finder 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.
- byjvopbhqybxcyfecxth.supabase.co
Impact Factor Finder sends data to byjvopbhqybxcyfecxth.supabase.co. No other extension we have analysed sends data here.
- osrqogdvurbqfwttfyqk.supabase.co
Impact Factor Finder sends data to osrqogdvurbqfwttfyqk.supabase.co. No other extension we have analysed sends data here.