Data Sourcing & Privacy Statement
Last updated: August 2026
This page explains where the podcast data on allfeeds.ai comes from, the legal basis for processing it, and how podcast owners can correct or remove their information. It's intended to answer the questions we most often receive from customers as part of their own supplier due diligence and compliance review process (including UK/EU GDPR and PECR), so you're welcome to share this link with your compliance or legal team rather than requesting a bespoke reply.
1. Where does this data come from?
We operate our own proprietary indexing system that continuously discovers and crawls publicly published podcast RSS feeds — the same feeds every podcaster submits to Apple Podcasts, Spotify, and other directories specifically so their show can be found and distributed. RSS is a syndication format by design: publishing a feed is a public act intended for redistribution.
From each feed we extract only the metadata the podcaster has already chosen to publish there: show title, description, category, language, episode information, and — only when the podcaster has chosen to include it in their feed's optional owner/contact tags — a contact name and email address. We do not scrape private or login-gated sources, purchase consumer data broker profiles, or infer contact details from anywhere other than the podcast's own public feed.
2. What is the lawful basis for processing this data?
We rely on legitimate interests (Article 6(1)(f) UK/EU GDPR) to process the professional contact details that podcast operators have published in connection with their show. In reaching that position we've weighed:
- The data is already public, and was published by the podcaster specifically for wide syndication;
- It is limited to professional/business contact details tied to operating a podcast — not private or special-category information;
- Processing is proportionate to the purpose podcasters generally publish this contact information for in the first place: enabling legitimate business contact such as advertising inquiries, guest bookings, and partnership outreach; and
- Any podcast owner can object or request removal at any time, at no cost (see Section 4).
This database is offered for legitimate business-to-business purposes — market research, advertising and sponsorship outreach, partnership or guest-booking inquiries, journalism, and similar professional use connected to the podcast itself. It is not intended, and must not be used, to build consumer profiles or for any purpose unrelated to engaging with the podcast in its professional capacity.
3. Were podcasters given a privacy notice at collection?
Because our data is aggregated from many thousands of independently operated public feeds across the internet, rather than collected directly from individuals through any form or account we control, we are not in a position to have delivered a bespoke privacy notice at the moment each podcaster first published their feed.
This page is how we provide that transparency after the fact: it is publicly linked so that podcasters, customers, and regulators alike can see exactly what we do and why. Any podcaster who was unaware their public feed had been indexed can request correction or removal at any time (Section 4), and we act on those requests promptly.
4. How current is the data, and is it checked against suppression lists?
Our indexing system re-checks known podcasts continuously, at least as often as every 5 days on average and typically much more frequently, and our live database is updated throughout the day — we do not sell static or stale snapshots.
We do not currently cross-reference third-party "Do Not Email" or corporate suppression registries before delivering data. Maintaining and honoring suppression and opt-out lists for your own outbound communications is your responsibility as the sender under PECR and equivalent direct marketing regulations — allfeeds.ai compiles podcast metadata, we do not send marketing communications on behalf of our customers. We do, however, permanently remove any individual from our database, our API, and all future exports upon a verified removal request, as described below.
5. Corrections, removal requests, and privacy questions
If you are a podcast owner and would like your contact information corrected or removed, or if you have any question about how we source or process this data, contact us at help@allfeeds.ai.
- You must provide the allfeeds_id of the podcast feed. (Search for it, and provide the 10-character code at the end of the URL.)
- You must contact us using the email address associated with that podcast feed.
We will act on verified removal requests promptly, and a removed listing is excluded from our public site, our API, and every data export going forward.
We do not have a formal Data Protection Officer under Article 37 GDPR, as our processing does not meet the criteria requiring one. For all data protection inquiries, correction requests, or compliance documentation requests, help@allfeeds.ai is our designated contact.