Privacy policy
Last updated: 2026-11-18
This policy explains what personal data the Zapo app (package com.imparator.zapo, on Google Play, the Amazon Appstore and the Samsung Galaxy Store as “Zapo Player”) and the website zapoplayer.app process, why, and what your rights are. We keep it short and specific: if something isn’t listed here, Zapo doesn’t collect it.
Who we are
Unismed BV, Kraaistraat 23, 3920 Lommel, Belgium, VAT number BE0738437442, is responsible for this processing (the “controller” under the GDPR). Questions or requests: info@zapoplayer.app.
In short
- Zapo is a media player. It has no channels of its own: you add a playlist from your own provider.
- Your playlist and its login stay on your device, encrypted. The app talks to your provider directly, not through us. Only if you have Premium and use cloud backup does an encrypted copy go to your account, so your other devices can use it.
- No ads, no advertising ID, no selling of data. The app sends usage statistics (which screens and features are used, never your playlists, channels or what you watch) to Google Analytics; you can switch that off in Settings. This website uses Google Analytics only if you allow it.
- A Zapo account (email and password) is only needed for Premium.
What the app processes
1. Your playlist (on your device)
The M3U link, Xtream Codes server, username and password, or the playlist file you add are stored on your device, encrypted with a key that is bound to that device. Android’s own device backup is switched off for Zapo; to use your playlists on another device, Premium has its own encrypted cloud backup (section 10). To load channels, the TV guide, movies and series, the app connects directly to the provider you added. That provider has its own privacy policy.
2. Adding a playlist with your phone (QR code)
If you choose to type your playlist on your phone, the details travel from your phone to your TV through our server. They are kept encrypted in a temporary file for at most 30 minutes and deleted as soon as your TV has collected them. They never go into a database. The one-time code is random, works only for that TV, and expires after 30 minutes.
3. Your Zapo account (optional, for Premium)
- Email address and password, to create the account and sign in.
- Your device’s MAC address, sent when you create an account and each time you sign in. Premium works on up to 3 devices per account; the MAC address tells your devices apart and lets us block misuse.
- Premium status: whether Premium is on, your plan, end date and trial end date.
- Sign-in tokens, valid for one hour.
Free trial without an account. To start and check the 7-day trial, the app sends the device’s MAC address. Every device gets one trial. To stop trials being restarted, we permanently remember which MAC addresses have used theirs, also after an account is deleted.
4. Buying Premium
In the Google Play version, Google processes the payment; we never see your card or bank details. To check the purchase and switch Premium on, our server receives the purchase token, the product and a coded account number (a one-way hash of your Zapo user ID) and verifies it with Google.
In the Amazon Appstore version (Fire TV), Amazon processes the payment; we never see your card or bank details. To check the purchase and switch Premium on, our server receives the receipt ID, the product and your Amazon user ID (an ID that Amazon creates for Zapo; it isn’t your Amazon login or email address) and verifies them with Amazon. We keep these with your Zapo account, so we can check the purchase again. When a subscription renews, is cancelled or is refunded, Amazon tells our server which receipt changed. The Amazon Appstore also checks that the app on your device was installed from the Appstore; that check happens between your device and Amazon.
On this website, you enter your email address and pay on the secure page of our payment provider Stripe (Stripe Payments Europe, Ltd., Ireland). Stripe receives your email address, name, billing address and payment details, and processes them under its own privacy policy; we never see your card or bank details. Stripe tells us what you bought, the amount, the VAT and your country, and gives us a customer number. We keep, with your Zapo user ID: the plan, the amount, the partner code if you used one, the Stripe customer and payment numbers, the status (for a yearly plan: when it renews or ends) and when you bought it. We then tell our account server to switch Premium on for your account, and off again when a yearly plan ends or a payment is refunded. Stripe also uses the data to prevent fraud. If there’s no Zapo account for your email yet, you choose a password after paying and we create the account on our account server; the website doesn’t keep the password. To manage a yearly plan later on “My account”, you log in with a one-time link that we email you (it works for 30 minutes).
5. Movie and series information (optional)
With the Premium setting “Movie information” on, the app sends movie and series titles (with the year) to our server, which looks them up at The Movie Database (TMDB). TMDB never receives who you are. Answers are cached on our server and shared by all users. Posters, backdrops and cast photos load directly from TMDB’s image server, which sees your device’s IP address, as any website would. You can switch this off in Settings.
6. Update check (version from the website only)
The version of Zapo downloaded from our website checks unismed.be/download/version.json at start-up and every 6 hours to see whether a newer version exists. Only the normal web request is sent (IP address and app name). Versions from an app store (Google Play, Amazon Appstore, Samsung Galaxy Store) don’t do this; their store updates them.
7. TV home screen
On Android TV, titles you’re watching and your favourite channels appear in rows on the TV’s home screen; this data stays on the TV. On Google TV, titles you’re partway through (name, picture, progress) can appear in Google TV’s “Continue watching” row through Google’s Engage service. This is kept on that device only; a random ID is used instead of your account, and no email or name is shared. Locked channels and titles are never shown there.
8. Services you choose yourself
- Encrypted DNS (Premium setting): if you pick Google, Cloudflare, Quad9 or AdGuard, that service handles the app’s DNS lookups.
- Trailers play from YouTube; YouTube’s privacy policy applies.
- Chromecast (phones and tablets): the address of the stream is sent to your Cast device, using Google Cast.
9. Stays on your device
Watch history, resume positions, favourites, your channel order, hidden and locked channels, settings, recordings and downloads are stored on your device. The parental PIN is stored as a one-way hash. A backup you export is written to a file you choose; playlist logins are only included when you protect the backup with a password, and then they are encrypted. With cloud backup (section 10), an encrypted copy of most of this goes to your account.
10. Cloud backup (Premium)
With Premium, the app keeps a backup of your playlists and settings with your Zapo account, so that a new device signed in to the account is set up in a moment and your devices stay the same. It is switched on by default when you sign in with Premium; you can switch “Back up automatically” off, or delete the backup, in Settings › Backup & restore.
- What it holds: your settings; the playlists you added with a link or a server, with their names and logins (link, server, username and password); favourites; watch history and resume points; your changes to groups and channels (order, hidden, locked, names); and the name of the device that made the backup. Playlists from a file on your device are left out.
- Encrypted before it leaves your device (AES-256), and stored only in that form, as a file on our account server (at most 5 MB per account). We don’t open or read the contents of backups.
- Only with Premium: uploading and restoring need Premium. When Premium ends, the backup is kept for 90 days, so you can still renew; after that it is deleted for good and can’t be recovered.
- When you delete your account, its backups are deleted at once.
- Misuse: you may only back up playlists you’re allowed to use. Anyone can report an account that keeps illegal playlists in its backup to abuse@zapoplayer.app. If a report is well-founded, we delete that account’s backups, without opening them, and may block the account.
11. Usage statistics (Google Analytics for Firebase)
To see which parts of Zapo are used and what to improve, the app sends usage statistics to Google Analytics for Firebase (Google Ireland Limited). It is on by default; switch it off in Settings › Share usage statistics, and from then on nothing is sent.
- What the app sends: which screens you open and which features you use (for example the player menu or the connection test), by fixed names; and which version of Zapo it is (store, app version), the kind of device (TV, phone or tablet), the design you chose and whether Premium is on.
- What Google adds: a random ID for this installation of the app (it changes when you reinstall), the device model, Android version, language, an approximate location (country and region) that Google derives from your IP address, and when sessions start and how long they last.
- What it never gets: your playlists, channels, titles or anything you type, your email address or Zapo account, the advertising ID or the Android ID. We don’t link the statistics to you or your account, and they aren’t used for advertising.
- Google keeps the statistics for at most 14 months.
App permissions
| Permission | Why |
|---|---|
| Internet, network state | Play streams and notice when the device goes offline. |
| Notifications | Recordings, downloads and subscription reminders. |
| Foreground service | Keep recordings and downloads running in the background. |
| Exact alarms | Start planned recordings and reminders on time. |
| Start on boot, display over other apps | Only for the optional “Start on boot” on TV; Android requires both. |
| TV home screen data | The Zapo rows on the Android TV and Google TV home screen. |
This website
- Cookies: one session cookie (
zapo_session) on the partner pages, the checkout and “My account”, set only when you open them. It keeps you logged in and protects forms against misuse. It is strictly necessary, holds no personal data itself, and ends when you close the browser or after 8 hours without activity. When you log in here with an email link, the session remembers your email address and account number until you log out or it ends. - Google Analytics, only with your consent. The first time you visit, a banner asks whether we may use Google Analytics (Google Ireland Limited) to see how visitors use this website: how many visit, which pages they open and where they come from. Only if you choose “Accept” does your browser load Google Analytics. It then sets cookies (
_gaand_ga_…, kept up to 2 years) with a random ID, and sends Google the pages you open (without anything after the “?” in the address), the page you came from, your browser, device type, screen size, language and an approximate location (country and city) that Google derives from your IP address. We don’t link this to your account or email address, and we don’t use it for advertising. Google keeps this data for at most 14 months. If you choose “Decline”, nothing is loaded from Google and no analytics cookie is set. Your choice is saved in your browser (local storage, not a cookie), and you can change it at any time with “Cookie settings” at the bottom of every page. - No other trackers, and no fonts or other scripts from other companies: everything else is served from our own server.
- Server logs: like any web server, ours records technical data about each request (IP address, time, page, browser). These logs are kept for 30 days, for security and to fix problems.
- Emails you send us (for example to delete your account), kept as long as needed to handle them.
Partner programme (optional)
If you create a partner account to share a code, we process:
- Your account: name, email address, password (stored only as a secure hash), your code, your language, and when you signed up and last logged in.
- Payout details you enter: whether you receive payouts privately or as a company (company name and VAT number), your address, and your IBAN or PayPal email. The address, IBAN and PayPal email are stored encrypted and used only to pay you.
- Sales with your code: date, amount, your commission, and whether the code came from your link or was typed in. You never see who the buyer is.
- Payout requests and their status, with a copy of the payout details used.
- Login protection: failed logins and password-reset requests are recorded for one day as a keyed hash of the email address and IP address (not the address itself), to block password guessing.
- Password-reset emails, with a link that works for 60 minutes.
Buying with a code: when someone buys Premium with a partner code, we record which code was used, so we can give the lower price and the extra devices and pay the partner’s commission. The partner doesn’t learn who bought.
Why we may process this (legal bases)
- Cloud backup (performance of a contract): storing the backup you make with Premium; and our legitimate interest in handling reports of misuse and deleting backups after Premium has ended.
- To provide what you ask for (performance of a contract): your account, Premium, purchases, adding a playlist with your phone, and features you switch on.
- Our legitimate interests: understanding which parts of the app are used, to improve it (usage statistics; you can object by switching them off in Settings), preventing misuse of the free trial and of accounts (MAC addresses, the permanent trial record), keeping our servers secure (logs), and telling you about updates (update check).
- Legal obligations: keeping payment records for accounting, including sales with a partner code and partner payouts.
- Your consent: Google Analytics on this website. You can withdraw it at any time with “Cookie settings”.
Who receives data
- Our hosting providers, which run our servers for us and store what we keep there (your account, Premium status, purchases, cloud backups, emails and server logs): Spaceship, Inc. (spaceship.com) hosts this website and our email (the emails we send you, such as login links and password resets, and the emails you send us); Easyhost (easyhost.be) hosts the account server the app uses and the app downloads.
- The app store you installed Zapo from (Google Play, the Amazon Appstore or the Samsung Galaxy Store), which handles the download, updates and any payment made through it, under its own privacy policy.
- Google: for Google Play purchases (purchase token, product, coded account number); Google Cast (the address of the stream); the Google TV home screen (title, picture and progress of what you’re watching); usage statistics from the app (section 11, unless you switch them off); and, if you allow it, Google Analytics on this website.
- Amazon: for purchases in the Amazon Appstore version (receipt ID, product, your Amazon user ID) and the Appstore’s licence check, under its own privacy notice.
- Stripe (Stripe Payments Europe, Ltd., Ireland): for payments on this website (email address, name, billing address, payment details, plan and amount).
- TMDB: for movie information (movie and series titles with the year, no identity; its image server sees your IP address).
- Your own IPTV provider, which your device contacts directly (your playlist login and IP address, as for any stream).
- Services you switch on yourself (section 8): the encrypted DNS service you pick (the names the app looks up and your IP address) and YouTube (the trailer you play and your IP address).
We don’t sell personal data and don’t share it with anyone else, unless the law requires it.
Some of these companies are outside the European Economic Area (for example in the United States). Where that is the case, the transfer is covered by the EU–US Data Privacy Framework or the European Commission’s standard contractual clauses.
How long we keep data
- Cloud backups: while you have Premium, then 90 days after it ends; deleted at once when you delete them or your account, or after a well-founded misuse report. Deleted backups can’t be recovered.
- Reports of misuse sent to abuse@zapoplayer.app: as long as needed to handle them.
- Your account and Premium status: until you delete your account. After that, the history of purchases and subscriptions is kept without your email address, as long as accounting law requires.
- Playlist details sent from your phone: at most 30 minutes.
- The record that a device used its free trial: permanently, without a link to you after your account is deleted.
- Payment records, sales with a partner code and partner payouts: as long as accounting law requires (in Belgium, 7 years).
- Your partner account and payout details: until you close it. After that, only what accounting law requires is kept.
- Records of failed logins: 1 day.
- Emails about your account or a deletion request: as long as needed to handle them.
- Data on your device: until you remove it or uninstall the app.
- Usage statistics from the app: at most 14 months at Google.
- Google Analytics data from this website (only with your consent): at most 14 months at Google; the cookies in your browser up to 2 years, or until you decline or clear them.
Your rights
You can ask us for access to your data, to correct it, to delete it, to restrict or object to its use, and for a copy in a common format. Email info@zapoplayer.app; we answer within one month. You can delete your account yourself on this website: we confirm your email address with a one-time link, then remove your email address and password from the account and release its devices. Your cloud backups are deleted at once. The purchase and subscription history stays, without your email address, for accounting and to prevent abuse.
You may also complain to the Belgian Data Protection Authority (Gegevensbeschermingsautoriteit / Autorité de protection des données), Drukpersstraat 35, 1000 Brussels, dataprotectionauthority.be.
Security
Connections to our servers use HTTPS. Playlist logins are encrypted on your device, and a cloud backup is encrypted before it leaves your device. Details sent from your phone are encrypted while they wait on our server. Our server only accepts requests from the app with a key and a personal sign-in token.
Children
Zapo isn’t aimed at children under 16, and we don’t knowingly create accounts for them. Parents can lock groups and channels with the parental PIN.
Changes
When we change this policy, we publish the new version on this page and update the date at the top. For important changes (for example new kinds of data, new purposes or new recipients), we tell you in the app before they apply, and by email if you have a Zapo account. Earlier versions are available on request.