Privacy Policy
This policy describes what the FeedEcho hosted service at feedecho.net collects, stores, and does with your data. Last updated: September 23, 2026.
FeedEcho is operated by Jason Crabtree, Winchester, Virginia, United States. For privacy questions or data requests, email support@feedecho.net.
What we collect and why
| Data | Why we need it |
|---|---|
| Email address | Account identity, verification, password reset, and operational alerts about your feeds. |
| Password | Stored only as a salted scrypt hash. Never in plain text. |
| Feed URLs | The feeds you ask us to watch, and a cursor (last seen item) per feed so posts are not duplicated. |
| Feed content | Titles, authors, summaries, article bodies, and image references from recent items, stored so the built-in reader can display them. The newest 200 unstarred items per feed are kept (older ones are pruned automatically); items you star are kept until you unstar them, delete the feed, or delete your account. |
| Reader organization | Your folders, saved searches, and per-item read/starred state. |
| Destination credentials | Tokens, app passwords, webhook URLs, and SMTP credentials for the accounts you connect (Mastodon, Bluesky, micro.blog, Matrix, Discord, Telegram, email, webhooks). Required to post on your behalf; nothing else is done with them. They are encrypted at rest. |
| AI alt-text API key | Optional. If you enable AI-generated alt text, the API key for the OpenAI-compatible vision provider you choose. Stored encrypted at rest, used only to request alt text for images you attach to posts. |
| Echo configuration | Your templates, filters, and delivery settings. |
| Post history | Which feed items were delivered where, when, and with what outcome — needed for retries, duplicate prevention, and failure diagnosis. |
| Server logs | Request paths, client IP addresses, your account id when you are signed in, status codes, and timestamps — for debugging and abuse prevention. Paths only: query strings (which could contain tokens) are never logged. |
Legal basis for processing (GDPR)
If you are in the European Economic Area or the UK, we process your personal data on these bases:
- Performance of a contract (Art. 6(1)(b) GDPR): everything needed to provide the service you signed up for — your account, feeds, echoes, destination credentials, and post history.
- Legitimate interests (Art. 6(1)(f) GDPR): securing the service, preventing abuse, and debugging. Server logs fall under this; they are minimal and kept only briefly.
We do not rely on consent as a legal basis — we process on contract and legitimate interests as described above, and we do not sell personal data.
Your privacy rights
Depending on where you live, you have rights over your personal data, which we honour through the controls below:
- Access — your dashboard shows your feeds, echoes, and full delivery history.
- Export / portability — export your configuration from the dashboard at any time.
- Rectification — edit or reconnect your feeds, accounts, and echoes in the dashboard.
- Deletion — delete any feed, account, or echo, or delete your entire account from Settings (this removes all of your data, including post history).
- Restriction and objection — email support@feedecho.net and we will restrict or stop processing where the law requires.
- Complaint — if you are in the EEA/UK and are not satisfied, you have the right to lodge a complaint with your local data-protection supervisory authority.
California residents: you have the right to know what personal data we collect, to request its deletion, and to non-discrimination for exercising your rights. We do not sell personal data. Email support@feedecho.net to exercise these rights.
What we don't do
- We don't sell or rent your data, and there is no advertising. Data is disclosed only as described under "Who else sees data" below.
- Feed content is used only to run your echoes and power your reader — never for advertising, profiling, or training.
- No analytics, tracking scripts, or third-party browser requests run on these pages.
- No payment data: billing is handled by Stripe, which processes your card directly — card numbers never touch our servers.
Where your data lives
All account data is stored in a Postgres database on a server we operate in the United States, with encrypted off-site backups of that database that rotate out within about 8 weeks. Destination credentials are encrypted at rest. Traffic is HTTPS with HSTS. Sessions are signed, HttpOnly, SameSite cookies; logging out or resetting your password invalidates existing sessions immediately. Every feed, account, setting, and history row is scoped to your account at the query level.
International transfer: if you use the service from the EEA or the UK, your personal data is transferred to and stored in the United States, where the server and the operator are located. You sign up directly with a US provider, so that transfer is necessary to perform the contract you requested (Art. 49(1)(b) GDPR); by signing up you acknowledge it.
Breach notification: if we learn that your personal data has been compromised, we will notify affected users and, where required, the relevant authorities.
Who else sees data
- Your connected platforms (Mastodon, Bluesky, micro.blog, your Matrix homeserver, Discord, Telegram, your email provider) receive exactly the posts you configure — nothing else.
- Our fetch relay (first-party). Some sites block server-side feed readers with a 403 or 429 response. When that happens, FeedEcho retries the fetch through our own relay service, hosted on Cloudflare Workers. The feed or image URL is passed to the relay exactly as you entered it — including any private token in its query string — and the relay fetches the site and returns the response. The relay logs and caches nothing, and no account credentials or post content go through it. (A self-hosted install only uses this if its operator configures a relay.)
- Email delivery for verification, password-reset, and operational mail goes through Mailgun, our transactional email provider; it processes the message (and your address as recipient) to deliver it.
- Payment processing is handled by Stripe, which processes your card directly for subscriptions and refunds.
- AI alt-text provider (optional): if you enable AI-generated alt text, images you attach to posts are sent to the OpenAI-compatible vision provider you configure, using your own API key. If you never configure one, no images leave the service for this purpose.
- FeedBooster (optional): if you enable Boost on an account or echo, the public URL of each published post is sent to the FeedBooster service — also operated by us, on the same infrastructure — which re-shares it on the fediverse. Only posts you explicitly mark for boosting, and only their already-public URLs.
- Uptime monitoring periodically requests the public health endpoint from outside the server; it does not involve your account data.
- Nothing else, unless required by law.
How long we keep things
- Account and configuration data: while your account exists.
- Reader items: the newest 200 unstarred items per feed; starred items until you unstar them, delete the feed, or delete your account. Deleting a feed removes its stored items and its URL immediately.
- Post history and delivery outcomes: retained with the feed/echo records they belong to, so your posting record and retry state survive — deleting a feed or echo keeps its delivery history. Full account deletion (below) removes everything.
- Verification and password-reset tokens: single-use, expire in 24 hours, stored only as hashes.
- Server logs: rotated automatically and kept briefly.
- Encrypted backups: deleted data (including after full account deletion) may persist in encrypted off-site backups until those backups rotate out, within about 8 weeks.
Your controls
- Delete individual feeds, connected accounts, or echoes from the dashboard at any time.
- Revoke any destination token at its source platform (Mastodon, Bluesky, micro.blog, Matrix, Discord, or Telegram settings) — we stop being able to post immediately. Webhook URLs can be rotated at the receiving service; disconnecting the account in FeedEcho stops all use either way.
- Export your data: the dashboard shows your feeds, echoes, and full delivery history.
- Delete your account entirely from Settings (password-confirmed) — this removes your account and all of its data, including post history. Encrypted backups may retain deleted data until they rotate out, within about 8 weeks.
Contact
Privacy questions or data requests: email support@feedecho.net.