Privacy notice

An email address, because that is where the login goes and how you sign in afterwards. A name or a label, so that whoever answers your message knows which account is writing. A country, which decides how the order is taxed and which channel groups make sense to point you at first. The device you intend to use, so the right setup instructions go out with the credentials. And the plan itself.

MAG and Formuler boxes need one extra thing, the MAC address printed on the underside, because a portal line authenticates against the box rather than a password. A phone number is optional and used only if you asked for the reply on WhatsApp. Nothing else on the form is compulsory and nothing else is stored.

The line itself: server address, username, password, expiry date and the number of connections it carries. Alongside it, a row for the order, a row for each renewal, and whatever is written in support tickets by you or by us. That is the operational record, and it is not hidden from you anywhere. Sign in at your account and you are looking at the same rows we are.

The card form is not ours. It runs on the payment provider’s own page, inside their 3-D Secure flow, and what comes back to this server is a yes or a no, a transaction reference and at most the last few digits so support can match a payment to an order. A full card number has never touched this database and there is no configuration in which it could. If someone ever asks you for card details over WhatsApp claiming to be us, it is not us.

There is no advertising pixel on any page. No Meta tag, no TikTok tag, no Google Ads remarketing, no analytics product that follows you off this domain and reports back. We do not buy lists and we do not sell one; there is nobody to sell it to who would not immediately make our support inbox worse.

We also do not keep a viewing history for marketing. The provisioning panel can see whether a line is currently connected, which is the only reason support can tell you that a stream is dead rather than your wifi, but that is a live status and not a diary of your evenings. Nobody here has a report of what you watched last week, because nobody built one.

The web server writes an ordinary access log: IP address, timestamp, the path requested, the response code and the browser string. It exists so that a bad deploy can be traced and a flood of junk traffic can be blocked, and it is what any web server on earth writes. It rotates on a short cycle measured in weeks, it is never joined to your order record for marketing purposes, and nothing is built on top of it.

A single cookie is set, and only after you sign in. It holds a random session token and nothing that describes you. It is marked HttpOnly so page scripts cannot read it and Secure so it never travels over plain HTTP, and it disappears when you sign out. Because there is no advertising or analytics cookie anywhere on the site, there is no consent banner: you cannot meaningfully consent to something that is not happening, and a popup asking you to would be theatre.

Three places, each getting the minimum it needs to do its job. The payment provider, so the money can move. The provisioning system, so a line can be created against your order. The mail server, so the credentials can reach your inbox. That is the whole list. No advertiser, no data broker, no affiliate network, and no other site in the operator’s portfolio gets a copy of this database for its own marketing.

Support runs largely over WhatsApp, and a conversation there sits on Meta’s infrastructure under Meta’s policies as well as under ours. That is a fine place to send “channel 402 has frozen again” and a poor place to send card details, passwords or a photograph of an identity document. If something is sensitive, email it instead. We will never ask for a password there, because we cannot read yours anyway.

The account and its orders stay while the account exists, and the payment records stay for the period accounting rules require after that, which is the one part of this we are not free to shorten. Support tickets are kept for roughly two years, because the same question about the same television tends to come back and the history saves you retyping it. Server logs go in weeks. Line credentials are removed with the line.

Ask for deletion and we will do it, apart from the financial records we are obliged to hold, and we will tell you specifically which ones those are instead of hiding behind the phrase.

Email from the address on the account and say which of the three you want. A person does it by hand, so expect a reply in a few working days rather than an instant automated export. We may ask you something only the account holder would know before acting, which is not obstruction: handing a subscription over to whoever writes in first would be the actual privacy failure. Corrections to a name or an email address can also be made yourself from the account page.

The whole site runs over HTTPS with no plain HTTP fallback. Account passwords are stored as one-way hashes, so a stolen copy of the database does not hand anybody your password. Access to the operator panel is limited to the people who answer tickets, and it sits behind its own login rather than being reachable from the public site. What no operator can honestly promise is that nothing will ever go wrong. What we will promise is that if something did, you would hear about it from us, quickly, and not from a forum thread.

The date at the top moves whenever the text does. If we ever start collecting something that is not described above, the section describing it will appear here before the collecting starts, not afterwards. This notice sits alongside the terms of service and the refund policy, and the three are meant to be read as one set.