Is Circle reader safe?
Circle reader sends account tokens and synced reading data to circlereader.com over cleartext HTTP.
When a user logs in or uses Data Sync, Circle reader requests Circle Reader account and sync APIs over HTTP instead of HTTPS. Those requests can include session or CSRF tokens, a user ID, and synced reading data such as URLs, page titles, rules, lists, and settings.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
Who publishes it染河 - no other listings under this identity, 1 shared hostname
染河 - no other listings under this identity, 1 shared hostname
What this publisher told the store about itself, and the other listings that told it the same thing.
Shared hosts - 1 hostname
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.
What it can do
Permissions this extension asks for, as declared in version 2.7.0. 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>
Add items to the right-click menu
contextMenus
Where it sends data
Destinations our analysis observed Circle reader 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.
- circlereader.com
Circle reader sends data to circlereader.com. No other extension we have analysed sends data here.