The freeRSS Directory
Categories New listings Info
Signed in asFor Publishers
Directory/Privacy Policy

RSS Directory — Privacy Policy

Last updated: 2026-11-07 · Effective: 2026-11-06


The short version

  • Visitors have no account. We set no cookies for them and run no advertising, no analytics and no tracking, so there is nothing to consent to and no cookie banner. Your browser keeps a few settings (such as the reader you chose) on your device only.
  • In the EU and the UK, and wherever we can't tell your country, feed pages don't load YouTube, X and similar embeds until you allow each service. You can withdraw that at any time (below).
  • Publishers have an account. We store their email address and nickname in the EU. We use the address to run the account and to tell you about your listings and important changes; news only if you opt in.
  • Listings can name the people behind a feed. If that's you, you can ask us to remove it.
  • We never sell your data.

The full detail is below.


1. Who we are (controller)

The controller responsible for your personal data is:

Tim Jansen
c/o Autorenglück #56265
Albert-Einstein-Straße 47
02977 Hoyerswerda
Germany
Email:

The RSS Directory is provided at rssdirectory.org, including the publisher console at rssdirectory.org/publishers. It is made by the makers of Downread, a free feed reader, and has the same operator.

2. What this policy covers

This policy explains what personal data the RSS Directory processes, why, on what legal basis, how long we keep it, where it is stored, and your rights. It covers the directory's pages, the feed pages, the publisher console and the emails we send publishers.

Parts of the directory are delivered by Downread's servers : the search, the feed pages (the listing and its latest posts) and the reports. The controller is the same. What happens there is described in this policy as far as it concerns the directory.

3. Visiting the directory (no account)

Visitors have no account, and we keep nothing about them on our servers under their name. To show the pages, your browser sends ordinary requests:

RequestGoes toData
the pages, scripts and fontsrssdirectory.org (Cloudflare)IP address, browser/user agent, the requested address
your country (used as described in §4)rssdirectory.org (Cloudflare)IP address; we receive only the country
search and its suggestionsDownread's serversIP address, user agent, what you type
a feed page: the listing and its latest postsDownread's servers and their content delivery network: the EU servers if you're in the EU or the UK, or if we can't tell your country, the US servers otherwiseIP address, user agent, the feed shown
images and embeds in posts, if the feed page shows full poststhe publishers' own servers, and services such as YouTube (§5)IP address, user agent
"Follow" in a reader you choosethat reader, only when you clickwhatever that reader collects

We use this data only to deliver the pages and to keep the service secure (legitimate interests, Art. 6(1)(f) GDPR). We don't build profiles of visitors. Our servers log requests briefly for security and abuse prevention (§13).

Reports. If you report a listing, a feed page or a post, we receive the reported item, the reason, the details you write, the optional email address you give (required if you tell us a listing is yours or ask us to remove it), and your IP address, which is stored with the report. While the report form is open, Cloudflare Turnstile checks that you're not a bot. Reports are handled with Downread's report system, on its EU servers for visitors in the EU or the UK. Legal basis: our legal obligations to handle reports of illegal content (Art. 6(1)(c), DSA Art. 16) and our legitimate interest in keeping the directory free of abuse (Art. 6(1)(f)). How long we keep them: see §14.

4. Cookies & local storage — and why there's no banner

  • Visitors: no cookies. Your browser's local storage keeps, on your device only:

    • the country we looked up (geo), so we ask only once;
    • the services whose embeds you allowed (embedConsent, §5);
    • the reader you chose to remember in the Follow menu (followReader, followCustomReader).

    Your browser's session storage keeps your recent searches and the feeds you looked at (keys starting with yf-). They are used to show them again quickly, and are deleted after 30 minutes or when you close the tab.

  • Publishers: one cookie. In the publisher console we set a single first-party cookie (authToken) whose only purpose is to keep you signed in. Local storage keeps your account's sign-in state (yf-publisher-auth: account id, status and email address); session storage keeps the email address during a one-time-password sign-in and an edit link you opened, until you close the tab.

  • Strictly necessary, no trackers. All of this is strictly necessary for what you asked for, so under the ePrivacy Directive / § 25 TDDDG it requires no consent (we still tell you about it here). We set no advertising, analytics or third-party tracking cookies, so we don't show a cookie banner. Our fonts and scripts are served from our own domain.

