Privacy Policy
Effective date: October 9, 2026
This Privacy Policy explains how BILPP OÜ (“we”, “us”), a company registered in Tallinn, Estonia, collects, uses and protects your information when you use the balkanesim.app website and the Balkan eSIM app for iOS and Android. It is written to be read rather than skimmed past: each section says what we actually do with your data, in the order you are likely to wonder about it. If anything here is unclear, ask us and you will get a plain answer.
1. What we collect
The website itself collects very little. Until you answer the consent bar it sets no cookies; if you accept, Google and Meta set the cookies listed in the table below so we can tell which adverts and pages lead to an install or a sale. A few things are written to your browser's own storage whatever you answer: your language choice and your consent answer; when you arrive through a link tagged by one of our adverts, a note of that advert's campaign name and click id (Meta's fbclid, Google's gclid and the like), which expires after the period shown in the table; when you arrive through a referral link, its referral code, kept for 30 days; and when you claim a gift eSIM from a venue's QR code, a random id for this browser, sent with that claim so the same gift cannot be claimed over and over from one browser. None of these notes holds a name or email; the advert note leaves your browser only with an order you place on this site or a tap on one of our app-store badges, so the sale or install can be credited to the advert. Cloudflare Web Analytics runs either way and is the exception worth naming: it counts page views without cookies and without identifying anyone. You can browse the whole site, including every destination and price, without accepting anything and without an account. Buying — in the app or on this site — collects what delivering an eSIM requires: your email address and order details, the technical data needed to provision an eSIM profile on your device such as device eSIM identifiers, and the content of any support conversation you start with us. On its first launch the app also reads the install source the store hands it: on Android the Play Install Referrer, which carries the campaign parameters of the link that led to the store, and on iOS Apple's AdServices attribution, which says whether an Apple Search Ads campaign led to the install and which one. Neither contains your name.
2. How we use your information
We use the data you give us when you buy to run the service: to take and confirm your order, to deliver and provision your eSIM, to answer support requests, and to meet our accounting and legal obligations. We do not sell personal data. We do use a small, defined set of it to measure our advertising, and we will not blur the line. Purchases: when an order placed on this website is paid, we send Meta a server-side Purchase event with the order number, the plan's name and destination, the amount and currency, the address of the page where the purchase was completed and your browser's user agent. If you accepted measurement, the event may also include your email address and customer id in hashed form, your IP address, the advert click id and the Meta pixel cookies, so Meta can match the sale to the advert; if you declined or have not answered, it includes none of these. A copy of the same purchase goes to Google Analytics, with your browser's analytics ids, only if you accepted. Whatever you answer when the app asks whether it may share your phone's advertising ID with Meta and Google, our server tells Meta when an order placed in the app is paid and, unless you say yes, once that the app was installed, with the amount, currency, plan and order number, your answer and basic details about the app and phone (for an Android install, the store link it came from), but never your name, email, phone number or advertising ID. If you say yes, Meta's software in the app also reports the install, app opens, your sign-up and each paid order with the phone's advertising ID and a random ID for this installation, and Google Firebase in the app reads the advertising ID too; on an iPhone the advertising ID is read only if you also allow tracking when Apple asks. The app also reports its installation and each purchase to Firebase (Google Analytics) and through it to Google Ads, again without your name or email. Installs: the install source the app reads on first launch (section 1) is stored with your account and copied onto your orders, so a sale can be credited to the advert that brought it; the tagged-link note from this website is treated the same way. If you decline the consent bar, the measurement cookies are not written and no hashed identity leaves this site; the app's events are never tied to a name either way.
3. Payments and Stripe
All payments are processed by Stripe, our payment provider, using the credit or debit card, Google Pay or Apple Pay method you choose in the app. Your card details go to Stripe directly — we never see or store a full card number, and we cannot charge your card outside that checkout. What comes back to us is the confirmation and the order record we need to deliver your plan, issue an invoice and handle a refund if one is due. Stripe handles the payment data it collects under its own privacy terms.
4. Who we share data with
We share data with the providers we need to run the service, and only as much as each one needs to do its part: Stripe for payments, the eSIM and connectivity providers who provision your profile and carry your data at the destination, and Cloudflare, which hosts the site and our services. Each of them may use the data only to provide that service to us, and none of them may use it for their own marketing. Google and Meta are different. For the measurement cookies and pixel on this website, we and each of them are joint controllers of the collection and transmission of that data — the Court of Justice of the EU decided this for embedded pixels in Fashion ID (C-40/17) — which is why we ask before any of it starts; what they do with the data afterwards, including advertising on their own platforms, they do as independent controllers under their own terms. The purchase and install events described in section 2 go to Meta and to Google (Firebase) on the same footing. Where a provider processes data outside the European Economic Area, we rely on the transfer safeguards the law requires.
5. How long we keep it, and how we protect it
We keep personal data only as long as the purposes above require, and then delete it. Invoicing and tax records are the exception: the law requires us to keep them for a set retention period, and we use them for nothing else in the meantime. The advertising identifiers have their own clocks. The tagged-link note in your browser expires after the period shown in the table. The install source and click ids copied onto your account and orders stay with the order record for as long as the order itself. The log of app-store badge taps on our link service holds the click id, the campaign parameters, your consent answer, the store you were sent to and the device type, browser family and country of the tap — no name, email or IP address. Each purchase or install event we send to an advertising platform is logged once, without the identity it carried, so that we can show what was sent. Access is limited to the people who need it, data is protected in transit, and we work only with providers who can meet the same standard. No system is perfect, and if a breach ever put your data at real risk we would notify you and the competent authority as the law requires.
6. Your rights, including deleting everything
If you are in the EU, the GDPR gives you the right to access your data, correct it, delete it, take a copy elsewhere, and object to or restrict what we do with it; in Türkiye, KVKK gives you comparable rights, and we handle both kinds of request the same way. The fastest route to deletion is inside the app: Account, then Delete account, sends a deletion request, and your account and personal data are permanently deleted within 30 days — you can cancel the request from the app during that window. You can also write to support@balkanesim.app or open the WhatsApp chat on the app’s Support screen, and we will answer within the time limit the law sets. If you think we have handled your data badly, you can complain to the Estonian Data Protection Inspectorate or to the supervisory authority where you live.
7. Contact
BILPP OÜ, registered in Tallinn, Estonia, is responsible for the personal data described in this policy. For any privacy question or request, email support@balkanesim.app or start a WhatsApp chat from the Support screen in the app. Please tell us the email address you used for your order, so we can find the right record and answer properly rather than asking you twice.
Ad measurement (Meta and Google)
We measure which of our adverts lead to an install or a purchase. For that we share data with third parties — Meta Platforms Ireland Limited and Google. With your agreement, this includes:
- In the app: your phone's advertising ID and your activity in the app with Meta and Google (on an iPhone the advertising ID only if you also allow tracking when Apple asks), plus a random ID for this installation with Meta. Google may use them to measure our adverts, never to personalise the ads you see.
- On this website: cookies from Google and Meta, set only after you choose “Accept all”.
Meta uses this data to provide measurement services and to target and deliver ads. How Google uses it is explained here: https://business.safety.google/privacy/
You can say no, or change your answer at any time — in the app under Account → Privacy & legal, and on this website with “Cookie choice” at the bottom of every page. If you say no, Meta still hears from us when the app is installed and when an order is paid, but without your name, email or advertising ID. The app and the website work the same either way.
Cookies and browser storage
| Cookie | Set by | What it does | Lasts |
|---|---|---|---|
| _ga | Tells one browser apart from another so a visit is not counted twice. | 24 months | |
| _ga_* | Holds the state of your current visit for one Google Analytics property. | 24 months | |
| _gcl_au | Records that an advert brought you here, so a later install can be attributed to it. | 3 months | |
| _gcl_aw | Holds the Google Ads click id (gclid) from the link that brought you here, so a later purchase or install can be credited to that advert. | 3 months | |
| _gcl_ls browser storage, not a cookie | Google's own copy of that click id, kept in browser storage beside the cookie. | 3 months | |
| test_cookie | Set by Google on doubleclick.net for minutes, to check whether your browser accepts third-party cookies. | This visit only | |
| _fbp | Meta | Meta’s equivalent: links a page view or app-store tap back to an advert. | 3 months |
| _fbc | Meta | Holds the Meta click id (fbclid) from the link that brought you here, for the same reason. | 3 months |
| lastExternalReferrer browser storage, not a cookie | Meta | Meta's note of the site that referred you here and when, so a click on a Meta advert can be recognised on a later visit. | Until you clear it |
| lastExternalReferrerTime browser storage, not a cookie | Meta | Meta's note of the site that referred you here and when, so a click on a Meta advert can be recognised on a later visit. | Until you clear it |
| multiFbc browser storage, not a cookie | Meta | Meta's list of click ids seen in this browser, in case more than one advert was clicked. | Until you clear it |
| consent-v1 browser storage, not a cookie | BILPP OÜ | Your answer to the consent bar, so the site does not ask again and the tags know what you chose. | Until you clear it |
| stg_attr browser storage, not a cookie | BILPP OÜ | Our own note of the advert-tagged link you arrived on — campaign name and click ids only, never your name or email. Written before you answer the consent bar; leaves your browser only with an order placed here or a tap on one of our app-store badges. | 3 months |
| sim_ref browser storage, not a cookie | BILPP OÜ | Our own note of a referral code (the ?ref= in a link you arrived on), kept 30 days so the person who referred you is credited if you buy. No personal data. | 1 months |
| gift_device browser storage, not a cookie | BILPP OÜ | Our own random id for this browser, written when you claim a gift eSIM from a venue's QR code, so the same gift cannot be claimed over and over from one browser. No name or email. | Until you clear it |
Decline and none of the cookies above are written; the site works exactly the same. The browser-storage entries marked as ours hold no name or email and are kept either way — section 1 says what they do.
Cookie list checked September 25, 2026.