A handle, a plan, a start date

1. What never gets as far as us

Start with the absences. On this subject they carry more information than any inventory, so they go first.

• Card numbers, and their neighbours. No page here holds a payment field, and there is no checkout to hold one. Money leaves through whichever service you chose — a card network, Apple Pay, Google Pay, PayPal — or across a public blockchain that nothing at this end governs. A confirmation comes back to us. The digits behind it stay exactly where you typed them.
• Recovery phrases and bank particulars. Seed words, private keys, an IBAN, a sort code, an account number: a subscription can be issued without a single one of them, so not one is requested. Any message wearing our name that asks for one was not written here.
• Sign-ins. Nobody registers on this site. That means no table of usernames, no stored hashes and no sessions to hijack — nothing an intruder would find worth the trouble of arriving for.
• Paperwork, and anywhere to send it. No parcel is dispatched and no identity is checked against documents, so a passport photograph and a street address would both be answers to questions nobody here has asked.
• Viewing habits. What plays on your television is a conversation between your device and the service. It never reports home to this website. There is no history file here to be leaked, sold or produced under pressure.
• Anything an ad market would bid on. No audience list is assembled and none is bought in. Brokers, exchanges and ad networks leave empty-handed, whatever the offer.

2. The three doors, and there is no fourth

Everything held here came through one of these. Nothing arrives another way.

The chat you open. Choose WhatsApp and the identifier is a phone number; choose Telegram and it is a username. Around it sits whatever you volunteered — a first name most of the time, the plan under discussion, which country the television is in, what is plugged into the back of it. Threads are kept whole on purpose. Somebody replying in month ten should be reading what was agreed rather than reconstructing it.

The order panel on these pages. Tapping a plan opens a short form. It takes the plan and a number, then hands the exchange across to a messaging app. Two extra values ride along: the page you came from, and whichever site pointed you at it. Neither goes near advertising. They exist to spare you a second explanation of a guide you have already read.

A letter to the inbox. Email leaves an address and the words you wrote. Both are kept for the same practical reason threads are — a question arriving in the eleventh month of a term deserves a reply built on the record rather than on somebody recollecting it.

3. Counting, and the panel at the foot of the screen

Measurement here is coarse and nameless. It can tell that the page about ending a term draws roughly twice the traffic of the device instructions, that a reader arrived on a phone, that one region runs heavier than another. Putting a name to any of it is beyond the tooling, and nothing has been configured to try.

On a first visit a small panel appears low on the screen with two buttons: allow or decline. Reading the site depends on neither. Until one is pressed, every optional script sits idle.

Essential storage runs either way, since the site behaves oddly without it, and it does three jobs: remembering which button you pressed so the question is not asked twice, remembering the page you landed on, and remembering display choices such as the currency the figures render in.

Analytics storage waits for permission. Before it is granted, counting runs in a cookieless mode that logs the visit and keeps nothing capable of singling out a browser. Grant it and standard analytics cookies are written. Refuse and none are, leaving the tally anonymous.

Reversing the decision takes two moves: clear this site out of browser storage, then reload. The panel returns and the newer answer replaces the older one. A browser sending a global privacy signal or a do-not-track header is read as a refusal without being asked again.

4. Which lawful basis covers what

Readers in the European Union, Ireland and the United Kingdom are entitled to see that mapping, and it is short. Arranging a subscription and supporting it through the year is contractual necessity, since the thing cannot be supplied otherwise. The payment entry that outlasts the term is retained because accounting law insists on it. Fraud and abuse screening rests on legitimate interests. Analytics rests on consent alone, which is exactly why it achieves nothing until consent exists.

5. Who else touches any of it

Four outside parties, one sentence each.

• An analytics provider, turning raw visits into totals, dormant unless the panel was allowed.
• The messaging platform you chose. The thread sits on their infrastructure under privacy terms they wrote rather than ones we wrote; read those before typing if it matters to you.
• The payment services. They process the transaction and hold the payment data, so any dispute is judged on their records rather than on anything kept here.
• The host and delivery network serving these pages, which sees the ordinary request logs every web server produces, and is how pages arrive and abuse gets turned away.

That is the whole list, and nobody is added to it for marketing purposes. A binding legal order receives exactly what it compels and nothing beyond it.

6. What survives, and for how long

The subscription entry — plan, start date, proof the payment cleared, and the support exchanges hanging off it — is kept for two years past the end of the term. The reason is dull: awkward questions surface late, and paperwork beats recollection. Payment entries last as long as accounting rules oblige.

Chat history obeys different rules. It lives with the app you opened rather than with us, and stays there until one side deletes it; your copy is yours to remove whenever you feel like it. Aggregate counting is thrown away after fourteen months. Ask for erasure and what we hold disappears within thirty days, apart from any payment entry the law requires us to retain.

7. Security, and why holding less beats holding carefully

Traffic runs over HTTPS, including the alert reaching the desk when the order panel is completed, and the inbox opens only for the handful of people who staff it. None of that is unusual and none of it is a promise, because no system can honestly make one. The real defence is subtraction: a breach can only expose what exists, and what exists here holds neither a card number, nor a password, nor a document proving who anybody is. Some providers process data outside your own country, the United States among them, under whichever safeguards each of them publishes.

8. Rights across the EU, Ireland and the UK

The EU and UK versions of the GDPR hand readers a set of controls, and all of them function here. Ask what is held and you are told, in a copy you keep. Flag something inaccurate and it is corrected. Ask for deletion and it happens. Processing can be restricted, personal data can be exported in a portable format, and an objection can be raised to anything resting on legitimate interests. Permission for analytics can be taken back at any point; what was measured beforehand remains lawful, and the measuring stops.

None of this costs anything, and thirty days is the longest any of it should take. Where the answer disappoints, every member state has a supervisory authority — Ireland has the Data Protection Commission, the Netherlands the Autoriteit Persoonsgegevens — and the United Kingdom has the Information Commissioner. The preference here, obviously, is to be handed a chance to fix it first.

9. Rights in California

Under the CCPA and CPRA you may ask which categories of personal information have been collected and for what purpose, receive a copy, have errors corrected, and have the lot deleted. An opt-out from sale and sharing exists as well, although exercising it alters nothing here: nothing here is sold, and nothing is shared for cross-context behavioural advertising. No discount attaches to data, because no incentive scheme exists, and using a right changes the way you are treated not at all. Replies go out inside forty-five days.

10. Readers under eighteen

Committing a household to a year of television is an adult decision, and none of this site is aimed at children. No information is knowingly gathered from anybody under eighteen. Where a child has written to the desk, tell us and the thread is deleted.

11. What this policy covers, and what happens when it moves

This policy is issued by IPTV Subscribe and applies to iptvsubscribe.eu together with the desk reachable by WhatsApp, Telegram and email. It ends there. Click through to somewhere else and that operator governs you instead of this page.

Any revision changes the date printed above. Where a change is material, a plain summary sits at the top of the page for a while as well, on the principle that a privacy policy edited in silence is exactly the sort of thing that deserves announcing.

12. Copies, corrections and deletions

Write to support@iptvsubscribe.eu with Privacy request as the subject, or raise it on WhatsApp or Telegram. Include the handle the subscription was agreed under, since that is what locates the right thread. What you have just read sets out practice, not law, so treat it accordingly. Sitting next to it: the refund policy and the terms of service.