Privacy Policy — Zee2 Player

Last updated: 11 November 2026

1. Introduction

Zee2 Player is an IPTV player app for iPhone and iPad, published by Zee2 Group, founded by Rafek Gorgay ("we", "us"). This policy explains what the app does and does not do with your information.

Zee2 Player is a player, not a service. It ships no channels, films or television, and we run no servers that hold your data. The one server we do run is an optional hub that links your own devices to each other (section 4); a device you never link never contacts it. You supply your own IPTV subscription — an Xtream Codes account or an M3U/M3U8 playlist — and the app plays it. Everything the app builds from that subscription is kept on your device.

Because of that design, most of what a privacy policy usually describes does not apply here. We do not operate an account system or a data store that holds anything about you. The hub passes sealed messages between your devices and stores nothing on disk. There is nothing for us to sell, share or lose, because we never receive your playlists or your viewing in a form we can read.

This policy covers the Zee2 Player app itself. It does not cover your IPTV provider, whose own policy governs your relationship with them — see section 4.

2. Information we do not collect

We do not collect, receive or have access to any of the following:

Your name, email address, phone number or postal address
Your IPTV provider's username, password, server address or subscription details
Payment or billing information — the app takes no payments and has no in-app purchases
Your precise or approximate location, or any advertising identifier
What you watch, search for, favourite, download or record, in any form we can read
Contacts, photos, calendars, health data, or the contents of any other app

Your IP address is the one exception, and only if you link devices: the hub sees the IP address of each request it receives, as section 4 explains. If you never link a device, no IP address of yours reaches us from the app.

Zee2 Player has no user account of its own. There is nothing to register for, and no sign-up step that could collect these details. Linking devices uses no account, no email address, no device ID and no hardware address.

The app's privacy manifest declares no tracking and no tracking domains.

3. What the app stores on your device

Everything below stays in the app's own storage on your device. It is never transmitted to us, except that devices you have linked exchange some of it with each other, sealed, through the hub (section 4).

Your playlists and catalogue. When you add a playlist, the app downloads it from your provider and stores the resulting catalogue — channels, films, series, episodes, categories and TV guide programmes — in a local database inside the app's private storage.

Your activity within the app. Favourites, resume positions, watch history, hidden items and hidden folders, learned playback preferences, and download records. These exist so that the app can show you where you left off; they are rows in the same local database.

Your settings. Appearance, playback and buffering preferences, subtitle size, guide refresh interval, parental-control preferences, and similar choices, stored in the standard iOS preferences store.

Secrets. Provider passwords, parental PINs, secrets belonging to a custom TV-guide address, and, if you link devices, the household key that seals what your devices exchange. These are stored in the iOS Keychain — see section 5.

Linked devices. If you link devices, each one also keeps the list of devices in its household and their names, which you can rename. A device that is never linked holds none of this.

Downloaded and recorded media. See section 8.

Unlinking a device deletes its household key. Deleting a playlist removes its catalogue, its guide data, your favourites and history for it, its Keychain entry, and any playlist file you imported. Deleting the app removes all of it.

4. Your IPTV provider, and every other server the app contacts

Using an IPTV app necessarily means talking to your provider. To fetch your playlist, refresh your guide, and play anything at all, the app sends requests to the server address you entered, authenticated with the credentials you entered. Your provider therefore sees your IP address, which titles you request, and when. That is your provider's system, not ours. We have no visibility into it and no control over it, and their privacy policy — not this one — governs what they do with it. Choose your provider accordingly.

This is the complete list of network destinations the app can reach. Nothing is contacted before you add a playlist, the hub is contacted only after you link a device, and only the first two ever receive a credential.

Destination	When	What it receives
Your provider's server — whatever address you entered	Playlist and catalogue sync, guide refresh, background refresh, per-title detail lookups, every stream, catch-up, download and recording	Your provider username and password, as the provider's own API requires
A custom TV-guide address, if you set one	Guide refresh	Only a secret embedded in that address, if it has one
Artwork hosts named by your provider	Loading posters, backdrops and channel logos	Nothing we add. These URLs come from your provider's own metadata and often point at third-party image hosts, so those hosts see your device's IP address and which images it requested
The Zee2 hub, which we host, only after you link a device	Linking two devices, keeping them in sync while both are open, "Continue on TV", and typing on a phone into a TV's search	Your device's IP address, and messages sealed on your device with a key only your devices hold. No playlist address, username or password, and nothing we can read

Two further addresses are links, not requests: the "Watch Trailer" button opens a YouTube URL your provider supplied, and the About screen links to third-party licence and source-code pages. Both hand off to Safari or another app; Zee2 Player itself makes no request to them.

