Cookies

1What cookies are, and why this page exists anyway

A cookie is a small file a site asks your browser to keep and send back on every later request, which is what makes it useful for recognising a returning visitor and what makes it a tracking tool. Local storage is the other common mechanism: it also lives on your device, but it is never attached to a request, so a site can only read it with code running in the page. This page covers both, because from your side the question is the same: what is being kept, and who can see it.

2What is stored on your device

Two entries that we write, the cookies Google writes for the analytics and for the ads, and the ordinary browser caching every website relies on.

• esimradar.currency: local storage, written only when you change the display currency. It holds a three-letter currency code and nothing else, stays until you clear site data, and is never sent to us: prices are converted in the page, on your device.
• esimradar.consent: local storage, written only when you answer the analytics banner. It holds the word granted or denied and nothing else, is what stops the banner asking again, and never leaves your device.
• _ga and _ga_ plus the property id: cookies set by Google Analytics, and only after you have said yes. They hold a randomly generated identifier that lets Google recognise the same browser on a later visit, and they expire after two years. Say no, or say nothing, and they are never written.
• Cookies and local storage set by Google’s ad script on the plan boards, under Google’s own domains. Say yes to the banner and they may be used to choose ads from what Google knows about your browser. Say no, or say nothing, and the ads are non-personalised, though Google may still store enough to cap how often you see one banner and to catch click fraud.
• Your browser’s normal cache of our pages, stylesheets, fonts and scripts. That is how the web works rather than something we set, it holds no information about you, and a hard refresh clears it.

That is the complete list. Nothing we write is set before you have asked for it, and nothing on it identifies you to us.

3Why there is a banner, and why it is worded the way it is

Consent is required for storage that is not strictly necessary for the service you asked for: analytics, advertising and profiling, in practice. We do two of those three. So the banner asks about exactly those two, and it asks honestly: both are already running in their quietest mode, where analytics stores nothing and the ads are picked from the page rather than from you, and the question is only whether they may go further. Declining is a real answer that changes real behaviour, which is more than most banners can say.

Both buttons are the same size and the same weight. A banner that makes one answer easier than the other is not asking a question.

4Analytics

Google Analytics 4, and nothing else: no session recording, no heatmaps, no remarketing pixel, and no tag manager waiting to load one. Its advertising signals are denied until you answer the banner, and Google Signals and advertising features are off in the property itself. Everything else on a page is served from our own domain, including the two typefaces, which is a common exception people are surprised to find in their browser logs. The privacy page describes what is recorded and what is deliberately not.

5Advertising

Google AdSense fills the banners between the rows on a plan board, and that script is the second thing on a page we did not write. Before you answer the banner every ad is requested as non-personalised: Google is told explicitly that it may not use what it knows about your browser, and it picks from the page instead. Saying yes lifts that. Saying no keeps it in place, and the ads stay where they are rather than disappearing, because they are what pays for the site.

Non-personalised is not the same as storage-free. Google may still keep enough to stop you seeing one banner ten times and to catch click fraud, and those cookies sit under Google’s domains rather than ours, so clearing site data for esimradar.com does not reach them. Google’s own ad settings page does.

6Cookies set by other sites

The moment you follow a deal link you are on the provider’s site, or on the affiliate network that handles their referrals, and they set their own cookies, usually to record that the visit came from us so a commission can be attributed. We do not control those cookies and their policies govern them.

Blocking third-party cookies breaks nothing on eSIMradar. The only consequence is that a provider may not credit us for the referral.

7How to remove what is stored

Clear site data for esimradar.com in your browser settings, or use private browsing. That removes the currency preference, your banner answer and any Google Analytics cookie; the site keeps working, the display returns to US dollars, and the banner asks again so you can answer differently. Google’s ad cookies live under Google’s own domains, so they go with a browser-wide clear or from Google’s ad settings page rather than from ours. Browser settings can also block storage entirely: the site is built to survive that, analytics stays in its cookieless mode, and an ad slot that cannot be filled collapses.