Feed-elity

Privacy Policy

Last updated 2026-08-18

Feed-elity itself makes no network requests, sends nothing to its developer or to any third party, and contacts no server. Everything it stores stays in your own browser's storage. Some of it is synced between your own signed-in Chrome profiles by Google; none of it is sent anywhere else. That is not a summary of a longer policy. It is the whole policy. What follows is the detail that makes it checkable.

What the extension does

Feed-elity runs on https://www.strava.com/dashboard. It reads the activity cards already rendered on that page, decides which ones you probably do not want to scroll past, and folds those into a one-line summary you can click open again. Nothing is removed from the page and nothing is altered on Strava's servers.

What it stores, and where

Data	Where it lives	Why
Your filter settings: thresholds, keywords, per-athlete show/hide rules together with that athlete's display name, units, theme, filter order	`chrome.storage.sync`	So your settings survive a browser restart, and follow you to other Chrome profiles you are signed into. Because a per-athlete rule is stored with that athlete's display name, that name travels through Chrome Sync along with the rest of your settings, the same as any other synced setting (see below)
Display names and Strava numeric ids of athletes seen in your feed, plus the sports and unit (km/mi) your feed renders in	`chrome.storage.local`	So the settings panel can show a name next to a rule instead of a bare id, and offer the sports you actually see in the units Strava is already using. Never leaves your browser
Up to 40 recent activities per athlete: activity id, date, sport, distance, moving time, elevation gain, an approximate region name, comment count, and photo count	`chrome.storage.local`	So the extension can judge whether an activity is unusually big for that athlete, away from their usual places, or has gained comments or photos since you last saw it. Never leaves your browser
Diagnostics, only while you tick “Record diagnostics” (off by default): up to 200 entries	`chrome.storage.local`	For you to copy and paste when reporting a bug. A filtered-activity entry carries that athlete's display name with the activity's title, sport, distance, moving time and elevation, together with the filtering decision the extension reached, the rule that produced it and the flags that fed that decision; a failure entry carries an error message, and the athlete's numeric id where the extension knows it. Clearable from the options page, and never leaves your browser

chrome.storage.sync is Chrome's own sync, between your own signed-in Chrome profiles. It does not pass through any server operated by this extension's author, because there is no such server. It does mean a per-athlete rule's stored display name is visible to Google's sync infrastructure the same way every other synced setting is, and reaches every Chrome profile where you have this extension installed and Chrome's extension sync turned on.

Exporting and importing settings

The options page's “Export settings” button downloads everything in the table above from chrome.storage.sync as a JSON file named feed-elity-settings.json, including each per-athlete rule and that athlete's display name. Once downloaded, the file is yours: the extension takes no further part in it, and has no way to know where it goes next. If you plan to hand it to someone else, for example attaching it to a bug report, look at what is in it first. It can name people other than you.

“Import settings” reads a file in the same shape back into your settings on whatever machine you run the import on.

Support and feedback links

The popup and the options page each offer a link to Buy Me a Coffee. The settings panel's drawer offers a link to a Google Form for feedback. The extension itself sends nothing to any of them. They are ordinary links, the same as any link on any page.

Following one is an ordinary page visit. Buy Me a Coffee or Google sees your IP address the way any site does when you visit it, and that visit is between you and them, not something Feed-elity relays. The feedback form asks for an email address, but only as an optional field: leave it blank and nothing about who you are goes with your answer.

What it does not do

No network requests. The extension never calls fetch, XMLHttpRequest, or navigator.sendBeacon. There is no endpoint to send data to. In the source, this returns nothing:
```
grep -rE 'fetch\(|XMLHttpRequest|sendBeacon' extension/
```
No analytics, telemetry, or crash reporting. None, of any kind.
No advertising, and no data sold or shared. There is nobody to share it with.
No account, no login, no identifier. The extension never learns who you are beyond what is already on the page in front of you.
No remote code. Everything it runs is in the package you installed. It loads no scripts from anywhere.

Permissions, and why each exists

storage: to save your settings, the observed athlete and sport names, the per-athlete activity log, and the optional diagnostics log described above. Nothing else uses it.
Host access to https://www.strava.com/dashboard*: the content script is declared for that URL only. It cannot run on any other site, including the rest of strava.com. There is no <all_urls> and no activeTab.

Deleting your data

Removing the extension from chrome://extensions deletes everything it stored. You can also clear recorded diagnostics at any time from the extension's options page.

Relationship to Strava

An independent project. Not affiliated with, endorsed by, or sponsored by Strava. “Strava” is referenced only to describe the site this extension works with.

Contact

Questions or a problem: email angry.bee.software@gmail.com.