Editorial Policy: How We Source Numbers, Dates, Disputes
How we test (device, date, city, carrier — named every time)
A test claim on this site names a device, a date, a city and a carrier, every time. No page here makes that claim yet.
This project has not assigned a named author. Until it has, we do not write “we tried this and it worked”. We write what we checked instead, and we tell you which one you are reading.
You will see a line like “checked 10 August 2026” next to a source link on every page that carries a live product detail. That is a verification date, not a test result. The two stay labelled as different things. When a personal device test does appear here, it will carry all four fields above, inside the body of the page, not folded into a general claim about how something works.
How we source regulatory numbers (primary document beats secondary always)
A regulatory figure gets published only once it traces to a primary document — a law, a Gazette notice, a regulator’s own page — not a summary of one.
Turkey’s 2026 device-registration duty is the working example. The primary text, Harçlar Kanunu Genel Tebliği Seri No. 98 (Resmî Gazete, 31 December 2025, No. 33124), sets it at 54,258 TL. That is the figure we treat as the base. A second number, 57,241 TL, circulates on a site that ranks for the same search but names no comparably solid source. Both numbers stay on the page they belong to, both dated, each traced to the source it came from. Neither replaces the other.
The same rule covers currency conversion. Where a figure crosses from TRY to USD, this project’s working exchange-rate range, 40 to 43.5, is stated as our own assumption next to the number, not printed as a verified market rate.
How we handle open questions (we publish the disagreement, not a guess)
Where the evidence conflicts and no source settles it, the page names the conflict instead of picking a side. The formula holds everywhere it applies: no official answer exists; here is what the regulator publishes; here are two dated pieces of evidence; here is where they disagree.
The BTK ban status page runs it on a live case. A January 2026 community report says a blocked provider works from inside Turkey and takes payment there. BTK’s wave-one decision of 10 July 2025 lists that same provider as blocked. The page states both , treats the official record as the default, and marks the community report unverified until you check it yourself.
Naming a default is not resolving the conflict for convenience. It tells you which way to lean while the disagreement stays visible, not buried under one confident sentence.
How we update and how we correct (review date in the metadata, last-verified line at the foot)
Every page carrying a regulatory number gets a review date and an owner, because the material expires. Ownership sits with the editorial team today, and moves to a named author once one is on record.
A page priced or dated against a fee schedule, a blocklist or a registration window carries a next-review date in its own metadata. It also carries a “last verified” line at the foot of the page, naming the sources it was checked against and the date.
Before a decision number, a fee or a deadline goes live, we trace it back to the primary document it claims to come from. A claim that cannot be traced does not get quietly dropped, and it does not get quietly kept either. It gets logged as unverified in this project’s own working notes, then pulled from the page it was on.
How we make money (commercial-interest disclosure)
Where a link on this site is commercial, the page carrying it says so — on that page, not in a footer nobody reads. Buying through one may pay us a commission, or you may end up paying us directly for the plan itself. Either way, which provider we describe first, and how we describe it, does not change.
A price on this site appears only as a dated fact: what a package costs, on what network, for how long. It never appears as an argument. We do not write “cheaper” or “better value” about our own product or a competitor’s, and we cut that phrasing out of a community quote before we publish it too.
What we do not do
Four things stay off this site, regardless of which page is asking.
- We do not give legal advice. A fee, a deadline or a registration procedure can change after we publish it; the regulator and Turkey’s e-Devlet portal are the only authoritative answer, review date on this page or not.
- We do not register a device, file a form, or act on a reader’s behalf with any regulator.
- We do not promise a connection stays up, and we do not state that a travel eSIM revives a phone already blocked by its IMEI or gets around a VoIP block. Neither claim is settled by the evidence we have, so neither appears here as fact.
- We do not publish under a composite or invented author. A byline on this site is a real, named person, or it reads “editorial team” — never a persona built to look like one.