The exceptions are embeds, Turnstile and Google sign-in, which only ever load on your action (§3, §5, §8).

5. Third-party content on feed pages

A feed page shows a listing and, depending on the publisher's choice, short excerpts of the feed's latest posts (text only), its full latest posts, or no posts. Feeds and posts are third-party content.

If a feed page shows full posts, their images load directly from the publisher's servers, which then see your IP address. Embeds (YouTube, Vimeo, JW Player, Simplecast, Captivate, X/Twitter, Instagram, TikTok, Threads, Reddit, Bluesky) connect your browser to that service, which learns your IP address and can set its own cookies. If you're in the EU or the UK, or we can't tell your country, we don't load any embed until you allow its service: until then you see a placeholder with an "allow" button. Your choice is stored in your browser only (§4). Elsewhere, embeds load by default. The legal basis for loading embeds in the EU and the UK is your consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG).

Follow opens the feed in the reader you pick. Nothing is sent to any reader before you click, and that reader's own privacy policy applies.

We are not responsible for the content of third-party feeds or for the data third parties collect when their content is shown at your request.

External content

Showing content from other services connects your browser to that service, which then learns your IP address. You can withdraw the permissions you gave at any time. In the EU and the UK, content from those services is then hidden again until you allow it.

6. Publisher accounts: what we collect, and why

DataWhy we process itLegal basis (GDPR)
Email address, stored in plaintext (§7)sign-in, account emails, contacting you about your account and listingsContract (Art. 6(1)(b)); for statements of reasons and notice of changes also legal obligation (Art. 6(1)(c))
Nicknameto address you in emails and in the console; never shown in listingsContract (Art. 6(1)(b))
Password (stored hashed), or your Google account identifier (§8)authenticate youContract (Art. 6(1)(b))
When you signed up, last signed in and last used the console; when you accepted the Terms; account statusrun the account, prove that you accepted the Terms, delete inactive accounts (§13)Contract (Art. 6(1)(b)); legitimate interests (Art. 6(1)(f))
Claims, listings and change requests : the feed, how you verified it (with the results of our automatic checks: when, whether the token was found, the HTTP status), the listing texts, your comments to us, our decisions and their reasonsrun the directory and review listingsContract (Art. 6(1)(b))
Uploaded icons (public files)show your listingContract (Art. 6(1)(b))
Your consent to news emails (when, which wording, how, when confirmed)prove the consent (§7)Legal obligation (Art. 6(1)(c), Art. 7(1))
IP address, user agent, request logs; a Turnstile check at sign-updeliver the service, keep it secure, prevent abuseLegitimate interests (Art. 6(1)(f))

Approved listings are published in the directory and in Downread's catalog (see the Terms of Use , "Listings"). We do not process your data for advertising or profiling, and we do not sell it.

7. How we use your email address

Unlike Downread, which keeps only a hash of its users' addresses, the RSS Directory stores your email address, because it has to be able to write to you. We use it for:

EmailsExamplesLegal basis
Account emailsconfirming your address, password reset, one-time passwordsContract (Art. 6(1)(b))
Notes on your listingsyour claim or change was approved or declined, your listing was changed or removed after a report, the statement of reasons of a decisionContract (Art. 6(1)(b)); for statements of reasons also legal obligation (Art. 6(1)(c), DSA Art. 17)
Service announcementschanges to the Terms of Use or this policy, the end of the directory, security notices, the warning before an inactive account is deletedContract and legal obligation (Art. 6(1)(b), (c)); legitimate interests (Art. 6(1)(f))
Newsnews and new features of the RSS Directoryonly with your consent (Art. 6(1)(a))

