Privacy

Most privacy pages describe an analytics stack. This one describes the absence of it. Every claim below was checked against the live site on 8 September 2026 with a real browser, not written from a template.

Reading the site

No analytics, no session recorder, no A/B tool Arrive from a search result, a link or a bookmark and the page makes zero requests to any host other than esimrules.com. There is no Google Analytics, no pixel, no session recorder, no A/B tool, and nothing that follows you between sites.

One exception: arriving from a Google ad If your link carried a Google click id, or you are on the order page, one script loads from googletagmanager.com so the ad campaign can count the sale. It sets Google's own _gcl cookies. That is the only third-party request this site can make, it does not run for anyone else, and you can see it for yourself in the browser's network tab.

No cookies of our own We set none. Not for consent, not for sessions, not for preferences. The only cookies you can end up with are Google's, and only in the ad case above.

One item in local storage: your theme Choosing the Apple or Android look stores esimrules-theme in your browser. It never leaves your device and we never read it. Clearing site data removes it.

Server logs The site runs on Cloudflare, which processes request metadata (IP address, user agent, URL) to serve and protect it. We do not build profiles from it and do not export it.

Buying an eSIM

This is the only place where you give us anything, and it is the minimum needed to hand you the product you paid for.

Your email address Entered on the payment page. We use it to send the eSIM profile, to answer you if something goes wrong, and once after your plan is delivered to ask how the connection worked. That review request goes out one time per order and never again. There is no mailing list, no newsletter, and we do not pass your address to anyone but the payment processor.

Card details go to Stripe, never to us Payment runs on Stripe's own hosted page. We never see, receive or store a card number. Stripe is the processor and keeps the payment record under its own policy.

The order record we keep Payment session id, the package you bought, your email, the amount, and the eSIM identifiers (ICCID and activation details). It exists so the order page can show your profile again and so refunds and disputes can be checked.

What the operator gets To issue the profile we send Airalo the package and an order reference. Your email is not part of that request.

Who processes what

Processor	What it handles	Why
Cloudflare	Hosting, request metadata, the order database, outgoing and incoming mail	The site runs there
Stripe	Payment, card data, your email at checkout	Taking the payment
Airalo	Package and order reference	Issuing the eSIM profile

Your rights, and how to use them

Write to support@esimrules.com and ask for a copy of what we hold about you, a correction, or deletion. We answer within one business day. Deleting an order record removes your ability to re-open the profile from the order page, so we will say so before doing it. An eSIM already issued cannot be recalled from the operator.

The controller is JET SHARING MOBILITY LLC, trading as eSIM energy, registered in the United States. Contact: i.bulgakov@jetshr.com · +56 9 5534 2589.

Checked against the live site on 8 September 2026; last change: the email section now names the one review request we send after delivery, and the tracking section now names the Google ad script, which used to load on every page while this page said it did not. If we add anything that collects more than the above, this page changes first, and the change is listed on what changed.