Privacy Policy

1. The principle: collect as little as possible

Most privacy policies describe how much data a company gathers. This one mostly describes what we decided not to gather. The service is designed so that the normal, everyday operation of buying and using an eSIM never requires us to learn your identity.

There is no sign-up wall. There is no identity check. There is no "verify your account" step. If you pay in cryptocurrency and skip the optional email field, the records attached to your purchase are a random token, an ICCID, an amount and some usage numbers — and none of those say who you are.

2. What we actually collect

An email address — only if you give us one

Email is optional at every step. You'd give one so that we can send your QR code, so you can recover your eSIM from a new device, or so we can warn you before your balance runs out. If you attach one, we store the address, your notification preferences, and a log of the emails we sent you so we don't send them twice. If you don't attach one, that field is simply empty.

The eSIM itself

To run the SIM we hold its ICCID, the activation profile (the LPA string, the QR code and the install link), its status, and the balance. We can't operate a SIM without these, and there is no anonymised substitute for an ICCID — it's the number the mobile network bills against.

Balance and usage records

The network reports data consumption roughly every ten minutes; we record the amount and deduct it from your balance. That produces a usage ledger and a transaction history, which is what the account page shows you. It records data volumes and cost — not what you did with the data. We do not and cannot see the sites you visit, your messages, or the contents of your traffic.

Payment metadata

We record what a top-up was for, how much, which method, the processor's reference for it, its status, and the confirmation record the processor sends back. Card details never reach our servers — card payments happen on the processor's own checkout. If you deliberately turn on auto top-up, we store the processor's customer and payment-method references so it can be charged again; those are pointers held at the processor, not card numbers.

Support tickets

If you open a ticket we store the email address you typed, the ICCID if you gave one, your message, the page you sent it from, and your browser token so we can find the right eSIM. If you used the chat bubble first, the chat transcript is attached for context. You choose what goes in that box — please don't paste anything you wouldn't want us to hold.

Basic server and abuse logs

This is the part most "we collect nothing" policies quietly skip. Our servers see the IP address of every request, as every web server does, and we use it in two specific places:

• Rate limiting. The support chat endpoint counts requests per IP in a time window so one visitor can't run up the bill for everyone. Those counter rows are deleted after a day.
• Recovery throttling. Failed attempts to recover an eSIM are logged with the access code tried, the IP and whether it worked, so nobody can brute-force their way into somebody else's eSIM. This one is a security log and we keep it.

We don't build profiles from these, we don't join them to your purchase, and we don't use them for marketing.

3. What we don't collect

• No identity documents, passports or selfies. There is no KYC step and no plan to add one.
• No name, no postal address, no date of birth. There is nowhere on the site to enter them.
• No third-party analytics. No Google Analytics, no Tag Manager, no Meta pixel, no Plausible, PostHog, Hotjar, Segment or anything like them. This is a claim about the code, and you can check it — view source on any page and count the scripts.
• No advertising networks, no retargeting, no data brokers. We don't sell or rent anything about you, ever.
• No location tracking by us. The mobile network necessarily knows which country you're roaming in — it can't route data otherwise — but we don't take a location feed from it or store your movements.
• No browsing history. We're a data pipe, not a DNS logger.

Two honest footnotes. The site's HTML carries a single static Google Search Console verification tag — it's a fixed string, it loads nothing and it sends nothing. And our fonts are served by Google Fonts, so your browser fetches two stylesheets and some font files from Google's servers, which means Google sees the IP address making that request. No cookie is set by that request, nothing comes back to us, and it happens on every page whether or not you buy anything.

4. What the site stores in your browser

We don't set advertising or analytics cookies. The site keeps a small amount of state in your own browser instead. Here is every key, in full:

• silent_esim_token — a random string generated in your browser. This is the anonymous token that links this browser to your eSIM so the account page can load it. It replaces a login. It contains nothing about you.
• silent_recovered_esim_id — set after a successful recovery, so the account page knows which eSIM to show.
• silentesim_support_chat_v1 — your support chat history, kept locally so it survives a page refresh.
• silentesim_support_open_v1 — whether you left the chat bubble open. That's all it is.
• silent_attribution_v1 (session storage, cleared when you close the tab) — the first page you landed on, any utm_ campaign parameters in the link you followed, and the hostname of the site that referred you. Not the full referring URL, and nothing at all if you arrived from within our own site. It's attached to a top-up so we know which pages actually help people.
• A session key set by our database provider's auth library — only if you choose to create an optional email login.