There is no other destination. Apart from the optional hub, the app has no endpoint of its own, and it does not contact any third-party metadata, recommendation or advertising service.

The hub, in plain terms

The hub is one small server that we run. Linking is your choice; until you link a device, the app makes no request to it. Once you have, the app connects only while it is open.

What it can see. That something is connected at an address that looks random and cannot be traced to you; the size and timing of the sealed messages; and the IP address of each request. It can hold one sealed "last watched" message for your household in memory for up to 24 hours, so a TV opened later can show the right title first. It cannot read that message, and it is never written to disk.
What it cannot see. Your playlist addresses, usernames and passwords (passwords never travel between devices at all), what you watch, favourite or hide, your PIN in any form, your settings, your device names, or who you are.
What it keeps. Nothing on disk. Restarting the hub forgets everything it was holding.
The request log. Our web server keeps a request log of each visitor's IP address and the time of the request, for 7 days, to detect intrusions; it contains nothing about your playlists or what you watch.
The QR code. Scanning it with your camera opens a page on our website. Your browser sends us its IP address like any web request; the part of the link after the # holds the pairing key and is never sent to us.

Your IPTV provider still sees your IP address, and plays your video directly. Video never passes through the hub.

This website

This website sets no cookies, runs no analytics and loads no scripts, fonts, images or videos from other companies, and shows no ads. Our web server's request log is the one described above: your IP address, the time and the page, kept for 7 days. If you choose a language on this site, the choice is remembered in your browser's own storage on your device. It is not a cookie and it is never sent to us.

5. Credentials, and how they are protected

Your provider password is stored in the iOS Keychain — never in the app's database, never in a log, and never in a diagnostics export. The same applies to your parental PIN, to any secret in a custom guide address, and to the household key that seals what your linked devices exchange. The key is never sent to the hub in a form the hub can open, and never leaves the device in a backup.

Keychain items are stored with device-only accessibility. They are not synchronised to iCloud Keychain, not shared with any other app, and not carried into an encrypted device backup.

Address fields in the app hold a credential-free form of the URL. When a link you paste contains a password, the app removes it from the stored address and moves it to the Keychain, which is why the field afterwards shows an empty password. The password is put back only to make a request to your provider.

Revealing a saved password on screen requires device-owner authentication first — Face ID, Touch ID or your device passcode. A revealed password is re-masked automatically after a short timeout and whenever the app leaves the foreground, so that it does not appear in the app-switcher snapshot.

An honest limitation you should know about

Xtream-style providers embed your username and password inside the stream URLs themselves, in the form /live/{username}/{password}/{id}. Those URLs have to be stored to be playable, so for providers that use this scheme your subscription credentials are present inside the app's local catalogue database, even though they are not in any password column.

That database is in the app's private storage, unreadable by other apps. However, it is included in device backups. An unencrypted iTunes or Finder backup of your device therefore contains your IPTV subscription credentials. Encrypting your device backup protects them. We state this rather than imply a protection that the format of these URLs does not permit.

6. Plain HTTP connections

Most IPTV panels are self-hosted, serve plain http:// on a custom port, and have no TLS certificate. The app therefore allows cleartext connections; restricting it to HTTPS would make it unable to reach most of the services its users already pay for, and there is no fixed list of hosts to permit because every installation points somewhere different.

The consequence is worth stating plainly: if your provider's address begins with http:// rather than https://, your username and password travel across the network unencrypted on every request, and anyone able to observe that network can read them. This is a property of your provider's server, not of the app. Prefer an https:// address when your provider offers one, and be cautious on public Wi-Fi.

7. Diagnostics, logging and support

The app writes playback diagnostics to the standard iOS system log on your device. Nothing is uploaded. Credentials, stream tokens and URLs are redacted at the point they are logged.

Settings → About → Share Diagnostics builds a support report that you choose to share, with whomever you choose. It is never sent automatically and never sent to us unless you email it.

The report is built on the principle of presence, not value: it records that a setting is configured, not what it is set to. It contains:

