Sources
We publish factual claims only when we can trace them to a primary source. In order of preference:
- The official documentation of the developer or manufacturer.
- The listing in the official store the software is distributed from.
- Legal texts and measures issued by the competent authorities.
- Technical specifications published by standards bodies.
We do not treat as sources: user reviews in the stores, material from forums and messaging channels, or articles on other sites that do not themselves cite a primary source.
When a piece of information cannot be verified, we say so. The tables on this site contain cells marked “n/a” for exactly that reason: they mark data we were unable to confirm.
Checking
Every page containing technical data — compatibility, supported features, requirements — is compiled from the sources listed above and recorded in a structured store, rather than written by hand into the text. That allows a value to be updated in one place and to be reflected everywhere it appears.
The data on apps sits in a dedicated file, with a field recording whether it was verified first-hand and the date of the last check: the protocol is described in how we test. While that field is empty, the site says so openly.
Updates and dates
We distinguish three dates, and we treat them differently:
- Publication date: when the page appeared. It never changes.
- Update date: it changes only when the content changes substantively. Typo fixes and design work do not move it.
- Date of last hands-on check: it appears only when we have personally tried what we are writing about.
We do not update dates to simulate freshness. It is a widespread practice and we regard it as a form of deception towards the reader.
Corrections
If we publish something wrong, we correct it. For substantive errors — an incorrect technical figure, an imprecise statement of the law — we add a visible correction note on the page, stating what was corrected and when. We do not quietly remove the incorrect content.
Reports are sent through the contact page. Those accompanied by a reference to an official source go to the front of the queue, because we can check them immediately.
Content we do not publish
This is an editorial choice rather than a legal obligation, and we spell it out because it covers a substantial share of what people search for on this subject.
We cover these subjects where doing so informs — explaining how a phenomenon works, what risks it carries and what alternatives exist — but we never supply the practical instructions for taking part in it.
Use of automated tools
Assisted writing tools may be used in drafting and in language editing. They are not used to generate factual claims: every figure published is traced back to a source by a person before publication, and editorial responsibility for the content remains with the editorial team.
Commercial relationships
The rules on advertising, affiliates and sponsored content are on the revenue transparency page. The underlying principle: a financial relationship never determines the presence, the absence or the position of a product in our content, and every existing relationship is declared on the page it concerns.
Copyright notices
If you believe content published on this site infringes a right of yours, write to the address given on the contact page, specifying the URL, the nature of the right and how you can be reached. We will check and reply.