Minimal-data eSIM · QR after payment

QR after payment, no contract

Less data collected. More peace of mind.

A data-only eSIM as a second line. No long contracts — card payments are handled by Stripe and we don't keep card numbers.

Coverage·189+ destinations live

Quick pick:Czechia Croatia Italy Thailand Europe

Coverage

189+ destinations live

Available
Not supported yet
Home

Use mouse wheel to zoom, drag to pan.

How we verify reviews·Verified checkoutOrder, delivery and usage check

View legal information

Data eSIM

A data eSIM separate from your main number

A standard purchase without creating an account. Pick one-off data, Flex without commitment, or data for trips.

Data only

Data for Czechia

A data eSIM as a second line. Your main SIM with your number keeps working for calls and SMS.

A data-only second line
Your main number stays active
Buy without creating an account

Pick data for Czechia

No commitment

Flex subscription

Monthly data you can cancel anytime. No contract, no lock-in.

Renews monthly until you cancel
Cancel anytime in management
Payment handled by Stripe

Explore Flex

For trips

Data for trips

A data eSIM abroad instead of roaming. The QR code arrives by email after payment.

Coverage across countries
QR by email after payment
Your number stays as a second line

Pick data for trips

Overview

What we need from you — and what we don't

What we need

We keep the data set practical and limited so we can complete and later support the order.

email for QR delivery, receipt/invoice and order support
order details: selected package, price, currency, payment status and eSIM delivery status
technical and security records required to run the site, prevent abuse and resolve errors
diagnostic results after eSIM activation: reachability, speed estimate, latency, network status and provider usage delta where available

What we do not store

We do not turn checkout into a mobile-network registration or loyalty profile. If a field is not needed for the order, payment, delivery or required records, it stays out of checkout.

we do not require account registration for a standard purchase
we do not create a data profile to sell to third parties
we do not store payment card or wallet details; Stripe processes the payment
we do not ask for national IDs, document numbers or document photos
we do not store the content of mobile-network communication, calls, SMS or app data
public speed summaries do not contain profile, order, ICCID, QR code or precise location

Who processes data

Specialized services are used only where they have a clear role. Umami and consent-managed analytics run only after consent.

Stripe processes payment and payment confirmation
the eSIM provider creates and operates the eSIM profile for the order
the email provider delivers the QR code, confirmations and support replies
GA4 measurement and PostHog including session replay run under separate project settings; Umami runs only after analytics consent
marketing tools and server-side conversions run only after marketing consent
the mobile network processes operational data needed for connectivity, roaming and network security

Retention and accounting

We do not promise deletion before legal, accounting or security reasons have ended. At the same time, we do not keep checkout data just because it might be useful one day.

order and invoice records are kept according to legal and accounting duties
operational and security records are kept only as long as needed to resolve errors and protect the service
Umami/consent-managed analytics is processed according to consent; GA4 and PostHog run under separate project settings

Service roles

TvojeData handles checkout, support and order records; specialized services handle payment, email delivery, eSIM provisioning and optional analytics. The mobile network is a separate layer: it provides the actual connectivity.

TvojeData

Why we use it: order handling and customer support
What it typically sees: email, order, invoice details and operational records required for the service

Stripe

Why we use it: secure payment processing
What it typically sees: payment metadata, payment status and details needed to confirm the transaction

eSIM provider

Why we use it: eSIM profile creation and operation
What it typically sees: technical eSIM details, QR/activation data and profile status

Email provider

Why we use it: QR delivery and support replies
What it typically sees: email address and transactional or support email content

Analytics

Why we use it: measuring site and checkout performance
What it typically sees: product events, technical measurement data and, for PostHog, session replay according to project settings

Marketing with consent

Why we use it: purchase attribution, remarketing and enhanced conversions after marketing consent
What it typically sees: ad events, server-side conversions and, on purchase, hashed email or phone plus IP address

Mobile network

Why we use it: connectivity and roaming
What it typically sees: operational network data needed for connectivity; TvojeData does not store communication content

Automatic diagnostics

Why we use it: checking connection quality after activation and publishing aggregate speeds
What it typically sees: test result, speed estimate, latency, app version, related profile/order reference and provider usage delta; public reporting is aggregate only with at least 10 samples and 10 privacy units

Service	Why we use it	What it typically sees
TvojeData	order handling and customer support	email, order, invoice details and operational records required for the service
Stripe	secure payment processing	payment metadata, payment status and details needed to confirm the transaction
eSIM provider	eSIM profile creation and operation	technical eSIM details, QR/activation data and profile status
Email provider	QR delivery and support replies	email address and transactional or support email content
Analytics	measuring site and checkout performance	product events, technical measurement data and, for PostHog, session replay according to project settings
Marketing with consent	purchase attribution, remarketing and enhanced conversions after marketing consent	ad events, server-side conversions and, on purchase, hashed email or phone plus IP address
Mobile network	connectivity and roaming	operational network data needed for connectivity; TvojeData does not store communication content
Automatic diagnostics	checking connection quality after activation and publishing aggregate speeds	test result, speed estimate, latency, app version, related profile/order reference and provider usage delta; public reporting is aggregate only with at least 10 samples and 10 privacy units

Cookies and session replay

Essential cookies keep the site functional and secure. Umami analytics and marketing tools start according to your cookie-banner choice; PostHog session replay and GA4 measurement run under separate project settings.

td_session is used for login if you use an account; a standard eSIM purchase does not require registration
csrf_token protects forms and checkout from abuse
cookie_consent stores your analytics and marketing choice
td_attribution stores referral, affiliate or white-label tenant identifiers for contractual partner commission; we do not forward it to ad networks without marketing consent
without analytics consent we do not enable Umami; GA4 measurement and PostHog session replay run under separate project settings
PostHog session replay may capture site and checkout interactions; payment details are processed by Stripe outside our replay
Analytics consent is not marketing consent. Advertising pixels and server-side conversions for Meta, Google Ads, TikTok, Microsoft Ads or Reddit are used only after marketing consent; on purchase we may send hashed email or phone plus IP address, not passwords or eSIM content.

Operator vs e-shop

A mobile network is handled by an operator or network provider: they manage connectivity, roaming, billing and network security. TvojeData is an e-shop: we handle checkout, eSIM delivery and support. We are not the operator, we do not store the content of mobile-network communication, and we cannot control which operational records the mobile network keeps. We keep those roles separate; checkout asks only for what is needed for purchase and delivery.

FAQ

Short answers about privacy

Do I have to register to buy an eSIM?

No. You complete a standard purchase without creating an account. We mainly need an email for QR delivery and a card payment.

Do you store my payment details?

No. Stripe processes the payment; card numbers do not stay with us.

Is buying an eSIM anonymous?

No. A mobile data connection still has network and accounting records. At purchase we do not ask for ID or a national number and we do not build a profile to sell to third parties. The mobile network, however, processes operational data needed for connectivity, and we keep invoicing records as required by law.

Will I lose my number?

No. The eSIM runs as a second, data-only line. Your main SIM with your number keeps receiving calls and SMS.

Why does the app measure connection quality?

After activation, automatic tests are off by default. They run only when you explicitly enable them or start a manual test; one test usually uses up to 1 MB to separate device, location and provider issues. Public speed numbers are aggregate only, require at least 10 confirmed samples and do not include profile, order, ICCID, QR code or precise location.

Legal note

This page explains the product approach to data. It does not replace the full privacy policy or legal advice.

Continue to plans