Is Feedly Notifier safe?
Feedly Notifier sends an embedded Feedly OAuth client secret to Feedly during sign-in and token refresh.
When you sign in to Feedly, the extension exchanges the authorization code by posting its bundled client ID and client secret to Feedly's token endpoint. It sends the same embedded client secret again when refreshing access with the stored refresh token.
Who publishes itOleg Shevchenko - no other listings under this identity, 2 shared hostnames
Oleg Shevchenko - 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.
What it can do
Permissions this extension asks for, as declared in version 2.29.1. 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 feedly.com
*://*.feedly.com/
Store data in your browser
storage
See the address and title of every tab you have open
tabs
Show you desktop notifications
notifications
Watch every request your browser makes
webRequest
Where it sends data
Destinations our analysis observed Feedly Notifier 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.
- cloud.feedly.com
Feedly Notifier sends data to cloud.feedly.com. No other extension we have analysed sends data here.