A clear account of the data this site does and does not handle

Last updated: 09 January 2026

esimly is an independent informational publication. This policy describes information practices for esimly.digital, including the site’s use of third-party delivery services and the mailto contact form. It is written for readers in Europe and elsewhere who want a practical account rather than vague assurances.

Code editor open on a laptop screen — The publication limits its own collection and describes the third-party requests a page can make. Photo: Unsplash

Scope and controller

This policy concerns the public editorial site at esimly.digital. For privacy questions about the site, contact [email protected]. The address is an editorial inbox, not a mobile-service helpdesk. The site does not operate accounts, sell subscriptions or manage eSIM profiles.

The policy does not govern an operator, mobile carrier, eSIM provider, email application, browser or other third party. Each may have its own privacy notice and data practices. A reader should review the relevant party’s policy before providing personal or account information to it.

Cookies and local storage

esimly sets no first-party tracking cookies. It does not use cookies to build advertising audiences, follow readers between sites or create an editorial account. The site has no sign-in function.

The dark or light display preference may be saved in the browser’s local storage under the key esimly-theme. That preference stays in the browser until the reader changes it or clears local storage. It is not sent to an esimly server and is not used to identify a person. A reader can prevent or remove it through browser settings; the site will then use the system preference where available.

Analytics and server information

This site does not use a first-party analytics platform or behavioural measurement script. It does not maintain a visitor database, profile visitors or sell browsing data. Ordinary web hosting and network delivery may process technical request information such as an IP address, browser request headers, time, requested URL and security logs in order to deliver and protect the page. Those operational records are controlled by the relevant hosting or network provider under its own policies, not used by esimly for audience profiling.

If hosting arrangements change and introduce material site-side analytics or tracking, this policy will be updated before that practice is presented as part of the site. The date at the top of the page identifies the current policy version.

Illuminated corridor of data centre server racks — Network delivery can involve technical requests even where the publication keeps no visitor profile. Photo: Unsplash

Contact form and email

The form on the contact page is a client-side convenience only. It uses JavaScript to compose a mailto: message addressed to [email protected] in the reader’s own email application. No form data is transmitted to or stored by the website. The reader’s email application and email provider determine whether the message is sent and how it is handled.

If a reader sends an email, the message and its normal email metadata are received in the editorial inbox. Use the message to consider the stated correction, source or question. Do not send passwords, QR codes, activation data, account numbers or other unnecessary sensitive information. We do not ask for it and cannot use it to access a mobile service.

Emails may be retained only for the time reasonably needed to correspond, assess a correction or maintain an editorial record. We do not sell correspondence or use it for marketing lists. A request to delete or access a message can be made at the address above, subject to legal, security and record-keeping needs.

Third-party services and requests

The pages use the Tailwind CSS CDN to provide styling resources, Google Fonts to request the IBM Plex typefaces, and Unsplash image URLs to display the editorial photographs specified for the site. Loading these third-party resources can cause the browser to make a request to those services. That request can expose ordinary technical data such as IP address, browser information, requested resource and referrer information according to the reader’s browser and the third party’s policy.

These providers are separate controllers or processors for their own services. esimly does not control their retention, cookies or geographic processing. Readers who prefer to limit such requests can use browser privacy controls, content blockers or a network configuration of their choice, understanding that this may affect the page’s appearance. Links to external resources are not endorsements of their privacy practices.

Legal basis, rights and choices

Where personal information is processed through a voluntary email, the relevant basis is ordinarily the reader’s decision to send it and the legitimate interest in responding to editorial correspondence or correcting published information. Technical delivery and security processing may be necessary for operating a public website or reflect the hosting provider’s legitimate interest in secure delivery.

Depending on applicable law, including GDPR-style rights in Europe, a person may ask for access to personal data, correction of inaccurate data, deletion, restriction, objection to certain processing or portability where applicable. A person may also complain to the relevant supervisory authority. Requests should identify the information and context needed to locate it without sending additional sensitive data. We will assess requests under applicable law and any obligations to preserve necessary records.

Changes and related information

We may revise this policy when the site’s practices, suppliers or legal context materially change. A new last-updated date will appear above, and changes will not retrospectively make an earlier contact submission part of a marketing programme. For the editorial purpose and independence statement behind the site, read about esimly. For terminology, travel preparation and device checks, visit the main guide, device file and FAQ desk.