App version and build, iOS version, device model class (for example "iPhone" — never your device's name), language, and the time it was generated
Playlist counts, and for the active playlist: its kind, dates, guide time-shift, and yes/no flags for whether a custom guide address, User-Agent or Referer is set
A provider fingerprint — a truncated SHA-256 hash of the server address and username, computed with no password as input. It cannot be reversed into either. It exists so that two reports from the same person can be recognised as related
Catalogue and guide counts, provider capability values, and sync statistics
Your settings values, whether a parental PIN exists (never the PIN), and whether App Lock is on
The last 50 playback log events

Before the report can be shared it is scrubbed twice. Known values — the usernames, passwords and provider hostnames actually held in the Keychain — are replaced, and separately every URL, hostname, IP address, email address, file path, credential-bearing parameter and high-entropy token is removed by pattern. The finished text is then re-checked, and if any known secret somehow survived, the app refuses to share the report at all.

8. Downloads and recordings

Downloads are stored in the app's private storage. They are limited to Wi-Fi by default, and Settings → Downloads shows the space used and offers Delete for a single download and Delete All.

Recordings are live-TV only and are written to the app's Documents folder, which appears in the Files app under "On My iPhone → Zee2 Player". This is deliberate — it is how you get a recording off the device — but it means a recording is a visible file that is reachable without opening the app, and is therefore outside the app's parental-control filter. Downloads and recordings are both included in device backups.

9. Children and parental controls

Zee2 Player is not directed to children. It is a general-purpose media player intended for adults who hold their own IPTV subscription, and we do not knowingly collect any information from anyone, including children — as described above, we collect nothing from anyone at all.

All content comes from your provider, and we neither supply nor moderate it. Because IPTV playlists commonly include adult material, the app provides parental controls: an adult-content filter, the ability to hide individual items and whole folders, and an optional PIN. The PIN is stored in the iOS Keychain under its own entry, so deleting a playlist cannot remove it. Devices you have linked share one stored one-way form of the PIN, sealed in transit; the digits themselves never leave the device you typed them on. There is also an optional App Lock that requires Face ID, Touch ID or your device passcode to open the app.

The adult filter classifies titles by name and by the categories your provider labels; it is a best-effort guess over provider-supplied text and will not be perfect. Until a PIN is set, it behaves as a display preference that anyone using the device can switch off. Parents should treat it as one layer alongside iOS Screen Time, not as a guarantee.

10. Advertising, analytics and tracking

Zee2 Player contains no advertising, no analytics, no crash-reporting SDK and no telemetry of any kind. It does not track you across apps or websites, does not use cookies or advertising identifiers, and contains no third-party tracking code. There is no data to sell, and we sell none.

The app's only third-party components are the media, database and image libraries listed on the About → Acknowledgements screen. None of them reports to us or to their authors.

11. Security

Secrets are held in the iOS Keychain with device-only accessibility, not in the database and not in preferences
Stored addresses are kept credential-free; passwords are re-attached only for the request itself
Every path by which a URL can reach a log, an error message, an on-screen message or a diagnostics export passes through a redactor first
Revealing a saved secret requires device-owner authentication, and revealed secrets are re-masked on a timeout and when the app leaves the foreground
App data lives inside the iOS application sandbox and is not readable by other apps
Everything your linked devices exchange is sealed on the sending device with a key the hub never has, so the hub, and anyone watching the network, sees only sealed bytes

No system is perfectly secure. The limitations we know of are stated in sections 5, 6 and 8 rather than omitted.

12. Your choices and your rights

Because your data stays on your devices, you exercise these rights directly rather than by asking us — we hold no readable copy of anything to disclose, correct or delete.

Access and portability. Your recordings are ordinary files in the Files app. A diagnostics report can be generated and read at any time
Deletion. Delete a playlist to remove its catalogue, guide, favourites, history and stored credentials. Delete downloads individually or all at once. Clear the stored guide. Unlink a device and it forgets its household key; there is nothing on the hub to delete. Deleting the app removes everything it holds, and iOS removes its Keychain items with it. The hub's one held message expires within 24 hours and its request log within 7 days
Control. Parental controls, App Lock, Wi-Fi-only downloads, background refresh and metadata enrichment are all settings you control. Linked devices and Continue on TV stay off until you link a device, each kind of data has its own sync switch in Settings → Devices, and you can remove any device from the household
Provider data. For anything your provider holds about you, contact your provider — we cannot access, export or delete it

If you are in the EEA, the UK, California, or another region with statutory data rights, the practical position is close to the same: a subject-access or erasure request to us would return no account, profile, playlist or viewing data, because we hold none. The one personal datum we do process is an IP address, in transit when you link devices and in the 7-day security log described in section 4; we cannot connect it to a person without being told the address. Your provider may well be a controller for your subscription.

13. Changes to this policy

If the app's behaviour changes in a way that affects this policy, this document will be updated and the "Last updated" date at the top will change. Material changes will also be reflected in the App Store privacy information for the app. Continuing to use the app after an update means you accept the revised policy.

14. Contact

Questions about this policy or about privacy in Zee2 Player:

Zee2 Group — zeetwogroup@gmail.com

The same address appears in the app under Settings → About → Support.