This page sets out what we actually do before writing about an IPTV service, an app, or a setup, and what the limits of that are. It is written so you can judge how much weight to give anything you read here.
What can be checked, and what cannot
Some things are verifiable: what a plan page says, which devices an app is published for, whether a documented setup route works, how a provider answers a pre-sales question, and what the cancellation terms are in writing. Other things are not reliably verifiable from outside, including total channel counts, long-term stability, and what a service will still be doing in six months. We separate the two instead of blurring them.
The checks we run
- Plan and terms review. We read the current pricing page, the trial terms, the refund or cancellation wording, and the accepted payment methods, and record them with the date we read them.
- App and device support. We confirm which apps a service documents, and whether those apps exist for the devices it names.
- Setup route. For any installation or configuration we describe, we follow the steps ourselves on the device in question and record where they differ from the provider instructions.
- Playback checks. Where we have access, we record what we saw: start-up behaviour, picture quality, how the guide behaved, and any stalling, on a stated connection and device.
- Support contact. We send a pre-sales question and record whether, and how fast, a human answered.
- Documentation quality. We note whether the provider publishes enough information for a buyer to make an informed decision before paying.
Devices and dates
Every article names the devices used for its checks and the date the checks were made. If an article does not name a device and a date for a claim, treat that claim as drawn from the provider rather than from us.
How we weigh what we find
There is no single score behind the recommendations. We weigh, in roughly this order: whether the key terms are stated clearly before payment; whether the service works on the devices the reader actually owns; the quality of the evidence available for its claims; the limitations a buyer would want to know about; and the clarity of its content rights position.
Keeping articles current
Articles are revisited when a provider changes its pricing or plans, an app or device changes, a reader reports something broken, or the article is simply old enough that its details need rechecking. The date on an article reflects its last substantive review.
Limits you should know about
- We are a small editorial team, not a laboratory, and we cannot test every service continuously.
- A service that worked on our connection may behave differently on yours.
- We cannot audit the content licensing behind a provider, and we do not claim to.