English

1. Who we are

Zaptune is developed by Merve Akdeniz, an independent developer, who is responsible for the data described in this policy. Contact: [email protected].

Effective date: 20 October 2026.

2. Summary

• Zaptune is a player. It does not provide, sell or recommend any channels or other content.
• We have no user accounts and no server of our own.
• Your playlist details (server address, username and password) stay on your device and are sent only to your provider's server.
• To keep the app reliable we use anonymous usage statistics (TelemetryDeck) and crash reports (Sentry). You can turn off both in Settings.
• Purchases of Zaptune Pro are handled by Apple, and purchase records by RevenueCat.

3. Data that stays on your device

• Your playlists (name, server address, username), favorites, hidden channels, watch progress, reminders, recent searches, locked categories and settings are stored only on your device. They are never sent to us.
• The channel list, TV guide and images downloaded from your provider are kept as a cache on your device.
• Playlist passwords and the parental control PIN are kept in the iOS Keychain. They are not synced through iCloud Keychain.
• Your playlists, favorites and settings are included in your device backups. The channel list and TV guide cache are excluded from backups and are downloaded again when needed. Keychain items can be included only in encrypted backups.

4. Usage statistics (TelemetryDeck)

Provider: TelemetryDeck GmbH, Germany. Data is stored in the European Union.

What the app sends: events about how the app is used, for example: sign-in finished, setup finished, playback started, failed or ended, a tab opened, a feature used, a search made, a refresh finished, the Zaptune Pro screen shown, a purchase finished or restored, and once a day a summary of your settings. Every value is a category, an on/off value or a range (for example "2–5 playlists" or "1–10 seconds"). We never send names, server addresses, usernames, playlist or channel names, the text you search for, or exact numbers. At most 120 events are sent per session.

What the TelemetryDeck SDK adds to each event: app version and build; device model, operating system version, screen size, orientation and time zone; language and region; accessibility settings (such as larger text or reduced motion); the day and hour; usage summaries the SDK keeps on your device (number of sessions, days used, average session length, date of first use); and a random session identifier. When the app opens, the SDK also sends a "session started" event.