About FeedEcho
FeedEcho is a small, paid hosting service for FeedEcho, an open-source tool that watches RSS feeds and posts new items to your Mastodon, Bluesky, micro.blog, Matrix, Discord, Telegram, email, or webhook destinations. It is operated by Jason Crabtree, Winchester, Virginia, United States. This page describes how the hosted service at feedecho.net handles your data. See also the Terms of Service, the Privacy Policy, and the Pricing page.
What we store
- Your account: email address and a salted scrypt hash of your password. Passwords are never stored in plain text.
- Feeds: the feed URLs you add and the last item each feed was checked against. Recent feed content — titles, authors, summaries, article bodies, and image references — is stored so the built-in reader can display it: the newest 200 unstarred items per feed (older ones are pruned automatically), and starred items until you unstar them, delete the feed, or delete your account. Your folders, saved searches, and read/starred marks are stored as well.
- Destinations: credentials for the accounts you connect — Mastodon access tokens, Bluesky app passwords, micro.blog tokens, Matrix access tokens, Discord webhook URLs, Telegram bot tokens, generic webhook URLs and headers, and email SMTP credentials. These are required to post on your behalf, and they are encrypted at rest. If you enable AI-generated alt text, the API key for the vision provider you choose is stored the same way.
- Post history: which items were posted where, and any delivery errors, so failures can be retried and diagnosed.
Everything lives in a Postgres database on a single VPS we operate. Data is not sold or rented; it is disclosed only as described under Third parties below.
What we don't do
- Feed content is used only to run your echoes and power your reader — never for advertising, profiling, or training.
- No tracking, analytics, or advertising networks run on this service.
- No payment data is stored. Billing is handled by Stripe, which processes cards directly — card numbers never touch our servers.
Security practices
- TLS everywhere: all traffic is HTTPS with HSTS.
- Encryption at rest: destination credentials are encrypted with Fernet before they are stored.
- Sessions: signed, HttpOnly, SameSite cookies; logging out or changing your password invalidates existing sessions immediately.
- Email links: verification and password-reset tokens are single-use, expire in 24 hours, and are stored only as hashes.
- Tenant isolation: every feed, account, setting, and history row is scoped to its user at the query level.
- Post templates run in a sandboxed template engine with no filesystem or network access.
- Outbound requests (feed fetches, image downloads) are validated against SSRF patterns, including private-network ranges.
- Login protection: failed-login and signup rate limits per address; account suspension available to administrators.
- Operational logging: server access logs record request paths (never query strings), client IP addresses, account ids for signed-in requests, status codes, and timestamps for operational debugging, retained briefly.
Third parties
- Your connected platforms (Mastodon, Bluesky, micro.blog, Matrix, Discord, Telegram, your email provider) receive exactly the posts you configure. Nothing else.
- Some sites block server-side readers with a 403 or 429. When that happens, the feed or image URL is retried through our own first-party fetch relay on Cloudflare Workers, which fetches the site and returns the response, logging and caching nothing. The URL is passed exactly as configured — including any token in it. No account credentials or post content go through it. (A self-hosted install only uses this if its operator configures a relay.)
- Billing goes through Stripe, which processes your payment card directly.
- Transactional email (verification, password reset, operational alerts) is delivered by Mailgun, which processes the message and your recipient address.
- 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 enable Boost on an account or echo, the public URL of each published post goes to FeedBooster — a companion service run by the same operator on the same infrastructure — which re-shares it on the fediverse.
- Pages use the self-hosted Inter font family. No third-party assets or requests are made from your browser.
Account deletion
Deleting a feed stops it from posting, removes its stored reader items, and blanks its URL; its delivery history is kept, so your posting record stays intact. Deleting a connected account or an echo likewise keeps its history. To remove everything, delete your account from Settings (password-confirmed) — that 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.
Questions or problems: email support@feedecho.net — it reaches the operator directly.