Cookie policy. No brand can pay to rank higher on Simscanner.
Simscanner is an independent travel eSIM comparison site that ranks brands country by country, and compares regional plans across the countries each region covers.
Policy · Effective 30 May 2026 · v1

Cookie policy

Effective 30 May 2026 v1
The policy, in one line

Simscanner uses a minimal set of cookies.

One language and viewport preference cookie is set only after explicit interaction. No advertising cookies are set. No third-party tracking pixels are loaded by default. Visitors can opt out by clearing browser cookies or by using browser-level blocking. The full inventory follows.

Cookies Simscanner sets

Inventory

Simscanner sets one client-side cookie named pref containing the visitor's language preference and viewport choice. The cookie is set only after the visitor interacts with a preference control. The cookie lifetime is one calendar year or until cleared. No advertising identifier, no cross-site identifier, no device fingerprint, and no behavioural profile is stored in any cookie.

Strictly necessary

Essential cookies

Simscanner does not currently set any cookie classified as strictly necessary. Site navigation, search, and route serving work without any cookie being set. The pref cookie listed above is a preference cookie, not strictly necessary. If essential cookies are added in the future (for example, session security on a future authenticated area), they will be listed here with name, purpose, and lifetime before being deployed.

Settings remembered between visits

Preference cookies

The pref cookie stores the visitor's preferred language code (en-GB by default) and viewport choice (auto, mobile, desktop). The cookie is set only after the visitor interacts with a preference control. The cookie lifetime is one calendar year. Visitors may delete the cookie at any time without affecting site functionality; on a subsequent visit the site defaults to auto.

External requests

Third parties

When the browser renders a Simscanner page it makes requests to two external endpoints. Google Fonts serves the Fraunces, Geist, and Geist Mono webfonts; the request includes the visitor's IP address. The Google favicons service serves brand favicons used in identity tiles; the request includes the visitor's IP address. Neither service sets a cookie on the Simscanner domain. Visitors who block third-party requests at the browser level will see fallback fonts and missing favicons but no loss of functionality.

Browser-level controls

How to opt out

Visitors can delete or block the pref cookie using browser settings. Most browsers expose a cookie inventory under Settings, Privacy, Cookies. Blocking third-party requests to fonts.googleapis.com and google.com/s2/favicons will prevent the external font and favicon requests described above. Simscanner respects the browser Do Not Track signal where it is sent, even though the site sets no tracking cookie regardless.

Cookie-policy questions

Contact

Questions about this cookie policy should be sent to privacy@simscanner.app. Simscanner aims to acknowledge within 5 working days. Updates to the cookie inventory are dated at the top of this page and listed in the revision history.

Structured data on this page: Article BreadcrumbList. No FAQPage schema is emitted: this policy is a single declarative document. No Product, Offer, AggregateRating, or Review schema is used.
Notes for the delivery team
  • The build brief's "Crawlable FAQ" instruction asks for a visible FAQ on every page, but the zero-paid-placements content pack explicitly renders no FAQ section and supplies no FAQ copy (section 7 and section 11). The content pack is treated as the source of truth, so no FAQ section and no FAQPage schema are emitted here. Confirm this is intended before sign-off.
  • Enforcement-map cards link to internal QA files (qa/qa-checklist.md, qa/schema-audit.md, qa/internal-link-audit.md) using the ../ relative convention. Confirm those files exist in qa/ at port time.
  • This is the reusable policy template. The same chrome renders /policies/editorial, /policies/data-sources, /about, and the remaining policy family by copy substitution only.
  • Internal links use the ../ relative convention from the brief and resolve to clean URLs after the post-extraction rewrite.