Editorial policy
The rules every piece of content must pass before it goes live.
Last updated September 6, 2026
The publication pipeline
- An idea comes from a question readers actually ask.
- A brief sets the search intent and the sources required.
- A draft is written.
- Editorial review covers language and structure.
- Fact check against the cited sources.
- Approval, then publication.
- A review date is set, and the page is archived when it stops being useful.
What we never do
- We do not invent reviews or testimonials. Only genuine customer feedback is shown.
- We do not invent experts. Where no named human is assigned, the byline says it is our editorial desk.
- We do not copy another site's text, images or design.
- We do not invent travel regulations. Without an official source we tell you to check with the authority itself.
- We do not create thin or doorway pages that exist only for a keyword.
The single principle behind every rule here
Every rule on this page comes from one sentence: a reader must always be able to tell what we know, what a supplier told us, and what is the editorial desk's opinion. A site that both sells eSIMs and writes the guides has an incentive to blur those three together, because a confident sentence sells better than one that says this depends on your handset. Writing the rules down means the person drafting the next page does not have to make that judgement call from scratch.
This standard applies to every kind of content on the site: guides, destination pages, FAQ entries, the explanatory copy inside our calculators, and the short lines that sit on a plan card. If a buyer reads it, these rules cover it.
Who writes, and who is accountable
Every page has one accountable owner, either a person or a desk. Where we cannot point to a real, verifiable human author, the byline says the editorial desk rather than a name we made up. We do not build fake expert profiles, we do not attach photographs of people who do not exist, and we do not award anyone a professional title they do not hold.
Accountability does not end at publication. The person who approved a page is the person who answers when a reader says it is wrong, and the person who decides whether it gets corrected, reworded or pulled.
Three grades of statement, and how each is marked
Before a sentence clears review, an editor has to say which of three grades it belongs to. Different grades need different evidence, and they have to be phrased differently.
| Grade of statement | What must back it | How it must read |
|---|---|---|
| A verifiable fact | Public documentation from a manufacturer, a provider or a government body | Stated plainly, with the source and the date we checked it |
| Information a supplier states | The supplier's own spec page or the data in their system | Marked as supplier-stated, never written as if we measured it |
| An editorial judgement | Reasoning shown to the reader, not just a verdict | Written as a conditional recommendation: suits this case, for this reason |
| Something we do not know | No source we can stand behind at the time of writing | Stated as unknown, with a pointer to who can answer it |
These grades decide both the evidence required and the wording allowed.
The grade most eSIM sites get wrong is the second, because supplier information reads like fact when it is actually a claim from a commercially interested party. We are not saying that information is wrong. We are saying we will not present it as though we stood on the street with a stopwatch ourselves.
The sourcing rule
A factual statement has to trace back to something a reader could open themselves. Where the source is a supplier-only document, we say the information came from the supplier rather than dressing it up as common knowledge. When two sources disagree, we write about the disagreement instead of quietly picking whichever number sounds better.
Travel rules, tax and customs limits, and SIM registration requirements in some countries can change without notice and differ by nationality. We therefore never write them as a final answer. We describe what the official source says and tell you to check with that authority again before you travel.
Prices and specifications that move
The numbers that move fastest on this site are plan prices and data allowances. Our rule is that those figures come only from the synced provider data, and are never typed into the prose of an article, because articles are not re-read every day while prices can change any day.
The pre-publication checklist
Before a page goes live, the reviewer walks this list item by item. If one line fails, the page goes back to the writer — it does not ship with a note promising a fix later.
- Every factual statement has an identifiable source and a date we last checked it.
- No speed figure, coverage claim or percentage appears without an origin.
- Anything that depends on a handset or OS says so, by model and version.
- Every link resolves, and goes straight to the plan page or the supplier's own documentation, not a link that pays us anything.
- Refund wording matches the policy that actually applies, not a friendlier version of it.
- No support promise exceeds the support hours we publish.
- The Thai and English say the same thing; neither carries a guarantee the other lacks.
- The page answers a question readers actually arrive with, rather than existing for a keyword.
Fact checking happens line by line
Our fact check is not a read-through that ends in a feeling that it sounds about right. It is done a sentence at a time, and the reviewer leaves a trace of what was checked.
- 1Highlight every factual sentenceThe reviewer marks every sentence that asserts something checkable — a handset supporting eSIM, a country requiring SIM registration. Sentences that merely explain reasoning are left alone.
- 2Find the source behind each oneEach highlighted sentence must pair with a source. If it cannot, the sentence is cut or rewritten as something the reader should check themselves — it is not left standing because it seems reasonable.
- 3Confirm the source actually says thatOpen the source and read the relevant passage rather than trusting the writer's summary. The most common error we catch is a source that refers to a different model variant or a different country from the one the article claims.
- 4Check the age of the sourceAnything older than the page's own review cycle is re-checked for currency. The two things that change most often are OS menu names and entry requirements.
- 5Record the check against the pageThe reviewer logs the date and the sources used, so whoever handles the next review cycle knows what was already verified and does not start from zero.
- 6Send back or approveIf unsourced sentences remain, the page goes back to the writer. Approval means the reviewer shares responsibility with the writer for what the page tells a reader.
Thai and English must say the same thing
This site is written in two languages, and we treat both versions as carrying equal weight rather than as an original and a translation. The rule that follows is that neither side may carry a guarantee or a caveat the other lacks. If the English says it depends on your handset, the Thai has to say the same, not sound more confident because the audience is different.
In practice the Thai is written as Thai from the start, not translated word for word, because literal translations of technical explanations tend to read like nothing at all. What has to match is the facts and the conditions, not the sentence structure.
Instructions that depend on the handset and OS version
The menu names used to install an eSIM differ by manufacturer and by OS version. Two handsets running the same system can label the same screen differently, and a single system update can move it. Our rule is that a guide describes what to look for rather than asserting exactly where the menu sits on every device.
Drafting tools and human accountability
We may use writing tools while drafting and outlining, but no page ships until a human has read every line and taken responsibility for it. Language tools produce over-certain sentences very easily, particularly where the honest answer is that it depends on the supplier, so finding and cutting those sentences is part of the reviewer's job.
The conflicts of interest we actually have
We sell eSIMs ourselves, and that is a real interest that writing a policy does not make disappear, since our revenue is the margin on the plans we sell. What a policy can do is decide where that interest is not allowed to surface: revenue is not a ranking factor, and a recommendation has to justify itself without any reference to margin.
Equally, we will not pretend to be disinterested. A page recommending our own plan says we are the seller, and a page linking to another seller says who your contract would be with once you click through.
Reviews and customer voices
We do not write our own reviews, buy them, or polish a customer's words into something warmer. Where we edit customer text at all, it is to remove personal information — never to remove the criticism.
Reviewing pages, and taking them down
Pages do not only go wrong by being wrong at the outset. Most go wrong because the world moved after publication, so we define the events that force a page back into review without waiting for its normal cycle.
| What happened | What we do to the affected pages |
|---|---|
| A major OS release renames a menu | The install and troubleshooting guides are reviewed as a set, ahead of anything else |
| A supplier changes plan terms or withdraws a plan | Pages referring to it are corrected and any recommendation that is no longer true is pulled at once |
| A reader reports that the guide did not work for them | We re-check against the reported model and version, then widen the guide to cover that case |
| A destination changes a rule that affects travellers | The destination page is updated, and where we cannot confirm it yet we say we are checking rather than guess |
| The page no longer helps anyone | It is retired and points to a replacement, rather than being left up for search rankings |
These triggers run in addition to the scheduled review cycles.
When we do not know, we say so
Many eSIM questions have no single answer that holds for everyone, because the answer depends on your handset, on the provider issuing the plan, on the local operator, or on that country's law. The honest response is to say what it depends on, and to say who can give you a definitive answer.
We treat the sentence we have not been able to verify this as usable content, not a gap to be filled with something that sounds better. A reader told plainly what to check next loses less time than one who believes a wrong answer and finds out at the airport.
Complaints about content
If you think a page misleads, tilts towards what we sell, or cites a source wrongly, send it to us on LINE @esimonline at https://lin.ee/skDPoNx, by email at esimonline.asia@gmail.com, or by phone at 089-942-0818 / 088-521-6848. We take messages around the clock, every day.
A complaint is read by someone other than the page's author, so the same person is not judging their own work. If the review concludes the content was right, we reply with the sources we used, so you can check whether we read them correctly.
FAQ
Does this policy cover the product pages too?+
Yes. The descriptive copy on a plan page sits under the same rules as an article. The difference is that the price and data allowance come from synced provider data rather than from something an editor typed, while the explanation of who a plan suits and what its limits are goes through exactly the same review as an article.
Why do some pages not carry a person's name?+
Because we have no publicly verifiable individual to attach to that page. The choice is between inventing a credible-sounding name and saying plainly that it is desk work, and we take the second. Those pages still go through review and still have an approver who is accountable for them.
If a supplier gives us wrong information, who is responsible?+
The page is ours, so correcting it and telling readers is our responsibility even when the error originated in what a supplier told us. When we find one, we fix the affected pages, mark it as a correction, and raise it with that supplier. What you are entitled to as a buyer — a refund, for instance — depends on that seller's terms and on how you paid.
Does this site take paid articles?+
Articles here are written by the editorial desk. We do not sell space for someone else to publish an article under our name, and we run no creator or affiliate programme you could join. Our revenue is margin on the plans we sell ourselves, and business orders — all set out on the about page.
How can I tell whether a page reports supplier information rather than your own testing?+
Look at the wording. We write according to the provider or according to the manufacturer's specification when the information comes from a supplier, and we never write we tested or we measured unless we did it ourselves. If you find a page ambiguous enough that you cannot tell, that is a defect on our side and we would like to hear about it.
Instagram and TikTok have no web share button, so we open your phone's share sheet or copy the link instead.