A(z) Add to Feedly Plus adatvédelmi irányelvei
Add to Feedly Plus szerző: quasiyoke
A(z) Add to Feedly Plus adatvédelmi irányelvei
This Privacy Policy describes how the Add to Feedly Plus browser extension (“the Extension”) handles your information. We are committed to your privacy and operate with a fundamental principle: we do not collect, store, or transmit your personal data.
1. Data Collection: We Collect Nothing.
The Extension is designed with a privacy-first approach. It functions entirely on your local machine (your browser).
- We do not collect any personal information. This includes, but is not limited to, your name, email address, IP address, browsing history, or any other identifying data.
- We do not have a server. There is no central server to which any data is sent or stored.
- The Extension does not use analytics or tracking. We do not use any tools to track your usage of the extension.
2. How the Extension Works
The sole purpose of the Extension is to simplify the process of discovering and subscribing to RSS and Atom feeds using Feedly. Here is what it does:
- Local Page Analysis: When you activate the Extension on a webpage, it analyzes the HTML code of that specific page locally within your browser.
- Finds feed Links: It scans the page's code to identify any existing links to RSS or Atom feeds.
- Interacts with Feedly: If you choose to subscribe to a found feed, the Extension will open a new tab to feedly.com. This interaction is solely between your browser and the Feedly service. This Extension and its creator are not associated with or endorsed by Feedly.
3. Data Sharing: We Share Nothing.
We do not sell, rent, trade, or otherwise transfer any information to third parties because we have no information to transfer.
Your interaction with the Feedly service (feedly.com) is governed by Feedly's own Privacy Policy. We encourage you to review their policy to understand how they handle your data when you use their service.
4. Permissions Explanation
The extension requires certain browser permissions to function. Here is why each permission is needed:
storage
: the Extension caches the list of feeds received from the page to avoid restarting the DOM selector each time this list is needed. The Extension's background script should be ready to run as a service worker (this is particularly relevant for Chrome). To prevent the cache from being cleared when the service worker enters an idle state, we don't store the cache in global variables but usestorage.session
.host
permission (all URLs): in order to find links to RSS and Atom feeds in the page head, the extension needs access to the source code of the pages. All it does with it is execute a DOM selector by link tags.