Privacy Policy

Last updated: August 7, 2026

Klave is an IPTV player for iPhone, iPad, Mac, and Apple TV. It is built to be privacy-first: your provider credentials and your library live on your device and in your own private iCloud. We run no advertising and no tracking, and our servers never see who you are or what you watch.

The short version

• We do not create accounts, track you, run ads, or use third-party analytics or tracking SDKs.
• Your IPTV credentials are stored in the device Keychain and are never sent to Klave.
• Your favorites, ordering, watch history, and settings sync through your own private iCloud — we can't see them.
• Our metadata service only ever receives cleaned movie/show titles to look up artwork — never your identity or credentials.
• If Klave crashes, it offers to send us the crash report — only if you tap "Send Report".
• There is an optional "Share diagnostics" setting, off by default. Turn it on and Klave sends anonymous performance data (no identifier of any kind) to help us fix freezes and slowdowns.
• You can optionally link a Trakt account; if you do, your watch activity goes to Trakt.

1. Who we are

Klave ("Klave", "we", "us") is the developer of Klave: IPTV Player, distributed on the Apple App Store. This policy explains what data the app handles and how. It applies to the Klave apps and the Klave metadata service described below.

2. Information we do not collect

Klave has no Klave account and no sign-up. We do not collect your name, phone number, contacts, location, or device identifiers for advertising. The app contains no advertising SDKs, no third-party trackers, and no analytics SDKs. We do not sell or share personal data.

There are exactly four cases where information leaves your device and reaches us, each of which you turn on or trigger yourself: a crash report you choose to send (section 6), performance diagnostics if you switch on "Share diagnostics", which is off by default (section 6), a support message you choose to write (section 7), and the title lookups our metadata service performs (section 5). Nothing in any of them identifies you.

3. Your IPTV provider credentials

To watch your streams, Klave needs the connection details for the IPTV service you already subscribe to (for example a provider URL, username, and password, or an M3U playlist URL). These are your credentials for a third-party service.

• Credentials are stored locally in the iOS/macOS/tvOS Keychain, never in plain text.
• With iCloud Keychain enabled, they may sync across your own Apple devices, encrypted by Apple.
• Credentials are never transmitted to Klave's servers. They are used only by the app on your device to connect directly to your IPTV provider.

4. Your library and preferences (iCloud sync)

Klave keeps your library on your device and syncs a small overlay of your choices across your devices using your private iCloud database (CloudKit). This is tied to your Apple Account, not to any Klave account.

• What syncs: a reference to your playlist/source, category and channel ordering, hidden items, favorites, theme and preferences, and watch history.
• What stays on device: the full parsed channel catalog and the artwork cache, which are regenerated from your source as needed.
• Because this lives in your private iCloud database, neither Apple nor Klave can see its contents, and we operate no servers that store it.

5. The Klave metadata service

To show posters, descriptions, ratings, accurate titles, and sports schedules, the app queries a Klave-run metadata service. That service calls The Movie Database (TMDB) for artwork and details, OMDb for IMDb and Rotten Tomatoes scores, and a number of public sports data feeds. Your device talks only to the Klave service; the Klave service talks to those providers on your behalf, without passing along anything about you.

• What is sent: a cleaned title and year (e.g. "Dune 2021") so the service can resolve it to a canonical movie/show and return artwork and details.
• What is not sent: your identity, your IP-derived profile, your credentials, your playlist, or which specific streams you watch.
• Results are cached on the service so that titles already resolved by anyone come back instantly. The cache holds public catalog metadata, not personal data.
• Standard, short-lived web server logs (such as request timestamps) may be processed to operate and protect the service; they are not used to profile or identify you.

This product uses the TMDB API but is not endorsed or certified by TMDB. Movie and TV metadata and images are provided by TMDB and remain subject to TMDB's terms. Ratings data is provided by OMDb and remains subject to OMDb's terms.

6. Crash reports and diagnostics

If Klave crashes, it captures a diagnostic report on your device. The next time you open the app it tells you what happened and offers to send it. Unless you turn on "Share diagnostics" below, nothing is uploaded unless you tap "Send Report".

• What a report contains: the crash type and reason, the call stack, the Klave version and build, the platform, the OS version, and — only if you type one — a note you write yourself.
• What it does not contain: your identity, your credentials, your playlist, your library, or what you were watching.
• Reports go to Klave's own server. They are not shared with any third-party crash-analytics provider, because we don't use one.
• They are retained only as long as needed to diagnose and fix the bug.

"Share diagnostics" — optional, off by default

Klave has an optional Share diagnostics setting, offered once in a prompt and available any time in Settings. It is off unless you turn it on; leaving it off is fully supported and the app behaves identically. Turning it on does two things: it lets Klave send performance diagnostics, and it lets crash reports upload on the next launch without asking you again each time. That second part is the point of the setting — with it on, crash reports are no longer individually prompted.