Clearing your browser storage clears all of it. Be careful doing that on an anonymous order: the token in silent_esim_token may be the only thing linking you to your balance if you never saved your access code or attached an email.

5. Who else processes your data

Each of these sees only the slice it needs to do its job:

• Supabase — hosts our database. It holds the records described above.
• Stripe — processes card payments on its own checkout, and holds the card data we deliberately never touch. It has its own privacy policy and its own obligations to you as a cardholder.
• Cryptomus — processes cryptocurrency payments. It sees the invoice and the on-chain transaction. It doesn't get an identity from us, because we don't have one.
• The upstream mobile network operator — provisions the eSIM and carries your data. It sees the ICCID, the network you attach to, and your data volumes, because that's what running a mobile connection means. It does not get your email address from us.
• An email delivery provider — only if you attached an email. It receives your address and the message so it can deliver it.
• A third-party AI provider — if you use the chat bubble, what you type is sent to an AI model to generate the reply. Don't put anything sensitive in there; if you'd rather skip it entirely, use the ticket form on the support page instead, which goes straight to a human.

That's the complete list. If it ever changes, this section changes with it and the date at the top moves.

6. Anonymous orders stay anonymous

If you bought with crypto and gave no email, there is no step anywhere in our systems that links your eSIM to a person. We cannot look you up by name, because there is no name column holding one. We cannot hand over an identity we never collected — not to a marketer, not to a partner, and not to anyone who asks. That's not a promise about our good behaviour; it's a consequence of the data we chose not to hold.

If we receive a valid legal demand, we can only produce what actually exists: an ICCID, a balance, usage totals, payment references, and an email address if you gave us one. We'd rather you knew that in advance than read a policy implying we hold nothing at all.

7. How long we keep things

• Your eSIM, balance and usage records — for as long as the eSIM exists. Your balance never expires, so these records can't expire either; deleting them would delete your credit. Ask us to close an eSIM and we'll delete what isn't legally or financially required.
• Payment records — kept while needed for accounting, reconciliation and dispute handling.
• Support tickets — kept while the case is open and for a reasonable period afterwards, so a follow-up doesn't start from zero.
• Rate-limit counters — deleted after one day.
• Recovery attempt logs — retained as a security record against brute-force attempts.

8. Your rights — and the honest limit on them

You can ask for a copy of what we hold about you, ask us to correct it, ask us to delete it, or ask us to stop emailing you. Open a ticket on the contact page and say which one you want.

Here's the catch, and it's a real one: to answer a request we have to find your records, and the only handles we have are an ICCID, an order ID, an access code, or an email you attached. If you bought anonymously, we can't verify that a stranger's request relates to your eSIM — and handing over data to whoever asks would be the actual privacy failure. So include your ICCID or order ID. The privacy that protects you from us also stops us from identifying you on request.

If you're in the EU, UK or another region with statutory data rights, those rights apply and we won't make you argue for them. If we can't fulfil a request, we'll tell you plainly why.

9. Data crossing borders

This is a global service, so data moves internationally by nature. Our database, our payment processors and the mobile networks that carry your traffic are in different countries, and your data will be processed in some of them — including outside the country you live in. Where transfer safeguards are legally required, we rely on our providers' standard contractual terms. The practical protection is the same one as everywhere else on this page: the less we collect, the less there is to move.

10. Children

This service isn't aimed at children, and we don't knowingly collect data from them. Since we don't collect ages, this is a rule we can state but not verify — another reason we'd rather hold as little as possible.

11. Changes to this policy

If this policy changes, the version on this page with the "last updated" date at the top is the one that applies. If a change means we start collecting something new, we'll say so in plain words rather than burying it in a clause.

12. Contact

Privacy questions go through the same channel as everything else: open a ticket from the contact page. If your question is about a specific eSIM, include the ICCID. See also our terms of service.