Tuneline's Content Policy: Zero Hosting, Zero Curation

This is Tuneline's content policy, stated directly rather than buried in legal boilerplate.

We host nothing

Tuneline does not store, mirror, cache, or transcode any stream on its own infrastructure. When you play something in Tuneline, your device connects directly to the source you added — a server Tuneline doesn't operate and has no access to. There is no Tuneline-run archive of channels, movies, or episodes anywhere. (The mechanics, in detail.)

We curate nothing

Tuneline does not maintain a list of sources, does not recommend providers, and does not rank or promote any source over another. The app has no "discover" tab pointing at third-party content and no built-in suggestions for where to find a playlist. Every source in every Tuneline install got there because the person using the app typed or pasted it in themselves.

We don't know what's in your source until you tell us

Tuneline has no visibility into the contents of a source before you add it. The app parses whatever playlist or EPG data the source provides and displays it — a group-title becomes a category, a channel name becomes a label — but that's rendering, not review. Nobody at Tuneline looks at a source before it's added, because there's no step in the product where that would happen.

Who's responsible for what

This follows directly from the architecture:

• The person who added a source chose it, has a relationship with whoever operates it, and is responsible for that choice.
• The operator of a source is responsible for what's actually served from that URL.
• Tuneline is responsible for the player: parsing correctly, playing reliably, and not doing anything with your data beyond what's needed to sync your own settings across your own devices.

If something at a source shouldn't be there, the right party to contact is whoever operates that source — Tuneline has no ability to remove content that was never on a Tuneline server to begin with. Reports about how the app itself behaves are always welcome at support@tuneline.app.

Why the policy is this simple

A zero-hosting, zero-curation design isn't a workaround — it's what falls out of building a player instead of a service. A service that assembles and sells a catalog has to make editorial and licensing decisions about what's in it. A player that only ever renders a URL the user supplied has nothing to curate, because it never assembled anything in the first place.

Related reading

• What Tuneline Actually Is (And Isn't)
• How Tuneline Works
• Private, No Tracking, No Ads — the same zero-catalog design applied to privacy

---

— Shamir