The eye is closed.
You already pay for IPTV. Twiga is a web player for live IPTV that makes watching it nobody’s business — account first, then your M3U playlist or Xtream Codes login, sealed with a key only you hold — and you’re watching in your browser, no app to install.
Free to start · pay in Monero, no card
Sign-up takes an email and an invite. No invite yet? Write us for one — [email protected].
§ 01 · The ledger
Who sees what when you watch IPTV.
Privacy copy is cheap, so here’s the claim as a ledger instead: what each party can actually see when you watch through Twiga. Watched directly, your home IP goes to your provider and your stream traffic to your ISP — here’s what changes.
| What’s visible | Watched directly | With Twiga |
|---|---|---|
| Your ISP sees | The IPTV service you connect to. Your ISP sees its servers, plus the timing and volume. | An encrypted connection to twiga.tv. Your ISP sees the timing and volume — not the provider, not the stream. |
| Your provider sees | Your home IP address. Every request reaches the provider from the address your ISP gave you. | Twiga’s exit IP, not your home IP. Streams leave from our VPN exits; the TV guide is fetched over Tor. |
| Your provider login | Held by your player app. Your provider credentials sit on the device and go out with every request. | Sealed in your browser with a key only you hold. We store ciphertext we can’t open; the key never reaches us. |
| The stream | Decoded on your device. Your device fetches the stream straight from the provider. | Decoded in your browser. Our relay runs no transcoding and no codec detection: 0 bytes decoded server-side. |
| A record of what you watch | Tied to your account and IP. The provider can log which channels you request, against your subscription. | — not collected — USER IPs LOGGED · NONE — verify on /uptime |
The receipts: live status · the manifesto · the privacy page
§ 02 · The refusals
Three things Twiga refuses to see.
One refusal per layer — what we store, what your provider sees, what the guide gives away. Each links to the wiki entry where we defend it.
§ 03 · The wire
The wire, end to end.
Three steps between you and the channel. The relay path runs no transcoding and no codec detection — it forwards bytes it never decodes. The manifesto walks the same path in full.
YOU — a browser tab, signed in │ ① you ask for a channel ▼ TWIGA RELAY — forwards bytes, │ never decodes them │ ② upstream opens from a VPN exit ▼ YOUR PROVIDER — sees the exit IP, │ never your home IP │ ③ the stream comes back │ through the relay ▼ YOU — your browser decodes it and plays ◆ never decoded ◆ no content logged
Bytes in. Bytes out. Opaque.
§ 04 · The receipts
Verify it, don’t trust it.
Three claims this page makes, each with the place you can check it yourself. If a number here ever disagrees with the live one, the live one wins. The rest of the receipts are in the journal.
Shown as user_ip_logged: false in the read-only status readout — curl‑verifiable.
No transcoding and no codec detection on the relay path — it forwards opaque bytes, by construction.
How the relay works →Your provider login is stored as ciphertext we can’t open, keyed by a secret only you hold. In transit it’s ordinary HTTPS, like any site.
The privacy page →$ curl -s https://twiga.tv/v1/public/network-status | jq . — the same values, no browser required.
§ 05 · The questions
The questions we’d ask too.
What people ask before they trust a web IPTV player with a login, answered without hedging. Each one has a full page in the wiki.
§ 06 · Start
Open a tab and it’s on.
The player runs in the browser you already have, on the subscription you already pay for — no download, no install.
Web player — live now · Android TV & Google TV — beta
Free to start · then €4/mo in Monero · no card, no ID