Privacy policy
Draft — not in force yet.
This document explains what data the SeeMoveTV IPTV app and our server process, why, for how long, and what your rights are. We write plainly; if anything is unclear, write to [to be completed].
Who is the controller
The controller of personal data is [to be completed], [to be completed], tax ID [to be completed], [to be completed]. Contact for all personal-data matters: [to be completed].
In short
- The app works without an account. Without an account our server receives no personal data from you — the app only checks whether its version is supported, and we count such requests in aggregate, without an identifier. More detailed statistics only with your consent.
- Your playlists, provider logins and passwords, favourites and watch history are kept on your devices (and — if you turn it on — in your Google Drive), not on our server.
- We do not sell data, show ads, or use advertising, analytics or tracking tools. The app does not send us crash reports.
- An account (optional) is an e-mail address, a password stored as a hash, and the list of your devices. You can delete it at any time — in the app or on the “Delete account” page.
Data inside the app
On the device, the app stores what you set up in it: sources (playlist and server addresses, logins, passwords, portal MAC addresses, Plex, Jellyfin and Emby account tokens), cameras and network shares with their logins, favourites, watch history, reminders, recordings, settings, and household members with a PIN (stored as a hash) and a child profile. This data sits in the app's storage, which Android protects from other apps; it is not encrypted with a separate password and is not included in Android backups or sent to our server.
You can also save a copy of your settings to a file yourself. That file is not encrypted; logins are included only if you tick that option.
Your sources and services you turn on
The app connects directly to the servers you add: your playlist provider (Xtream, M3U, Stalker), a Jellyfin, Emby or Plex server, a programme guide, cameras, network shares. It sends them the logins you gave for them (for Xtream also inside the stream address) and — once a source is added — refreshes playlists, the guide and the account status with the provider in the background. Jellyfin, Emby and Plex servers also receive the Android device identifier (ANDROID_ID) and the device model. Logos and posters are downloaded from addresses given by the source. All of them see your IP address and process data under their own terms, not on our behalf.
Outside services the app uses only once you turn them on, with your own credentials:
- TMDB (film descriptions and posters) — after you enter your own key; the title, year and language are sent.
- OpenSubtitles (subtitles) — with your key and account; the film's title or id, season, episode and languages are sent, and for live TV the title of the current programme.
- Plex account — signing in to plex.tv with your login and password.
- Google Drive — backups and sync (see below).
- Casting to Chromecast (phone) — the device receives the stream address (which may contain your provider login), the title and the logo.
- External player — if you choose one, it receives the stream address.
- Internet speed test — downloads test data from Cloudflare servers and, if they do not answer, Hetzner or OVH.
- Trailers — open the YouTube app or a browser with a search for the title.
Each of these services has its own privacy policy.
Backups and sync in your Google Drive
These work only after you connect a Google account with the button in the app. The app then gets access only to the hidden app-data folder in your Drive (it cannot see your files) and to your e-mail address, to show which account is connected. Data goes to your Drive, not to our server; we have no access to it. Disconnecting revokes the access.
A backup is made automatically once a day if something changed. Each backup has two parts: a version without logins (sources, household members, favourites, lists, history, settings), which the app does not encrypt, and a full version with logins, encrypted on the device with the household key (AES-GCM). Including logins is on by default and can be turned off.
Sync between devices (once turned on) and shared film descriptions (off by default) are fully encrypted with the household key. Only technical data stays unencrypted: space and device identifiers, a sequence number, the device name and the time.
The household key is created on your device, protected there by the Android keystore, and never sent to Drive. You can save it as a recovery code or hand it to a paired TV.
Home network: TV, phone and other devices
The TV and the phone pair with a QR code (the phone uses the camera only to scan it) and exchange data directly with each other on the home network, without our server: sources with logins, settings, household members, lists, favourites, history, remote-control commands and — on request — the TV's log. These messages are encrypted. To find each other, the devices send a signal on the local network that contains only cryptographic fingerprints.
Sending a file from the phone to the TV, and playing a phone video on the TV, go over the local network with a one-time key in the address; the file content itself is not additionally encrypted.
Features you turn on yourself: sharing recordings and device videos with other devices on the network (a DLNA server — without a password), receiving video from other devices (DLNA, AirPlay), casting to TVs and set-top boxes on the network, and searching for Plex servers, ONVIF cameras and cameras on the subnet. Devices then announce themselves on the local network (SSDP, mDNS).
So that the list of TVs is ready the moment you tap the cast icon, the phone app looks for them in advance — when playback starts and after the Wi-Fi network changes — also when you do not cast. It only asks devices on your home network (DLNA, AirPlay, Chromecast) and reads their name and kind; it sends them nothing until you pick a TV yourself, and the result never leaves the phone — it does not reach our server or anyone else.
On the TV, channel names and numbers (without addresses or logins) go into the system channel list and search, so that the system's voice search works.
Diagnostic log
The app keeps a log on the device (up to 7 days, a few MB at most): device model, network type, playback and guide events, channel names (this can be turned off), errors and the reasons the app closed. Passwords, tokens, MAC addresses and logins inside addresses are masked in it.
The log is never sent anywhere automatically — only when you copy, save or share it yourself. Before sending it to anyone, look through it: it contains channel names and a description of what the app was doing.
An account on our server
If you create an account, we process:
- your e-mail address and whether it is confirmed,
- your password — only as a hash (Argon2), we do not know the password itself; when you sign in with Google: your Google account identifier and the name Google provides (if any) — there is no password at all,
- your chosen language and an optional display name,
- the devices on the account: kind (phone, TV), name and model, app version, a random installation identifier, when added and when last used (the signed-in app checks in every 15 minutes while it is on screen and overwrites that time — no history is kept; the panel counts from it how many people with an account have the app open now),
- sign-ins (sessions): when created, refreshed and ended; tokens only as hashes,
- the country of the last sign-in (determined by Cloudflare from the IP address; we do not store the address itself) and the time of the last sign-in,
- a count of failed sign-ins and a temporary lock after several attempts in a row,
- one-time codes from e-mails and TV sign-in codes — only as hashes, valid for a short time.
Purpose and legal basis: running the account and providing the service you ask for (Art. 6(1)(b) GDPR), and the security of the account and the service (Art. 6(1)(f) GDPR — our legitimate interest in protecting accounts from takeover and abuse).
E-mails
We send only the messages the account needs: address confirmation, a link to set a new password, a link to sign in a TV or delete the account (when you ask for it) and a confirmation that the account was deleted. We send no newsletters or ads.
Before a trial or Premium ends (and when Google reports a payment problem) we send a reminder by e-mail and show it in the app. Every such e-mail has an unsubscribe link; after unsubscribing, reminders appear only in the app. We record which reminder we sent and when, so as not to send it twice.
E-mails are sent on our behalf by: [to be completed]. After sending, the message content (address and link) is removed from our job queue.
Server, logs and security
The server is hosted by: [to be completed]. Traffic to the server passes through Cloudflare (protection against attacks and encrypted connections); in doing so Cloudflare processes the IP address and technical connection data as our processor.
Server logs are kept without IP addresses and without address parameters (which could contain one-time codes): time, kind of request, result, response time. The logs contain no e-mail addresses, passwords or tokens — only account identifiers where needed to explain an error. The IP address is used on the fly to limit the number of requests and, apart from sign-in attempts, is not stored.
Sign-in attempts — in the app, on this site and in the administrator panel, successful and failed — are recorded with the IP address, country (from Cloudflare), browser or app name and version, time, result and the account they concerned (an e-mail address with no account only in shortened form, e.g. “jo***@gmail.com”). This is used to detect and block break-in attempts (password guessing) and to look into sign-ins you do not recognise: after a series of failed attempts, password sign-in to that account is paused for a few minutes, and sign-ins from that IP address for some time; if your account is locked this way, we e-mail you about it (at most once a day). Attempt records are deleted after 90 days, also if the account was deleted earlier. Basis: security of the service and of accounts (Art. 6(1)(f) GDPR).
Connections to the server are encrypted (HTTPS).
Purchases
Payments for Premium are handled by Google Play. We receive no card or payment details — Google sends us a purchase confirmation (order id, product, period, subscription status) so that we can turn Premium on for your account. This applies once purchases are launched.
When you sign in, buy or refresh Premium, the app may ask Google to confirm that it comes from Google Play and has not been modified (Play Integrity). We store the result of that check, the app version and the country — to detect modified copies of the app (Art. 6(1)(f) GDPR). The result does not block use of the app.
Version check and counting active installs
At start and once a day the app asks the server for its configuration (among other things, whether its version is still supported) — also without an account. The request carries no account data and no identifier. We only add it to aggregate daily counts: device type (phone, TV), app and Android version, country (from Cloudflare, without the IP address), whether the app has an account, the plan (free, trial, Premium) and whether it is this install's first check-in that day, week, month or ever; also how many times the app was opened on each day and — if the app was installed from an advertising campaign link — the source and campaign name from that link (the app reads it once from Google Play; we also keep it with your account if you create one, to know which campaign brought accounts and purchases). A visit to this site from a campaign link adds one to that campaign's daily count — no cookies, IP address or identifier. When you sign in on this site (“My account”), your browser gets the strictly necessary session cookie `konto` (a random code, nothing else); the session ends when you sign out, after 14 days, or after 3 days without use. For the session we keep only when it started and when it was last used (the sign-in itself is recorded like every sign-in attempt — see “Server, logs and security”). The counts cannot tell who you are. Purpose and basis: operating the app and its versions (Art. 6(1)(f) GDPR).
If you agree to statistics in the app, the request also carries a random install identifier (not linked to your account). We store it only as a hash keyed with a server secret, together with the days on which the app checked in — to know how many installs come back after a few days. Basis: your consent (Art. 6(1)(a) GDPR); you can withdraw it in the app settings.
Sync through the server, crash reports, support requests and notifications
Sync through our server (optional, with an account) keeps the same small files as sync through Google Drive — encrypted on the device with the household key, which the server does not know. We see only the “envelope”: the file name, its size, a technical description (random identifiers of the space and the device, a sequence number, a key identifier), the time, and the result and duration of each sync — not your lists, favourites or history. We delete the files with the account or at your request. Purpose: the sync you ask for (Art. 6(1)(b) GDPR). Counts of syncs by the other ways (direct and through Google Drive) reach us only with your consent, without an identifier.
The app sends crash reports only with your consent (the same consent as for statistics): when it closes with an error, stops responding or the code itself reports an error — on the next start. A report contains the app version, the kind of device, its maker and model, the Android version, the country (from Cloudflare), the screen it happened on, the stack trace and the last lines of the app's log — without passwords, tokens, addresses with login details and MAC addresses (the app removes them and the server again) — and a hash of the installation identifier. If you are signed in, the report is linked to your account; only administrators see that link. Purpose: finding and fixing errors. Basis: your consent (Art. 6(1)(a) GDPR); you can withdraw it in the app's settings.
You send a support request from your account. We keep the subject, the messages, the replies, your rating of the help (if you give one), the app version, the kind and model of the device, the Android version, language, country and plan — and the app's log if you tick “Attach the log” (cleaned as above). Purpose: answering the request (Art. 6(1)(b) GDPR). You learn about a reply in the app, by e-mail (without the reply's text) and by a notification, where they work.
Push notifications go through Firebase Cloud Messaging (Google). While you are signed in, the app gives us this device's notification token; we delete it when you sign out, when the device is removed or when Google reports it invalid. A notification contains only a title and a short text (e.g. a reminder that Premium ends, a support reply) — no passwords or addresses. The app shows it according to its notification settings and quiet hours.
How long we keep data
- The account and devices — until the account is deleted. Deleting the account removes them at once.
- Sign-ins — expire after 60 days without use; records of ended sign-ins are removed with the account.
- One-time links — from one hour to 48 hours; TV codes — 10 minutes.
- Database backups — encrypted, on the server and with the backup storage provider (our processor); a deleted account disappears from them after 30 days. If new backups stopped being made, the last few stay longer — until the next ones.
- Server logs — up to 30 days.
- Install identifier hash (with consent) and Play Integrity check results — 90 days (set in the panel, from 30 to 400 days). Aggregate daily counts contain no personal data and are kept longer.
- Record of sent reminders — until the account is deleted.
- Single crash reports — 90 days (set in the panel, 14 to 400 days); aggregate crash counts without personal data stay longer.
- Support requests — text and log until a year after the request is closed (set in the panel) or until the account is deleted; only numbers for statistics stay.
- Notification token — until you sign out, the device is removed or the account is deleted.
- Server sync files — until the account is deleted, cleared at your request or replaced by later syncs.
Transfers outside the European Economic Area
Cloudflare, Google and the e-mail service may also process data outside the EEA. This happens on the basis of a European Commission adequacy decision (EU-US Data Privacy Framework) or standard contractual clauses. You can get a copy of the safeguards by writing to us.
Your rights
You have the right to access your data and receive a copy, to rectification, erasure, restriction of processing, data portability, and to object to processing based on legitimate interest.
You can download your account data in the app (a file with the account data) and delete the account in the app or on the “Delete account” page. For anything else, write to [to be completed]. We answer within one month.
You have the right to lodge a complaint with a supervisory authority — in Poland the President of the Personal Data Protection Office (ul. Stawki 2, 00-193 Warszawa) — or with the authority in the country where you live or work.
Children
An account can be created by a person aged 16 or over; a younger person needs the consent of a parent or guardian. The child profile in the app works on the device and needs no account for the child.
App permissions on Android
- Internet, network and Wi-Fi state — playback and connecting to sources.
- Wi-Fi multicast — finding the TV, phone, servers and cameras on the home network; on only while needed.
- Microphone — only when you press voice search. The sound goes to the system speech-recognition service (usually Google), the app receives text and does not store the recording.
- Camera (phone) — only to scan the QR code when pairing with the TV.
- Video files — browsing and playing videos from the device when you open them.
- Notifications, exact alarms, start after the device boots — programme reminders, scheduled recordings, download notices and refresh problems.
- Foreground services — background playback, recording, downloading for offline viewing, the connection with the phone and home-network features.
- TV: display over other apps (opening the app when the phone sends something — you grant it yourself in settings) and access to the system channel list.
Changes to this policy
We will announce important changes in the app, and to account holders also by e-mail, before they take effect. The date in force is at the top of this document.