Privacy-focused podcast listening with clear data boundaries

"Privacy-focused" is only meaningful if it names specific boundaries, so here are the ones that apply. No third-party advertising SDKs are embedded in the app to harvest behavior for ad networks. No advertising identifier is used to stitch your activity here into a cross-app profile. Listening history is never sold to data brokers, and it is never handed to outside advertisers for targeting. And core listening itself, as covered elsewhere on this site, doesn't require an account at all, so there's no identity to attach any of this to unless you choose to sign in. Those are structural facts about what is and isn't wired into the app, not a marketing promise sitting on top of tracking that still happens quietly underneath it.

"First-party product measurement" refers to a narrow, specific thing: aggregate signals like which screens get opened, whether a playback attempt failed, or whether the app crashed on a particular device or OS version. It exists to help the maker of the app find bugs and understand what's broken, not to build an advertising profile of an individual listener. It is collected by the app's own maker, never shared with outside ad networks or resold to brokers, and never tied to the specific episodes you personally chose to play for the purpose of advertising elsewhere. That is the meaningful line between ordinary product analytics and ad tracking, and it is a line many free, ad-supported apps blur or collapse entirely.

This measurement is off by default and is enabled only after a server-side policy check confirms it's allowed for your region and context, checked before any collection turns on rather than after. If that check is denied, times out, comes back unknown, or fails for any reason, collection simply stays disabled rather than defaulting to on, which matters because most systems default to fail-open. Where a region legally requires a consent prompt before any collection happens, that prompt is your literal control point: your answer decides it. Where no such prompt is legally required, the default-disabled, check-then-enable design is itself the safeguard against measurement quietly turning on in the background without anyone noticing or asking.

This is a different structure than an ad-funded free app, whose revenue depends on building detailed behavioral profiles, interests, location history, activity across other apps, in order to sell targeted advertising impressions, which gives it a built-in, ongoing incentive to collect as much as it can plausibly justify collecting. An app funded instead by an optional paid feature, like this one's Brain AI subscription, has no such incentive built into its business model: there's no targeting business on the other side waiting to be fed with your listening data. That's a structural argument about how the incentives point, not a claim that every ad-funded competitor is doing something improper, just a real reason the two models end up collecting differently.