Privacy
Last changed 11/7/2026.
Privacy
TDR WEB DEV SRL ("we") runs SmartX Player. This page says what we hold about you, why, how long, and who else sees it.
- Who is responsible: TDR WEB DEV SRL. The full company details — the registered office, the register number and who represents it — are on the company details page.
- How to reach us about your data: [email protected]. Say that your letter is about your data and it will be treated as this page describes.
- Last updated: 10 October 2026
What we hold, and why
If you buy from us
When you place an order we keep your e-mail address, your name, the country you gave for tax, the amount, and a reference for the sale. We need the address to send you your activation code and the rest to issue a correct invoice.
Two more things are on the order where you gave them. If you typed the address and key off your own home screen — which is the form offering to put the licence straight onto that installation instead of making you carry a code — the pair is kept on the order, because that is how the licence finds its way there when the money arrives. And if you used a discount code, the order records which one, because the figure on the invoice has to be explainable.
There is no account to create on the website, and nothing to sign in to with a password. Your own area is entered with the address and the key printed on the player's home screen, and nothing else. Where an operator has made a customer record for you by hand, a password is stored against it as a scrypt hash — unreadable to us and to anybody who obtains a copy of the database — and today nothing signs in with it.
If you use the player
Each installation registers itself and gets an address and a key, both generated by us. They identify an installation; they are not about you.
Alongside them we keep the platform and model the device reports, the version of the app, when it was last seen, the country the installation first registered from — worked out from that address and kept as two letters, never the address itself — and two IP addresses: the one the installation registered from and the one it last connected from. Those two are the only things here that say anything about where you are. They are two, and not a history: an installation that has moved four times has the first and the fourth, and nothing in between.
They can also be set to be forgotten once an installation has stopped checking in — the row stays, with its licence and its lists, and the two addresses go. Whether that happens, and after how long, is the setting in the table below; an installation that comes back writes its address again on its first connection.
The history, and it is worth reading. Some things are written into a record that is kept for two years. Most of them are a member of staff doing something to your installation — ending a licence, moving credit, blocking a device — and what is written is what was done, by whom, and the address the request came from. That is there so a change to somebody's account can be traced to the person who made it, which is as much your protection as ours.
Some of them are not staff, and your own address is in those. Every moment where somebody claims to be an installation, or where an installation acts on itself, is written down with the address the request came from: registering, being turned away while registering, signing in to the customer area, activating a code, releasing a set of lists, removing a list, and a licence carried over to a reinstalled device.
This page used to say there were two of them. There are nine, and being able to see later where such a claim came from is the whole point of recording it — a list removed or a licence moved is somebody's property changing hands, and support has no other way to answer "who did this".
Every platform also sends a machine digest: a one-way hash of something the device already knows about itself. It exists so that reinstalling, or clearing the application's data, does not cost you the licence you paid for.
On Windows it is made from a serial the machine reports. On the televisions it is made from the set's network address where the set offers one, and from the maker's own identifier where it does not. The address is used because a factory reset changes the maker's identifier on a Samsung and does not change the address, and a reset is the first thing anybody tries when a television misbehaves: without this, resetting the set costs you the licence you paid for. On an LG it is LG's own identifier, which LG keeps the same across a reset, and on a Hisense it is Hisense's.
On Android it is made from the identifier Android gives this application for this device — already particular to the pair of them, and hashed again with a fixed salt before it is sent; it survives an uninstall and is reset by a factory reset, which is the line most people would draw themselves.
Some devices send two, and which is which differs by platform.
On an Android box the first is the identifier Android gives this application and the second is the device's network address. On a television it is the other way round: the first is the network address and the second is the maker's own identifier.
The reason is the same either way — whichever one a factory reset destroys, there has to be another that it does not. A reset wipes the identifier Android gives an application and changes Samsung's own, and a reset is the first thing anybody tries when a device misbehaves; without a second digest, resetting one costs you the licence you paid for.
A network address is never treated as proof of anything, on either platform, because it can be read by anything on the same network. Where it is all a device can offer, that device waits rather than being believed.
Windows sends one, because a board serial is not changed by reinstalling Windows, which is the same event there.
In every case it cannot be turned back into what it was made from, and the thing it was made from never leaves the device.
If the player fails at something
On a television, on Android and, since 2026-10-09, on Windows. This section applies to all three.
When the app fails at something you can see — a channel it cannot decode, a picture that will not come back, a stream that stops, a picture it gives up on after trying every server, a crash — it sends us a short fault report. It carries five things:
- what kind of fault it was: picture, player, stream or crash;
- one line describing it, which is usually the message your own device produced;
- the player's own log of that session — when it opened something, when it began buffering, when the picture started, what it refused and with which code, and how long each of those took;
- the make, model and firmware your device reports about itself. On Windows there is no make or firmware to report — a PC is not a model of anything — so what it sends in that field is the version of Windows itself, such as
Windows 10.0.26100; - the version of the app.
It is signed by your installation, so it is attached to that installation — the same address and key as everything else here — and not to you.
What it does not carry, and this is deliberate rather than incidental. No address and no credentials. Any address in a report is reduced, before it is sent, to its scheme and the kind of file it names — <http ts> — and that reduction is applied to every line of every report rather than at the places somebody remembered. It carries no channel names, nothing about what you watched or where you got to, and no list of yours.
Why we keep it at all. The same build plays on one television and refuses on the next, and no manufacturer publishes a table of which model refuses which call. The table has to be ours, and it is built out of these reports. Without it the only way anybody hears about a set that will not show a picture is somebody writing to say "it does not work".
A device sends at most twenty an hour, and the same fault twice within ten minutes is sent once.
If you add a channel list
A list you add carries your provider's username and password — the subscription you bought from somebody else. For an Xtream list the password is encrypted before it is stored. For a plain M3U link the credentials are part of the address itself and are stored as you gave them.
We never sell, share or analyse what you watch. What you played and where you got to stays on your own device — the resume positions, the history, the favourites. None of it reaches us, and there is no route here that would carry it.
One thing does travel, and it is worth being exact rather than reassuring. To show a poster and a description beside a film, the app sends us the titles on the shelf you are looking at — not what you opened, not what you played, and never more than forty at a time. It arrives signed by your installation, so in principle it says "this installation's list has these films in it and somebody scrolled past them". We keep the answers, not the asking: what is stored is the film's own details, shared by everybody who ever asks about that title, because the answer to "what is Sintel about" does not depend on who wants to know. The Movie Database is sent the title and a language and nothing about you at all.
If you write to us
The contact form keeps your name, e-mail, what you said it was about and the subject you gave it, your message, the address of your installation if you filled that box in, and the IP address it was sent from. Everything but the last is how we answer you, and the installation address is on the form because it is the fastest way to find the thing you are writing about. The IP address is kept with the message so that abuse can be traced to where it came from — the limit that stops the form being flooded is counted in memory and does not use it.
How long we keep it
| Your orders | kept, as the law requires for accounts |
| Your account and lists | until you close it or ask us to erase you |
| History of what staff did (a licence ended, credit moved) | 24 months |
| Record of letters sent to you — address and subject, never the message | 12 months |
| Film details we looked up | 90 days |
| An installation that has ended and stopped checking in | 3 months |
| A registration that never checked in at all | 14 days |
| The two IP addresses of an installation that has stopped checking in | kept while the installation is |
| Fault reports from the player | 30 days |
These are settings, and an operator can change them. The figures above are what they are set to today — read off the running service rather than off the defaults in the code, because a setting somebody changed is the one that governs.
The addresses have no figure, and that is a decision rather than an oversight. Nothing forgets them on its own, so they live exactly as long as the installation row does and go with it when that goes. Whether support should still be able to answer "where did this install from" a year later is a business question; until it is answered, this page says what actually happens.
Who else sees it
- Our hosting provider, which runs the machine the service is on, and the second machine at the same provider that the nightly backup is copied to.
- Cloudflare, which sits in front of the website and sees the IP addresses of people visiting it.
- The service that sends our mail, which sees the whole letter — the address, the subject and the body. That is what sending a letter through somebody means, and the body of a receipt carries your name, your order reference and what you paid. We keep only the address and the subject in our own record, which is the line in the table above; the provider handles the rest on the way through.
- The Movie Database, when the app looks up a poster or a description. It is sent the title, the year where the title carries one, and a language. It is not sent anything about you, your device or your subscription.
- The reseller who sells you your subscription, if you bought through one. Their page in our dashboard lists the installations that are theirs, and against each one it shows your e-mail address and your name where we have them, so that they can tell one customer from another when you write to them. They do not see where an installation connected from, and they see only their own. If you bought from us directly, no reseller sees anything of yours.
- YouTube, if you press play on a film's trailer — and on a television, us as well, for a moment.
Every player shows the trailer inside itself rather than handing it to another application, and what each one puts on the screen is YouTube's own player loaded from youtube-nocookie.com. YouTube therefore sees the address you are connecting from and what your device says it is, because their player runs on your device. From that moment it is YouTube you are dealing with, under their terms. Nothing about your licence, your subscription or your lists goes with it, and nothing of ours is in it.
On a television there is one extra step, and it is ours. A television application's pages come off the set's own storage, which gives a browser no origin to send, and YouTube's player refuses to start without one — so the set opens a small page of ours at /trailer/ instead, and that page holds YouTube's player. Our own server sees that request: the address you are connecting from, what your device says it is, and which trailer was opened. It is the one thing in this notice that says anything about a film you were interested in, which is why it is written out rather than summed up, and our front-of-house provider sees the same request on the way through. Windows and Android build that page inside the application and ask us for nothing at all.
- Your own IPTV provider, because the app talks to them directly for your channels. That is a relationship between you and them, and on Windows, Android and most televisions we are not in the middle of it at all: the player asks your provider itself and we never see the answer.
On some televisions there is an exception, and it is the one place where we do stand in the middle. A television's browser is not allowed to fetch from every address — the set refuses it before any answer comes — and where that happens the application asks our service to fetch the list or the guide instead and pass it back. The address it asks for is the one your provider gave you, and that address carries your provider username and password in it, so our machine sees them in passing. It is used to make the request and is not written down. Your video never goes this way: the service reads lists and guides and refuses anything else, and the channel itself is always fetched by the television straight from your provider.
We do not use advertising, tracking pixels, or analytics that follow people between sites.
What you can ask for
- A copy of everything we hold about you. Write to us and we will send it.
- To be erased. We will delete your account, your lists and your messages, and clear the IP address from your installations. Your installations themselves keep working — they belong to whoever is holding the remote. Your orders stay, with your name and address removed from them, because we are required to keep the figures for accounting.
- To correct something that is wrong.
- To complain to your national data protection authority if you think we have got this wrong.
We answer these within one month.
Children
The player is not meant for children to buy or set up. It has a parental PIN so that whoever does set it up can lock categories, and that PIN never leaves the device.
Changes
If this page changes in a way that matters, we will say so here and change the date at the top.