What we collect, and what we refuse to.
PodAttr measures whether podcast ads work. It does that with the minimum data the job requires, and it is designed so that we never hold a profile of any listener. This policy is written to be read, not skimmed past.
Who this covers
Three groups touch PodAttr: podcasters (our customers), listeners (whose downloads pass through our prefix), and sponsor-site visitors (whose page visits fire our pixel). Listeners and visitors never have an account or a relationship with us — which is exactly why the sections about them matter most.
Listeners and sponsor-site visitors
When a podcast app downloads an episode through our prefix, or a browser loads a sponsor's page carrying our pixel, we compute a one-way hashed identifier from network-level request attributes, using a secret rotating salt. That hash — a short string like b29d… — is what we store, alongside a timestamp and the show or page involved. It lets us notice that a download and a purchase likely came from the same household, which is the entire product.
What that hash deliberately is not:
- Not reversible. We do not store raw IP addresses — only the hash, which cannot be turned back into them. One raw request detail is stored alongside it: the user-agent string (the name a podcast app or browser announces, like AntennaPod/3.2), because industry-standard invalid-traffic filtering — separating real listeners from bots — requires it. A user agent identifies software, not a person; see the methodology for how it's used.
- Not a profile. No names, no emails, no ad IDs, no cross-site browsing history, no demographic data. We could not tell you who a listener is, and we've built it so we never can.
- Not permanent. The salt rotates, which severs the link between old hashes and new ones. Attribution works within its matching window and degrades by design after it.
- Not for sale. We do not sell, rent, or share listener or visitor data with anyone. It exists to produce our customers' attribution reports and for nothing else.
Podcasters (our customers)
We hold what running your account requires: your name, email, show details, and billing status. Payments are processed by our payment provider; we never see or store full card numbers. Your show's download and match data belongs to you — exportable as CSV at any time, as promised on our continuity page.
Retention and deletion
- Attribution data is kept while your account is active, so your reports can show history.
- Leave, and ask us to delete: we remove your show's data from our systems within 30 days and confirm in writing when done. Instructions are on the removal page.
- Listeners and sponsor-site visitors can email ceo@podattr.com with privacy questions or deletion requests; note that because we hold only irreversible hashes, we usually cannot connect any person to any record — the honest limit of both our data and our ability to delete "your" rows specifically.
Where data lives
PodAttr runs on Cloudflare (edge workers and the D1 database). Cloudflare processes requests as our infrastructure provider under its own privacy terms. We add analytics to podcast feeds — we do not add third-party advertising or tracking scripts to anything, including this website.
Changes to this policy
If we change this policy in any way that affects what's collected or how long it's kept, active customers get email notice before the change takes effect — not after.
Questions, concerns, or deletion requests: ceo@podattr.com. Last updated July 23, 2026.