We've made ourselves replaceable on purpose.

The only reason to stay with PodAttr should be that we're good — never that leaving is hard, or that our failure would take your tracking down with us. This page is the commitment that backs that up, in writing, before you need it.

Why this page exists

Chartable was a reliable measurement tool for podcasters — until Spotify acquired and shut it down with roughly ten weeks' notice. Every customer's attribution data and integrations went dark on Spotify's timeline, not theirs. Nothing about Chartable's reliability record predicted that outcome, which is exactly the point: a track record of uptime tells you nothing about what happens the day the company changes hands or runs out of runway. We think that risk should be underwritten structurally, not promised away.

A 12-month minimum wind-down notice

If PodAttr is ever sold, shut down, or otherwise stops operating as an independent service, every active customer gets a minimum of 12 months' written notice before the service is switched off — more than six times Chartable's ~10 weeks. That window exists to give you time to export your data, stand up a self-hosted replacement using the open-source worker below, or move to another vendor, on your schedule.

This commitment is written into our terms of service as a contractual obligation that survives a sale of the business — meaning it binds any acquirer, not just us. A buyer inherits the notice obligation along with the customer relationships. That matters because "acquired, then quietly discontinued" is exactly how Chartable ended; a promise that evaporates at the moment of acquisition protects you from nothing.

The prefix worker is open-source, from day one

The redirect worker every customer's podcast feed routes through — the piece whose failure would actually hurt you — is published as MIT-licensed, self-hostable source at github.com/podattr/podattr-prefix. It is not a promise to open-source it later if we wind down; it is already public today, under a fresh repository (not carrying our internal history), so any customer's developer can fork it, deploy it on their own Cloudflare account, and point their feed at it directly. Worst case, your tracking keeps running on infrastructure you control, indefinitely, with or without us.

The matching engine, sponsor reporting, dashboard, and everything else that turns raw download and conversion logs into an attribution report stay closed. That split is deliberate: we open-source the piece whose absence would hurt you, and keep closed the pieces whose absence would only hurt us.

Full data export, always

Every download and every matched conversion your show has generated is exportable as CSV on demand, at any time — not only during a wind-down. There is no minimum tenure, no retention hostage, and no premium tier gating your own history. See methodology for exactly what data is collected.

And if the founder disappears?

PodAttr is currently a one-person company, and you're right to ask the bus-factor question. The honest answer: the closed parts of the product — matching, reports, the dashboard — would eventually stop being maintained. But the part that touches your feed is already public, already documented, and already deployable by anyone, and data export is self-serve, so neither depends on the founder being reachable. The failure mode is "the reports stop improving," not "your show breaks."

Don't take our word for it

• Read the prefix worker's source and self-host guide: github.com/podattr/podattr-prefix
• Read how every number is produced: methodology
• Watch our uptime, permanently public: status page
• Read the exit before you enter: removal

What this does and doesn't cover

Read the prefix worker's source yourself: github.com/podattr/podattr-prefix. Questions about this commitment: ceo@podattr.com. Last updated July 23, 2026.