Where should a trustworthy answer come from?
Use the record that can answer the exact question, keep company claims labelled and say plainly when a real-world check is still needed.
Which sources come first?
Use regulators, courts, company registers, filed accounts and binding terms for legal and contractual facts. Use technical guides for features. Treat marketing as the company’s statement, not independent proof.
- Publisher and title
- Working link
- Effective and access dates
- Product and country
- Exact sentence supported
Can an official page still be weak evidence?
Yes. A real document can be old, describe another product or omit an important qualification. We test whether it supports the sentence beside it, not only whether the page exists.
What makes a hands-on check believable?
Record the country, account type, app version, device, asset, amount, time, steps and limitations; a published hands-on check carries those fixed parameters and pass conditions.
How are company claims shown?
A security, reserve, speed or scale statement stays attributed until independent evidence tests the same scope. Proof of reserves is never called a full audit or solvency guarantee.
What if the answer is not available?
Say ‘not verified’ and explain which record or safe observation could answer it. Missing evidence is not zero, average, safe, dangerous or proof of wrongdoing.
Why is there a retrieval date?
Fees, terms, companies, licences, app versions and incident responses can change. We re-open the linked primary source before changing a conclusion and keep the date beside the evidence.
Do machine-readable files say something different?
No. The visible server-rendered guide is the controlling answer. Structured data, RSS, the research index and llms.txt only mirror or navigate it. llms.txt is not a special Google ranking file.