The first three kinds contain no advertising. News emails are sent only if you tick the optional box at sign-up or subscribe on your account page, and confirm it with the link we email you. You can withdraw your consent at any time on your account page; the consent record is then deleted. You can also object to the use of your address for direct marketing at any time (Art. 21(2) GDPR).

We don't show your email address to other users or the public, and we don't share it with anyone except our email provider (§11) and where the law requires it (§14).

8. Sign in with Google (optional)

You can sign in to the publisher console with your Google account instead of a password. Nothing from Google loads until you choose it. Your sign-in request then goes to Google under Google's privacy policy, and we receive a Google account identifier and your email address to create or authenticate your account. We load no Google analytics or tracking.

9. People named in the directory

Listings describe feeds, and the listing of a personal blog or podcast often contains the name of its author, sometimes a photo as the icon. That is personal data of people who may not use the directory at all.

  • Source: the feed itself (its title and description, as published for syndication), or the publisher who wrote the listing.
  • Purpose and legal basis: helping people find feeds that their authors published to be found and followed (legitimate interests, Art. 6(1)(f)).
  • Recipients: the public; listings are also shown in Downread. We don't publish the catalog as open data yet; before we do, we will update this policy.
  • Your choice: if a listing names you and you don't want that, use Report → "remove my listing" on the listing, or write to . We remove a photo used as an icon on request. You don't need a publisher account for this.

We don't inform each person named in a listing individually, because that would take a disproportionate effort for thousands of listings (Art. 14(5)(b)); this section is the information instead.

