Editorial policy
Everything we publish that makes a factual claim carries a source and the date that source was read. Competitor information comes from the competitor's own pages, never from a third-party summary. When we are wrong we correct the page and say what changed, rather than editing it quietly.
Why this page exists
We sell a travel eSIM, and most of what we publish is about a market we compete in. That is a conflict of interest, and the only useful response to one is to be specific about the rules we hold ourselves to so that a reader can check whether we followed them.
This page is those rules. It is not a statement of values. Each section describes something we do or refuse to do, in a way that can be checked against any page on this site.
Sourcing
Every factual claim carries a source and a date. Prices, network names, country counts, activation policies and anything attributed to another company appear with a link to where we read it and the day we read it. The sources list at the foot of each research page is that record.
Competitor information comes from the competitor. A price, a policy or a limitation attributed to another provider is taken from that provider's own pricing page, terms, help centre or app — not from a comparison article, not from a press release, and not from a reseller. Where a provider's own pages disagree with each other we say so rather than picking the more convenient one.
A market claim is dated and scoped or it is not made. "Cheaper" is not a claim; "cheaper than provider X for this itinerary, at this data size, in USD, including tax, on this date" is. Where we cannot scope a comparison that tightly, we describe the difference in shape instead of asserting a winner.
We do not publish a number we cannot reproduce. If a figure on this site comes from our own data — a savings percentage, a usage average, a customer count — there is a methodology page saying what was measured, over what period, with what excluded, and the claim links to it. A number with no methodology page behind it should be treated as not yet verified, and should be reported to us using the address below.
Testing
Setup instructions are tested on current devices before they ship. Steps and screenshots for installing or activating an eSIM are checked on current iOS and Android releases, and the version they were checked on is recorded. An instruction we have not run ourselves does not go on the page.
We do not publish an instruction that can cost the reader something. eSIM plans can begin their validity at a moment that depends on what the traveller does, and some actions on a phone cannot be undone. Where a step carries that risk, the page says so before the step, and where our own policy on it has not been confirmed by the product team, we link to support rather than guess.
Comparisons
We name the fit, not the winner. Our product suits a traveller who takes more than one trip and wants to pick exact countries. It is not the right choice for everyone, and our comparison pages are required to say who it is not right for and which alternative is better for them. A comparison in which we win every row is a comparison nobody should believe, including us.
We do not mark up ratings we awarded ourselves. Comparison pages on this
site carry no Review or AggregateRating structured data. A star rating we
generated for a page on which we are one of the compared products is not a
review, whatever a search engine would do with it.
We disclose the obvious. Every comparison page states plainly that Hoam eSIM publishes it and sells one of the products in it.
Corrections
We correct the page, and we say what changed. When a factual error is found, the page is fixed and a dated note is added describing what it said before. Silently editing a claim out is the practice this section exists to rule out: a reader who acted on the old version has no way to learn that it changed.
Two dates, because they mean different things. Every research page shows when it was last updated and, where it makes external claims, when those claims were last verified. A page reformatted in March is not a page checked in March, and showing one date would let the second pass for the first.
Stale is a defect. A comparison whose sources have not been re-read within its review period is treated as broken rather than merely old — it is either re-verified or withdrawn.
Telling us we are wrong
Write to [email protected] with the page and the claim. A correction to a factual error does not need to be persuasive to be actioned; it needs to be specific. If you are a provider we have described incorrectly, the same address reaches us, and we will link to your own page for the corrected fact.
What this policy does not cover
This page governs the guides, comparisons and methodology documents published on this site. It does not govern the Help Centre, whose job is current operational steps for our own product, or product marketing copy, or the terms of service. Where a support article and a page on this site disagree about how our product behaves, the disagreement is a bug — please report it.