Privacy Policy

Data kept on your device

The app can store your podcast library, episodes, playback progress, playlists, Playing Next queue, settings, audio downloads, and some image or audio-analysis caches locally. This data stays on your device unless you use iCloud sync or the web player described below.

iCloud sync

If an iCloud feature is enabled, some library and preference data may be synced through Apple's services, between your Apple devices. That data is then handled according to your Apple account's settings and privacy policy.

iCloud and the web player

The web player uses Apple CloudKit JS and Sign in with Apple to access Fennec Cast records in your private iCloud database. Apple handles the sign-in process; Fennec Cast never receives your Apple ID password.

The web player can display your podcasts, favourites, Playing Next, playback positions, and non-secure playlists. It can offer Playing Next and position changes back to iCloud. Secure playlists and their contents are never displayed on the web.

These records are handled under your Apple account settings and Apple's privacy policy. Network, quota, or account errors do not erase the player state kept locally in your browser.

Network, podcasts, and search

When you add or refresh a podcast, in the app or on the web player, the app contacts RSS feeds, podcast hosting services, image services, or Apple's public podcast search API to get the information needed to display and play content. These third-party services may receive technical information such as your IP address, the requested URLs, and the usual network metadata.

On the web, one RSS or Atom feed URL at a time is sent to a same-origin Cloudflare relay. The relay validates destinations and redirects, applies time, size, and rate limits, and does not cache the response. It does not store your library, listening history, Apple ID, or a feed list.

New-episode alerts

If you turn on new-episode alerts, public RSS metadata remains necessary to detect new episodes, and the pre-existing notification tokens used by the service remain necessary to deliver those alerts.

Installations associated with the same iCloud account are grouped using a pseudonymous hashed scope; the raw CloudKit identifier is never transmitted. Firebase keeps only minimal deduplication state: opaque hashes, delivery status, and technical timestamps. This state expires after 180 days. It contains no podcast or episode title, description, listening history, playback position, playlist, transcript, or chapter.

Analytics and diagnostics

Fennec Cast may produce local technical logs to help diagnose playback or performance issues. These logs stay on your device unless you voluntarily choose to share them to get help.

Local storage in the web player

The web player (fennec-podcast.com) keeps some data in your browser's local storage — your theme choice, cover images, and a cached copy of your synced library (subscriptions, playlists, Playing Next and playback positions) — so it loads quickly and remembers your place. This is purely functional: it stays on your device, is never used for advertising or tracking, and you can clear it at any time from your browser settings or by signing out.

Contact

For any question about this policy or to exercise your rights, contact the developer at the address used in TestFlight or App Store Connect.