• What is sent: aggregate performance summaries from Apple's MetricKit (launch times, hang time, memory and disk figures), app-freeze reports, memory-pressure and excessive-disk-write events, and a short trail of the app's own technical log lines — each stamped with the Klave version and build, the platform, and the OS version.
• What those log lines are: structural breadcrumbs only — which launch step or screen type the app was in ("movieDetail", "player.open.live"), and disk and memory figures. They deliberately carry no titles, no URLs, no credentials, and no identifiers.
• What is not sent: any account or device identifier, your credentials, your playlist, your library, or what you were watching. The events carry no ID of any kind, so they cannot be tied back to you or joined together into a profile.
• This is not advertising or usage analytics. We do not measure which features you use, and no third-party analytics SDK is involved — the data goes to Klave's own server and nowhere else.
• Turn it off at any time in Settings. Klave stops sending immediately and discards anything still queued.

7. Support messages

Settings → Contact Us, and the form on our support page, send your message — plus an email address if you choose to give one, so we can reply — to Klave. The message is delivered to our private team chat (a Discord webhook) so it reaches a person. It is used only to answer you, never to market to you, and never added to any mailing list.

8. Optional connected services (Trakt)

Klave can optionally connect to Trakt, a third-party watch-tracking service, from Settings → Connected Services. This is entirely opt-in and off by default; Klave works fully without it.

• You sign in with Trakt's own device-code flow. Klave never sees your Trakt password. The resulting access token is stored in your device Keychain.
• If you connect it, Klave sends your watch history, playback progress ("scrobbles"), and watchlist to Trakt, and reads the same back. This is the entire point of the integration.
• That data is handled by Trakt under Trakt's privacy policy, not ours. Klave's servers do not store it.
• Disconnect at any time from Settings; Klave discards the token and stops sending anything.

9. Sharing a list with other people

If you choose to share a curated list, Klave uses Apple's CloudKit Sharing (CKShare). Sharing only ever happens when you start it yourself, from Settings → Sources → Share this list. Nothing is shared automatically, and Klave never shares a list on your behalf.

What is shared. Not your library — the list itself. Klave publishes which provider the list comes from, the login for it, and the way you have arranged it (your category order, the channels and categories you have hidden, your favourites and any names you have changed). The person you share with does not receive your watch history, your other sources, or any of your own settings. Their device fetches the channels from the provider directly, using what you shared, and shows them arranged the way you arranged them.

The login. The source credential is carried inside the shared record, which Apple end-to-end encrypts — Apple cannot read it, and neither can we. It is there so the recipient's app can play the streams. Klave never displays it to them, gives them no way to edit it, and stores it on their device only, without copying it into their iCloud Keychain. We should be straightforward about the limit of that: sharing a list means giving someone access to your subscription, and a determined recipient with access to their own device could recover the login from it. Share lists only with people you would be comfortable giving your provider login to.

The invitation link. Sharing produces an iCloud link that you send yourself, through Messages, Mail, AirDrop or anything else. Anyone who ends up holding that link can accept it and watch. Klave shows you everyone who has accepted, lets you remove any of them, and lets you stop sharing entirely at any time — which revokes everyone's access at once and deletes the shared record, and the login inside it, from iCloud.

Read-only. People you share with can watch the list but cannot change it. Their own favourites, hidden channels and watch history stay entirely separate from yours, and nothing they do flows back to you.

10. Third-party services

• Your IPTV provider: when you play a stream, your device connects directly to your provider. Their handling of your data is governed by their own policy, not ours.
• Apple iCloud: sync and sharing rely on Apple's iCloud/CloudKit, governed by Apple's privacy policy.
• TMDB: metadata and images originate from TMDB, governed by TMDB's terms and privacy policy. Klave's service calls TMDB; your device does not.
• OMDb: IMDb and Rotten Tomatoes scores originate from OMDb. Klave's service calls OMDb; your device does not.
• Trakt: only if you opt in (section 8). Your watch activity is then handled under Trakt's privacy policy.
• Discord: support messages you send are delivered to our private team channel via a Discord webhook (section 7).
• YouTube: recap, review, and trailer rails link out to YouTube. Following a link hands you to YouTube, governed by Google's privacy policy. Klave embeds no YouTube tracking.
• Google Cast: the iPhone and iPad app includes Google's Cast SDK so you can send playback to a Chromecast or other Cast device. It is used only when you open the Cast picker or cast something; anything it reports back to Google at that point is governed by Google's privacy policy. Klave itself receives nothing from it.

11. Children's privacy

Klave is not directed at children and does not knowingly collect personal information from children. The app plays content from sources you configure; that content is outside our control.

12. Data retention and deletion

Because your data lives on your device and in your private iCloud, you are in control of it:

• Use the in-app "clear cache" control to remove the local catalog and artwork cache.
• Remove your stored credentials from within the app, or delete the app to remove its on-device data and Keychain items.
• Manage or delete your synced data through your Apple device's iCloud settings.
• The metadata service stores only public catalog data and no personal profiles, so there is no personal account to delete there.
• Crash reports and support messages are not tied to an account. To have one removed, email us with enough detail to find it.
• Disconnecting Trakt in Settings stops all further sync; deleting the data already held by Trakt is done through your Trakt account.

13. Changes to this policy

We may update this policy as the app evolves. If we ever add analytics, advertising, or any automatic (non-opt-in) collection, we will disclose it here and in the App Store privacy label before it ships. Material changes will be reflected by the "Last updated" date above.

14. Contact