This policy describes the native iiPTV app for iPhone and iPad and its current release. It is separate from the website Privacy Policy, which covers visiting iiptv.app, the browser player and Web tools. Privacy questions about the app can be sent to support@iiptv.app.
The native app does not require an iiPTV account and does not operate a developer-hosted library or automatic CloudKit sync. The current client has no developer analytics, advertising or cross-app tracking SDK. The app does not automatically upload your configurations or viewing history to the developer. User-selected source requests and information you deliberately share are described below.
Data kept on your device
The app stores configurations, parsed channel names and addresses, groups, channel edits, favorites, viewing history and playback positions in its local container. Source addresses and configured request headers may contain private tokens or other credentials. Language, appearance and playback preferences are also stored locally; app-owned language preferences use the system preference store.
Preview images and their technical metadata are cached on your device. The app can remove or replace cached items as part of its cache limits, and you can clear previews in Settings. A cached preview and a saved library are different: clearing previews does not delete configurations, favorites or history.
Files are read after you select them through the system file picker. Reading a playlist or backup does not give the app unrestricted access to all documents on your device. The app does not request access to your contacts, microphone, photo library or location for this workflow.
Requests to the sources you choose
Importing or refreshing a remote list, loading a logo or preview, and playing media contact the relevant source servers. A source can receive network information such as your IP address, request timing, the requested address and headers used for that request. A private URL or a header can contain credentials. HLS media can also request child manifests, segments and encryption keys.
Independent source operators and network providers handle their own records under their own practices. iiPTV does not control an independent source's records, availability or retention. Use sources you trust and are authorized to access. Plain HTTP traffic is not encrypted; HTTPS requests use normal system certificate validation rather than a custom bypass.
If you choose the iiPTV-hosted demo, its media requests reach the website's media host and can produce hosting records covered by the website Privacy Policy. Fetching that media is not the same as embedding the website's analytics script in the native app.
For media that requires configured headers, the system playback path can use an on-device relay bound to 127.0.0.1. It passes requests between the player on your device and the registered source. This local transport is not the website's Cloudflare media proxy and does not route your native-app library through a developer-operated cloud relay. The compatibility player uses its supported source-access path. Neither statement means an independent source host keeps no logs.
The app can pass media to system capabilities such as AirPlay or Picture in Picture when supported. A receiver, the operating system and the source may process information required for that operation. Consult their settings and policies when choosing an output destination.
Backups, copying and deliberate sharing
You choose when to export or share a backup through the system file or share interface. A backup can include configurations, media URLs, request headers, favorites and history. Treat that file as private data. The destination you choose, such as a file provider or another app, controls its own copy and data handling.
Copying an address or error writes the selected value to the system clipboard. Sharing a media URL can disclose the address and any credentials it contains. Sensitive-header masking in the interface is a display control: it does not remove the underlying value from a requested source connection or an intentional backup.
The native app does not implement automatic cross-device library sync. A manual file stored in iCloud Drive, or a system-managed device backup such as iCloud or Finder backup, is separate from an iiPTV-operated cloud service. Those copies depend on your platform settings and chosen destination. Clearing local data cannot recall exported files, clipboard contents or requests that a source has already received.
Information you choose to send to support
Using the feedback email link opens a mail workflow you control. If you send a message, the developer receives the sender address and the information or attachments you include. The email provider can process the message to deliver and manage that correspondence. The app's shared diagnostic summary contains app and system versions, not your private source addresses, headers or library contents.
Support information is used to investigate an issue, respond to a question or handle the request. Support correspondence is separate from the on-device library and may be retained according to the mailbox setup, the request and applicable requirements. There is no fixed response or deletion deadline promised on this page.
Before sharing, remove passwords, cookies, Authorization values, tokens and private media URLs from screenshots, backups, copied errors and logs. Use App Support for the reporting outline. A request concerning a source host's own records must go to that host; the developer does not hold your local library simply because you used the app.
Your controls and local-data retention
- In Settings, clear preview caches or viewing history, export or restore a backup, reset preferences, or reset local data. Read the confirmation before a replacement or reset.
- Remove a configuration or edit a saved channel or request parameter to change the local values used for later actions.
- Deleting the app removes its local container from that device. Original files, exported copies and system-managed backups are separate; use the relevant destination or platform controls for them.
- To ask about information you previously sent to support, email support@iiptv.app with enough context to locate the correspondence, without attaching unrelated credentials.
Local library data remains subject to your changes, the app's storage and history limits, and system storage behavior. The developer cannot remotely recover or erase a library that has not been sent to it. Keep an independent permitted backup when needed.
Components, websites and policy updates
The compatibility playback path includes VideoLAN/MobileVLCKit components. Their license and build notices are available in the app's Open-source licenses area. For corresponding-source materials for included LGPL-covered components, contact support with the app version and build so the request can identify the relevant distributed components.
Opening a website, including this policy, makes a separate website request. iiptv.app uses website hosting and Google Analytics as described in the website Privacy Policy; third-party sites use their own policies. Those Web requests are distinct from analytics code inside the native client.
The date at the top identifies this notice's revision. Update the app and review the current notice when a release changes how data is handled. For questions, contact support@iiptv.app.