10. Where your data is stored

  • Publisher data (accounts, claims, listings, uploads' records) is stored in the EU, on our servers in Strasbourg, France, for all publishers wherever they are. The publisher console talks only to our EU servers. Uploaded icons are public files on Cloudflare's network.
  • Visitors' requests to Downread's servers go to its EU servers if you're in the EU or the UK, or if we can't tell your country, and to its US servers otherwise. Reports are stored on the same servers.
  • Backups of publisher data are encrypted and kept in the EU.

11. Who processes data for us (sub-processors)

We use a small number of providers who process data on our behalf under data-processing agreements:

  • Server4You GmbH (Germany) — server hosting in its EU datacenter (Strasbourg: publisher data, and Downread's EU servers) and its US datacenter (Downread's US servers, which serve visitors outside the EU and the UK).
  • Cloudflare, Inc. (USA) — hosting of the directory's pages, content delivery, proxying, the country lookup, object storage (R2: uploaded icons and encrypted backups), email delivery and the @rssdirectory.org mailboxes, and Turnstile bot protection at sign-up and in the report form. Cloudflare is certified under the EU–US Data Privacy Framework and offers EU data-processing terms; Turnstile is privacy-preserving (no advertising cookies, no cross-site tracking).

Google processes the sign-in with Google (§8) as an independent controller, only when you choose it. We use no advertising networks and no analytics providers, and we do not sell your data. We keep this list current and add any new provider before it starts processing your data.

12. International transfers

Publisher data stays in the EU, so no international transfer of it takes place for normal use. Visitors outside the EU and the UK are served by Downread's US servers. Where a provider (e.g. Cloudflare) may process limited data outside the EU, that transfer is covered by the EU–US Data Privacy Framework and/or EU Standard Contractual Clauses. Separately, where we are legally required to report child sexual abuse material, we may transmit the relevant data to the US-based NCMEC and to competent authorities (see §14) — this is a legal obligation, not a commercial transfer.

13. How long we keep your data (retention)

  • Publisher accounts: we keep your account data, claims, listings, change requests and uploads for as long as your account exists, and delete them when you delete your account.
  • Inactive accounts: if nobody signs in to an account or uses the console with it for 2 years, we delete it and its data. We email you a warning 30 days before; signing in keeps the account.
  • Your listings stay in the directory and in Downread after you delete your account (including the icon, which Downread keeps with the feed), without any link to you (see the Terms of Use, "Listings"). If a listing contains a photo of you, we remove it on request (§9).
  • News consent: while it is in effect; deleted when you withdraw it.
  • Server/security logs: kept only for a short period for security and abuse prevention.
  • Backups: deleted data disappears from our backups after at most 4 weeks.
  • Data on your device (§4) stays until you clear it; session storage is cleared when you close the tab.
  • Exceptions: the limited records we are legally required to keep (§14).

14. Legal retention, reports and law enforcement

Running a directory with listings written by publishers carries legal duties. To meet them we may retain, beyond an ordinary deletion, the minimum data needed for these specific purposes:

  • Evidence when we act on content: when we take down an icon, decide against a publisher for illegal content or for infringing the rights of others, or a publisher deletes data about a feed that has an open report, we keep a frozen copy of the publisher's data about it (claims, listings, change requests and uploads) for 3 years, identified only by the account's id.
  • Abuse & repeat-infringer prevention (DSA / DMCA): strikes are counted for 2 years. If an account is banned, its email address can't be used to sign up again; we keep it only as a peppered hash (a pseudonymised form) with the ban status, until the ban is lifted.
  • Child sexual abuse material (CSAM): if we obtain knowledge of apparent CSAM, we are legally required to preserve the relevant material and data, including the publisher's identity, for at least 90 days (longer if the authorities ask), and report it to the competent authorities — in Germany the police or the Bundeskriminalamt (BKA) and, where applicable, the US NCMEC — and we may not notify the person concerned. We do not otherwise search your content.
  • Reports and what we did about them are kept as evidence that we acted, for a limited period.
  • Legal claims: data relevant to an actual or reasonably anticipated legal dispute, until it is resolved.

The legal bases are legal obligation (Art. 6(1)(c)) and legitimate interests / legal claims (Art. 6(1)(f), Art. 17(3)(e)). These records survive the deletion of the account. We disclose data to law enforcement or authorities only where legally required or permitted.

15. Your rights

Under the GDPR (and UK GDPR) you have the right to: access your data; rectify inaccurate data; erase your data; restrict or object to processing (including, at any time, to direct marketing); data portability; and, where processing relies on consent, to withdraw it at any time without affecting prior processing — for news emails on your account page, for embeds above.

In the publisher console you can edit your account, download your data (account page, "Download my data"), and delete your account. For anything else, contact . Where we are legally required to retain certain records (§14), we may not be able to erase those.

You also have the right to lodge a complaint with a data-protection supervisory authority — in Germany, the authority of your federal state (or ours), or the authority in your country of residence.

16. Security

Everything is transferred over HTTPS. In the publisher console we keep your session token in an HttpOnly cookie (inaccessible to page scripts) and your login token only in memory, and we store passwords hashed with salt. Your email address is stored in plaintext , because we need it to contact you (§7). It is kept only on our EU servers, access to them is limited, and our backups are encrypted. We sanitise third-party feed content before displaying it. On sign-up and in the report form we use Cloudflare Turnstile, a privacy-preserving bot-protection check that sets no advertising cookies and does not track you across sites. No system is perfectly secure, but we take appropriate technical and organisational measures (GDPR Art. 32), and we will tell you if a breach puts your data at high risk (Art. 34).

17. Age

Publisher accounts are for people aged 18 or older. The directory is not directed at children, and we do not knowingly collect data from children. If you believe a child has provided us data, contact us and we will delete it.

18. Changes to this policy

We may update this policy. We tell publishers by email before material changes take effect. The "Last updated" date at the top shows the current version.

19. Contact

Questions or requests about your data:
Abuse / illegal-content reports: Report in the "⋯" menu, or . See also our Terms of Use and Legal Notice.

Website owners: how we check that a feed belongs to the publisher who claims it, and what our verifier requests from your site, is explained on the Verifier page.

RSS Directory

A free and open directory of RSS feeds. Made by the makers of Downread.

rssdirectory.org
Directory
Categories A–ZNew listingsSuggest a feed
Publishers
Add a feedManage my feedsClaim a listingListing guidelines
About
How RSS worksRSS newsTerms of UsePrivacyLegal Notice (Impressum)