The short version: every outside claim names its source and the date somebody read it, and a job re-reads all of them every Monday. All 24 are listed on the sources page, which is generated from that same list rather than typed.
Phone verdicts
We answer 120 models, and say eJugaar works on 86 of them. A verdict comes from the maker’s own published eSIM list or the model’s own specification sheet — never from a retailer, a comparison site or another eSIM seller. Each brand’s source and the date it was read are printed on that brand’s page.
Three answers are possible, and the middle one matters most. "Yes" means the maker lists it. "No" means the hardware is not there. "Depends on the variant" means the same model name is built differently for different countries — and on those we tell you to check your own handset before buying, because your unit is the only proof that counts.
Where a maker publishes no list at all, we say so on the page rather than guessing from a spec sheet for one model and applying it to a whole brand.
Guides
There are 6 guides, each written in both languages and each carrying its sources and the date they were last read. A guide may only link to a page that exists — a test fails the build otherwise — and none of them may present the eSIM as a replacement for PTA registration, which is both a legal line and a test.
We quote PTA in English only. A translated sentence inside quotation marks is not a quotation, and on a regulatory question that difference is the whole thing.
When nobody can answer
Some questions have no published answer. When that happens the page says it is not known, and says who would have to say otherwise. The PTA tax page is the clearest example: we will not print what registration costs for a named phone, because FBR’s last consolidated rate sheet is from 2021-22 and their per-model values come from valuation rulings. Other sites print a figure anyway. We link you to FBR instead, and do the arithmetic on the number they give you.
Prices
Every price on the site comes from one place in the code, so the plan page, the checkout, the machine-readable data and any structured data a search engine reads cannot disagree with each other. A price shown in a search result is the price you pay.
Re-checking, and corrections
Every Monday a job opens all the sources and looks for the exact sentences our pages lean on. If one has changed, or a maker has dropped a model from its list, it emails us — because the failure mode here is silent: nothing breaks, the page simply keeps stating yesterday’s answer under today’s confident heading.
- A source that refuses an automated read is marked as such, not reported as broken — a block is not a retraction.
- A dated news report is cited for what it said on its date; it is not expected to change.
- Found something wrong? Tell us and we will fix the page — the contact page has every way to reach a person.
What we will not do
- Publish a review we did not receive, or a delivery count we did not deliver. Where there is no real number, the component does not render.
- Sell a plan for a phone we believe will not take it. The compatibility answer turns the sale away when the answer is no.
- Market it as a replacement for PTA registration. It is a roaming data eSIM: it does not register your phone, and it does not settle what FBR charges. Both of those stay true whatever you buy from us.
- Machine-translate a page into a language nobody here reads. A locale goes live only after a native speaker has reviewed it.
Every document behind all of this is listed on the sources page.
