The order, the thread, and very little else

1. The list that never reaches us

On a site about handing money to strangers, the gaps matter more than the inventory. So the gaps come first.

• Card numbers, and everything printed beside them. No page on pay-iptv.com carries a payment field, and there is no checkout here to carry one. Money moves inside whichever provider you picked — Apple Pay, Google Pay, a card network or PayPal — or, for a cryptocurrency payment, across a public chain that answers to nobody at this end. What returns to us is a yes. The digits that produced the yes never leave the place they were typed.
• Wallet credentials and bank account details. A seed phrase, a recovery key, a sort code, an account number: none of it is needed to issue a subscription, so none of it is ever asked for. If a message using our name asks you for any of those, the message is not from us.
• Logins. Registration does not exist here. There is no username table, no password hash and no session store — nothing an intruder would consider worth the effort of breaking in for.
• Documents, and anywhere to post them. Nothing physical ships and no identity is checked against paperwork, so neither a passport scan nor a street address has any job to do in this transaction.
• A record of your viewing. Playback runs between your device and the service. None of it reports back to this website, which means there is no habit file sitting here to leak, to sell or to hand over on demand.
• Anything an advertiser would pay for. No audience segment is assembled at this end and none is bought in. Brokers, ad networks and data exchanges get nothing from us, at any price.

2. The three routes information actually travels

Everything held here arrived one of three ways. There is no fourth.

The conversation you open. The app you pick decides the identifier: choose WhatsApp and it is a mobile number, choose Telegram and it is a handle. Beside it sits whatever you chose to type — usually a first name, which plan you are after, the country the set is in and what is plugged into the back of it. That thread stays intact on purpose. Write again in month nine and whoever replies should be reading history rather than guessing at it.

The order form on these pages. It captures two items, the plan you tapped and the phone number you enter, then passes the exchange to a messaging app. Two more values travel with it: the page you were reading when you clicked, and whichever site sent you to it. Neither feeds advertising. They exist so the desk does not re-explain a guide you have already finished.

An email to the desk. Writing in leaves us your address and the message itself. Both are filed for the practical reason chat threads are filed: a query raised eleven months into a subscription deserves an answer built on a record rather than a recollection.

3. Measurement, and the card at the foot of the window

Site measurement is aggregate and blunt. It reports that the payment methods guide outdraws the setup pages by roughly two to one, that a visit came from a phone rather than a desktop, that traffic skews to one region over another. Naming you is beyond it, and nobody has asked it to try.

First visit, and a compact card appears near the bottom of the window offering two choices: accept or reject. Reading the site is conditional on neither. Until one of them is chosen, nothing optional runs at all.

Essential storage runs regardless, since the site would behave strangely without it. It carries three things: your answer to the card, so the question is not put twice; the page you arrived on, so the desk knows what you have already read; and display preferences, the currency the prices render in among them.

Analytics storage waits for a yes. Before you give one, counting happens in a cookieless mode that registers the visit and retains nothing capable of identifying your browser. Say yes and ordinary analytics cookies are written. Say no and none are, which leaves the tally nameless.

Changing your mind takes two steps: wipe this site from your browser storage, then reload. The card returns and your fresh answer overwrites the old one. Where a browser transmits a global privacy control or a do-not-track signal, we read it as a refusal and leave it alone.

4. The grounds we rely on

Readers in the United Kingdom, Ireland and the European Union are owed an account of which lawful basis covers which activity, and the mapping here is short. Running an order and the support that follows it is contractual necessity — a subscription cannot be sold to you otherwise. The payment record that outlives it is retained because accounting law says to retain it. Screening for fraud and abuse falls under legitimate interests. Analytics has no basis beyond your consent, which is exactly why it does nothing until you give it.

5. Everyone else with a hand on it

Four processors, each with a job that can be stated in a single sentence.

• An analytics provider, which turns raw visits into aggregate counts and stays dormant unless you accepted the card.
• Whichever messaging platform you opened. The thread lives on their servers, governed by privacy terms of their writing rather than ours; if that troubles you, read them before you type.
• The payment providers. They run the transaction and they retain the payment data, so a chargeback, if one ever arises, is decided on their records instead of ours.
• The host and content-delivery network behind these pages. It sees the request logs any web server produces, which is how pages get delivered and abuse gets blocked.

That is the entire list. Nobody joins it for marketing purposes. A valid legal order would be answered to the extent it compels and not one line further.

6. How long each record survives

The order file — plan, date, confirmation that money cleared, and the support exchanges attached to it — outlives your twelve months by two further years. The reason is unglamorous: disputes and questions surface late, and a record beats a memory. Payment entries stay for as long as accounting rules oblige.

Chat history is a different animal. It belongs to the app you opened rather than to us, and survives there until one party clears it; your own copy is yours to delete at any moment. Aggregate analytics is discarded after fourteen months. Ask us to erase what we hold and it is gone inside thirty days, minus any payment entry the law requires us to keep.

7. Security, and the argument for holding less

Everything moves over HTTPS, including the order alerts that reach the desk when a form is completed, and only the small group who staff the support inbox can open it. None of that is remarkable and none of it is a guarantee, because no system is. The stronger protection is arithmetic: a breach can surrender only what was collected, and what was collected here holds no card number, no password and no identity document. Some providers work on data outside your own country, the United States included, and those transfers ride on the safeguards each provider publishes.

8. Rights in the UK, Ireland and the EU

The UK GDPR and the EU GDPR hand you a set of levers, and every one of them works here. Ask what we hold and you get told, in a copy you can keep. Point at something wrong and it gets corrected. Ask for erasure and it is erased. Processing can also be restricted, personal data can be taken elsewhere in a portable file, and anything resting on legitimate interests can be objected to. Consent to analytics may be pulled back whenever you like; measurement already taken before you pulled it stays lawful, but the measuring stops.

Nothing is charged for any of this, and thirty days is the outside limit on a reply. Should the reply disappoint you, the Information Commissioner covers the United Kingdom and the Data Protection Commission covers Ireland, with an equivalent supervisory authority in every EU member state. We would far rather be given the chance to put it right first.

9. Rights in California

The CCPA and CPRA entitle you to learn which categories of personal information have been gathered and for what purpose, to receive them, to have them corrected and to have them deleted. An opt-out from sale or sharing exists as well, though using it changes nothing here: no personal information is sold, and none is shared for cross-context behavioural advertising. Data buys you no discount, because no financial incentive is offered in the first place, and exercising a right changes how you are treated in no way whatsoever. Forty-five days is the response window.

10. Under-eighteens

Buying a television subscription is an adult transaction, and nothing on this site is pitched at children. Information is not knowingly taken from anyone below eighteen. If a child has messaged the desk, tell us and the thread goes.

11. Scope, and what happens when this changes

Pay IPTV issues this policy and runs pay-iptv.com along with the support desk reachable on WhatsApp, on Telegram and by email. Its reach stops there. Follow a link away from this site and a different operator policy applies to you, not this one.

A revision moves the date printed above. Anything material also earns a plain summary at the top of this page for a while afterwards, because a quiet edit to a privacy policy is precisely the sort of thing that ought to be announced instead.

12. Asking for a copy, a correction or a deletion

Email support@pay-iptv.com and put Privacy request in the subject line, or raise it on WhatsApp or Telegram. Mention the handle your original order came from, since that is how the right thread gets found. What you have read describes how we work rather than what the law says, so treat it as practice and not as legal advice. The refund policy and the terms of service sit beside it.