Privacy Policy

1. General Information

Website Name: TLV Flights

Operator and Database Owner: Digital Point, micro-business no. 204269369

Address: Herzl 14, Kiryat Ekron, Israel

Contact: contact@tlvflights.com | WhatsApp +972 55-947-4565

Website URL: www.tlvflights.com

Website Purpose: Providing real-time information on arrivals and departures at Ben Gurion Airport (TLV), cargo tracking (AWB), airline information, courier tracking (DHL, FedEx, UPS, etc.), cargo terminals, and ground handling services, as well as an online store for travel eSIM data packages.

Scope: This policy covers the website www.tlvflights.com and our "TLV Flights" apps for Android and iPhone (com.tlvflights.app). What the Android app collects is listed in section 2.6, and what the iPhone app collects in section 2.7. In both it is less than what the website collects.

2. What Information Do We Collect?

We collect information in a limited manner and only for purposes essential to operating the website. Here are the types of information we collect:

2.1 Automatically Collected Usage Information

• Search Queries: Flight numbers, destinations, airline names, AWB (Air Waybill) numbers, and courier tracking numbers you enter on the site
• IP Address: Your computer or device's internet address (for security and geographic analysis purposes)
• Device Information: Browser type, operating system, screen size, device language
• Behavioral Data: Pages visited, time spent on pages, links clicked, entry and exit times
• Language Preferences: Choice between Hebrew and English

2.2 Information Collected Through Forms and Notification Signup

• Contact Form: Name, email address, message content
• Flight Notification Signup: A random device identifier generated by your browser (required to deliver push notifications; not derived from any identifying detail), the flight you selected, the notification types you requested, and your preferred notification language. If you answered the marketing question on the form, your answer is stored alongside this identifier together with its time and IP address, as described under Marketing consent below
• Email Notifications: Email address (only if you asked to receive alerts by email as well)
• Telegram Notifications: Your Telegram chat identifier (only if you chose to connect your Telegram account for alerts)
• Marketing consent (optional): The question is asked in one place only - the notification signup form on the website, as a separate checkbox that is never ticked in advance, where you may ask to also receive tips and offers ahead of your flight (by email or Telegram, depending on the contact detail you provided). The Telegram bot does not ask the question - it only carries across the answer you gave on the form. How your answer is stored: when you submit the form (or continue from it to the Telegram bot), the answer you marked - yes or no - is stored together with the time it was given and the IP address it was given from, linked to your device identifier. This is kept as evidence that consent was, or was not, given, as required by section 30A of the Israeli Communications Law, and is deleted automatically after 12 months if you did not actually join the marketing list. If you answered yes, we store on a separate list from the operational alert list the contact detail we can reach you through - your email address, your Telegram chat identifier (if you continued to the bot), or both - together with the consent evidence above and, where it can be told, the type of phone the consent was given from - one word, Android or iPhone, as your browser reports it at that moment. It is kept so that an offer available on one kind of phone only (for example, an offer in the Android app) is sent only to people who can use it. We do not store the full browser string, and when consent was given from a computer nothing is stored. If you answered no, we record only that refusal, so that we do not ask you again. Without explicit consent we send you no marketing at all, on any channel. You may withdraw at any time - via the unsubscribe link in every message, with the /stopoffers command in the Telegram bot, or by contacting us - and withdrawing does not affect the flight alerts you signed up for.

2.3 Information Collected When Purchasing in the eSIM Store

If you purchase an eSIM package in the store on this site, we collect the details needed to process, deliver and support your order:

• Order details: Name, email address, phone number, the destination and package you selected, and the device model you specified (for compatibility checking)
• Device kind: One word - iPhone or Android - as your browser reports it when you order, stored with the order. Support needs it: the Settings path differs entirely between the two, so without it any instruction we send you may be for a different phone. We do not store your full browser string, which is a unique identifier, only the kind of system; when it cannot be determined, nothing is stored
• Flight details: Flight number and date - only if you chose to provide them (for a pre-flight installation reminder)
• Delivery and usage data: The eSIM profile issued to you (the QR code, the identifier of the line issued to you (ICCID) and the supplier's order identifier) and the installation/activation status and data usage as reported by the supplier's network - in order to display them to you on your order page and for support
• The plan's handling log: For each order we keep a record of what was done with it through our server: when the app or the order page asked for the plan's status, whether the server answered that 80% of the data was used or that it ran out, whether the list for adding data was opened (and whether from the app's notification), attempts to pay for added data, and which of them were refused and why (for example, the store terms not accepted or an email address missing). For each action we keep the time, how many times it happened and one word on where it came from - the Android app, the iPhone app or the website. It exists to spot a customer who got stuck on the way to adding data and to help them. It is linked to the order only and does not include an IP address, a device identifier or anything you typed
• Payment reference: The transaction identifier at the payment processor - without any credit card details (see section 5.7)
• Marketing messages: During checkout in the store we do not ask for and do not collect marketing consent, and a purchase does not add you to any mailing list. The messages you receive following a purchase are operational only (package delivery, receipt, and an installation reminder if you provided flight details)

2.4 Measuring Use of the eSIM Store

So that we know which destinations are in demand, where in the purchase people run into trouble and which phone models get checked, we measure use of the store with our own system, on our own servers, with no third-party provider. This measurement does not identify you:

• A random identifier: your browser generates a random number and keeps it locally, so that one visit counts as one visit. It is not derived from you, from your device or from any identifying detail, and it is not linked to your name or email address
• The steps you took: which screens you saw, which plans you tapped and where you stopped
• What you searched for in the store: the destination search term and the phone model you typed into the compatibility checker
• Technical context: device type (mobile/tablet/desktop), page language, the page address without anything after the question mark, and the referring site's host name only

This measurement stores no IP address, no name, no email address and no phone number. On your private order page the address is truncated before it is stored, so the code that opens your order is never saved. The data is deleted automatically after 12 months. If you would rather not be measured, switch "Measurement" off in the Cookie Settings dialog (linked at the bottom of the site, and from the cookie notice shown on your first visit), and nothing at all will be collected.

2.5 Information We Do NOT Collect

It's important to note that we do NOT collect:

• ID or passport numbers
• Credit card details - payment in the eSIM store is handled entirely on a secure payment page of an external payment processor; card details never pass through our servers and we cannot see or store them
• Medical or sensitive personal information
• Precise GPS location data (only general geographic location from IP address)

2.6 Information Collected by the Android App

The "TLV Flights" Android app shows the same flight board as the website. It has no signup and it never asks you for a name or a phone number. Versions of the app that ask for it offer signing in with a Google or Apple account, entirely optional, used for one thing only - asking for the eSIM gift - and the rest of the app works without it. In versions that do not ask for a sign-in, the gift is requested without one. An email address is needed only where you choose it - buying an eSIM package in the app, a paid top-up (when the plan has no address, to send the receipt), recovering the link to an eSIM order you already placed, and asking for the eSIM gift with a sign-in - as described below. This is everything the app sends us:

• A pseudonymous device identifier (device_id): a random value generated on the device itself. It is not derived from your device, from your Google account or from any identifying detail, and it is not linked to a name or an email address, except through the link to an eSIM order described below
• A notification identifier (FCM token): the identifier Google's notification service issues for your device; without it a push notification cannot be delivered. It reaches us only after you allow notifications
• The details of each flight you chose to follow: the flight number, its date and its scheduled time (the time is needed to tell apart two different flights carrying the same number on the same day), the update types you asked for, the notification language, and a marker that the request came from the app
• The access token of your eSIM order: only if you made a purchase and opened its order link in the app. The token carried by that link is stored on the device and sent to us with every request, so that we can show you the state of your package, the data you have left and its expiry date. It grants nothing beyond that one order - exactly like the link itself - and you can remove it from the screen at any moment
• The link between the device and an eSIM order: when an eSIM plan is saved in the app, the app tells us that the device (by its pseudonymous identifier) holds that order, and so does a request for the 1GB gift. The link is used only so that we can send that device a service message about the plan, for example when we noticed unusually heavy data use. Such a message is written by a person on our side, and we keep its text, when it was sent and whether the notification service accepted it. Through the order the link also touches the details you gave when buying, such as your email address. On Android it carries no automatic data alerts from the server: those are raised on the phone itself. The link is deleted when the plan is removed from the app, by the delete-data action, and automatically 120 days after it was made
• The details of an eSIM purchase made in the app: the destination and package you picked, how many lines you ordered, the email address the package and the receipt are sent to, your acceptance of the store terms as you ticked it (kept as the record of that consent), and an identifier of the screen the purchase started from, used only to measure the funnel. We also receive the payment method you chose (card or Bit), to open the matching payment page. If you came back from the payment page to continue an order that has not been paid yet, the app also sends the open order's number and its resume identifier, which our server gave the app during that same purchase, so that the same order continues instead of a new one being opened. We also receive your device model as the manufacturer records it (for example SM-A546B), to check that the model supports eSIM; it does not identify you and carries no phone number or hardware identifier. Card details are entered on the payment provider's secure page only (section 5.7) and never pass through the app. Sections 2.3 and 2.4 apply to the order itself
• An email address (entirely optional): only if you asked the app to send you the link to an existing eSIM order again. The address is used to find that order and to send that one email, and this request adds you to no mailing list
• Signing in with a Google or Apple account (only if you asked for the eSIM gift in a version that asks for a sign-in): the identity provider gives us an email address and a permanent account identifier. We never receive or store a password. The email address is used to send you the eSIM and to restore your order if the app is reinstalled, and to check that no eSIM was bought with it before, because the gift is for people who have not bought one yet. The request also sends the destination you picked for the gift and your device model
• A device identifier, to prevent repeat claims (only if you asked for the eSIM gift): the gift is given once per device, and to someone who signed in for it, also once per account. To enforce that we store a one-way fingerprint (hash) of the device identifier, and of the account identifier if you signed in. A gift received without signing in is not sent by email and lives in the app only. The original values are not stored and cannot be recovered from the fingerprint. To confirm that the request comes from the app installed from Google Play, on a phone that has not been modified, it also carries an integrity confirmation from Google Play (Play Integrity): Google Play checks the app and the device and gives us a signed answer that says only whether the app is genuine and whether the device passes Android's integrity checks. We verify that answer with Google and do not store it
• One reminder if the gift was not installed (only if you asked for the eSIM gift): with the gift request the app also sends the pseudonymous identifier under which the device's notification identifier is kept, so that we can send the phone one reminder if the eSIM has still not been installed about 3 hours later. The link between the gift and that identifier is kept on our own server and deleted after 60 days
• A summary of the eSIM check on your phone: when an eSIM plan is saved in the app, the app checks on the phone whether the line you bought is set up correctly - on the eSIM screen, and also in the data-usage check that already runs in the background (see below). The first time the check manages to read the line, when it finds a fault abroad (and once more when the fault clears), or when you tap on the eSIM screen to contact us, the app sends us a short summary of it: whether the eSIM is switched on, whether data roaming is on, whether data is set to go through it and whether its mobile data switch is on, whether airplane mode is on, the network generation (2G, 3G, 4G or 5G), whether the internet gets through it according to the phone's own check, your device model, the Android version, the app version and the time of the check. The summary is linked to your order and is used only to help you when something is not working. It does not include your phone number, the name of the network or the country you are in, your location, or any identifier of the device or of its SIM cards. It is kept for 90 days and then deleted automatically. The background check is not a separate check: it runs together with the data-usage check, roughly every two hours, and reads only what the phone keeps in its memory, without the internet. If, abroad, it finds a switch that needs turning on - data roaming, mobile data itself, or the line chosen for data - it shows you one notification about it, which opens the eSIM screen
• An anonymous report about the gift screen (only while the eSIM gift is offered to you): so that we can see where people stop on the way to the gift, the app reports the steps themselves: that the offer was shown, that the gift screen was opened and from where, the destination you picked for the gift, that you tapped the claim button, and if it stopped - at which step and why (for example, there is no connection, or the Google sign-in window was closed in a version that asks for a sign-in). The report carries a random session identifier that is created afresh every time the app is opened, is never stored on the device and is gone when the app closes - so that several steps of one visit are counted as one person rather than several. It does not include a name, an email address, a device or account identifier, your location, your device model, or anything you typed: a search in the destination box is not sent, only a destination you picked from our own list
• An anonymous report about the eSIM install screen: so that we can see whether the install ever opened on the phone, the app reports that the screen was shown, and what the operating system answered when you tapped the install button: that Android's "Add eSIM" screen opened, that the SIM settings opened and the activation code was copied to the clipboard, or that nothing opened at all - and in that case also whether the phone does not support eSIM. The report carries which line of your own order it was (a serial number inside your order, which says nothing about you), the app version, and the same random session identifier. It does not include the order reference, an email address, the card identifier (ICCID), the install code, your device model or a device identifier
• An anonymous report about the eSIM store: so that we can see where people stop on the way to a purchase, the app reports the steps themselves: that the eSIM store or the offer on a flight screen was shown, that a destination's screen was opened, the destination and package you picked, that the details screen opened or that you went back to the list of packages, that you tapped "Pay" and the payment method you chose (card or Bit), and, if something was missing, what was missing (an email address, or accepting the store terms), that the payment page opened or that we could not open it, and if the payment processor refused the payment - the payment processor's refusal message as it was shown to you (for example, that the card was declined). The report carries the same random session identifier, which is also sent with the order itself, so that a purchase is counted on the same path as the steps before it. It does not include the email address you typed or any other text you typed, a name, a device or account identifier, your location or your device model
• Turning the anonymous reports off: the app's settings (on iPhone, and on Android in the versions released from October 2026) have a "Send usage data" switch. On iPhone it is off until you turn it on; on Android it is on until you turn it off. When it is off, the app sends none of the anonymous reports about the steps you took (the gift screen, the install screen and the eSIM setup). What the service itself needs in order to work - following a flight, an order, an alert - carries on as before
• A taxi fare between Ben Gurion and an address (only if you use it): the flight screen can estimate the fare of a taxi from Ben Gurion to an address, or from an address to Ben Gurion. The address you type is sent to our server, and from it to Google Maps, to complete it as you type. It is sent with a random search identifier, created afresh for each search and never stored, so that Google counts the keystrokes of one search as one search. When you pick an address we send Google's identifier for the address you picked, the date and time of the ride (taken from the flight) and the direction, to work out the distance, the drive time and the fare. The address is not stored on the phone and is not linked to you, to the device identifier or to any account, and it travels in the body of the request rather than in its address, so it is not written to the technical log. So that we do not ask Google about the same route twice, we keep the street and the town, without the house number, together with the distance and the drive time, and nothing about you
• Ordinary server requests: as with any website or app, the requests the app makes to our server are written to the technical log together with the IP address they came from (see section 6.2)

What the app does not do: it collects no advertising identifier, contains no third-party analytics or advertising toolkit, and requests no access to your location, contacts, microphone, photo gallery or files. It asks for no camera permission either: photographing a document opens the system camera app, and choosing an image uses the system photo picker, which hands us the one image you picked and not your gallery. The app does ask for two permissions, each on the screen that explains why it is needed: (1) permission to send notifications; (2) the phone-state permission (READ_PHONE_STATE), entirely optional. The eSIM check described above works without it too, from information Android gives any app without a permission: which lines are switched on and which network each belongs to, which line carries your data, the mobile-data and roaming switches, the signal strength and the network generation. The permission only adds details Android gives with it alone, and serves the same purpose only: to tell you whether the line you bought is installed, switched on and set up correctly, and whether the internet gets through it. That reading happens on the device, and its results stay on the phone, except for the check summary described above. We do not read and do not store your phone number. Backup on Android: the list of flights you follow is also stored on the device itself, and it is the only thing the app puts into Google's cloud backup and into transfer to a new device, so that your follows come back after a restore. That list also holds the pseudonymous device identifier each follow was registered under with us (and a follow you cancelled before the server was told keeps the identifier it was made under). The current device identifier and the notification identifier are not backed up: after a restore the app creates a new identifier and registers your follows with us again under it, so that two identities never believe they are the same person.

The travel documents you save in the app: the "My documents" screen lets you keep a photo of your passport, your boarding pass or any other document so that it is available with no signal. Those pictures stay on your device and are never sent to us or to anyone else - there is no upload, no sync and no copy on any server. They are held in the app's private storage, encrypted with a key generated inside the device's security hardware, and excluded from cloud backup and from transfer to a new device; the list of document names is encrypted too. The app has no action that shares or sends a saved document. Each document can be deleted on its own, and the delete-data action in settings erases all of them.

The eSIM store in the app: the eSIM tab shows the destinations and their prices, and the purchase itself happens on a screen of the app - you pick a package, enter an email address and accept the store terms, as described in the purchase item above. Only the payment step opens the payment provider's secure page in an embedded browser window, and the card details are given there and not in the app. Sections 2.3 and 2.4 of this policy apply to the order. If you bought a package and opened its order link in the app, that same tab shows your package from then on - its status, the data you have left, its expiry date and an install button - using the access token listed above. A top-up starts here too: the app sends us the package code you picked and the payment method you chose (card or Bit) and, on an order carrying more than one line, which line of your order the top-up is for - a position within your own order that says nothing about you (the price is always ours to set and never the device's), and we return a payment page that again opens in the embedded browser. The token is stored on the device, and can be removed from the screen at any moment. On Android it is excluded from cloud backup; for the iPhone see section 2.7.

Deletion: the app's settings screen has a delete-data action, which cancels all of your follows on the server and erases the identifier from the device. The same deletion can be requested at the app data deletion page, without installing anything. What is kept even after you delete: if you received the eSIM gift, the record that a particular device or account has already received it is kept even after you delete your account or your data. The record holds a one-way fingerprint only. It contains no name, no email address and no identifier that can be recovered, and it is needed to stop a one-time offer being claimed again - without it, deletion itself becomes the way to get a second gift.

2.7 Information Collected by the iPhone App

The "TLV Flights" iPhone app is built from the same code as the Android app and shows the same flight board. It has no signup and no sign-in of any kind, and it never asks you for a name or a phone number. It sends us the information listed in section 2.6, with the following differences only:

• The notification identifier: on an iPhone, notifications are sent by our server directly to Apple's notification service, so the notification identifier sent to us is the identifier Apple issues for the device, not a Google one. It reaches us only after you allow notifications, together with a marker that the device is an iPhone. See also section 5.8
• The live flight card (Live Activity): to show a live card on your Lock Screen for a flight you follow, the app sends us two kinds of identifier issued by Apple: one that lets our server show such a card on the device, and, for every card shown, its own update identifier together with the flight it shows. With them the server shows the card about six hours before a flight you follow, updates it when the time, status, terminal or counters change, and removes it about an hour after take-off or landing. Live cards for the app can be switched off in the iPhone's settings
• Data plan alerts: the iPhone's operating system does not let an app measure data use, so when an eSIM plan is saved in the app, the app tells us that the device (by its pseudonymous identifier) holds that order. With that link our server checks with the eSIM supplier how much data was used and sends that device an alert when 80% is used, when the data runs out, or when the eSIM has not been set up yet. The same link is also used to send a service message about the plan, as set out in section 2.6. The link is deleted when the plan is removed from the app, when it expires, or by the delete-data action
• The reminder before a flight: on Android the reminder five hours before a departure is created on the phone itself. On an iPhone it is sent by our server, from the flights you follow and the notification identifier, and needs no further information
• The device model when buying an eSIM: on an iPhone the app sends the identifier Apple uses for the model (for example iPhone15,2), for exactly the same purpose: checking that the model supports eSIM. It does not identify you and carries no phone number or hardware identifier
• The anonymous report about the eSIM screens: on an iPhone the install opens Apple's install link, so the report says that the screen was shown and whether the link opened, instead of the Android answers listed in section 2.6. Everything else said there applies as written, including what the report does not include
• The 1GB gift: on an iPhone, when you claim the gift, the app sends, instead of Google Play's integrity confirmation, Apple's confirmation that the request comes from our app on a real iPhone (App Attest): a key created in the phone's secure chip, Apple's attestation of it and the key's identifier, together with a one-time Apple token (DeviceCheck). With that token our server asks Apple whether this device has already received a gift, and marks it with Apple once the gift is delivered. That mark is kept by Apple, not by us; we keep only a fingerprint of the device identifier (as on Android) and a fingerprint of the key identifier for two days, so the same attestation cannot be used twice. There is no sign-in and no email for the gift. The device identifier sent with a gift claim is kept in the phone's Keychain, and stays there after the app is deleted and after the delete-data action, so that a gift you already received comes back to you after a reinstall. It does not move to another iPhone
• Backup on iPhone: what the app stores on the phone, including the list of flights you follow, the pseudonymous device identifier and the access token to your eSIM orders, is included in the iPhone's backup (iCloud or a computer backup) and in transfer to a new iPhone, like the data of most apps. So an iPhone restored from such a backup keeps showing your eSIM orders and lets you manage them, as the original phone did. That backup is kept by Apple under your own settings, not by us, and the travel documents are excluded from it (see below)
• What the iPhone app does not send: it has no sign-in of any kind. The iPhone's operating system does not let an app read whether the eSIM is switched on, whether data roaming is on or which line is carrying your data, so there is no iPhone permission that corresponds to READ_PHONE_STATE and no check summary. Instead, the eSIM screen shows what the eSIM supplier reports to us about the line (whether it is switched on in the phone and whether it has connected yet), and before it shows a fix, the phone checks whether the internet gets through the cellular network with a short connection to our own site. That check sends us no information, and its result stays on the phone.

Travel documents on iPhone: the pictures you save on the "My documents" screen are kept in the app's private storage under iOS file protection at its strongest class, which makes them unreadable while the phone is locked. They are excluded from iCloud backup and from transfer to a new iPhone, and are never sent to us or to anyone else. The screen opens only with Face ID or the phone's passcode, and the delete-data action deletes them.

Permissions on iPhone: the app asks for three permissions, each only at the moment it is needed: (1) to send notifications, when you first tap a bell; (2) camera access, only when you photograph a travel document on the "My documents" screen; (3) Face ID, to open the saved documents. Choosing an image uses the system photo picker, which hands the app only the image you picked, so the app has no access to your photo library. It asks for no access to your location, contacts or microphone. The app does not track you across other companies' apps and websites and does not access Apple's advertising identifier.

Deletion: as on Android: the delete-data action in the app's settings, which on the server also deletes the live flight card identifiers and the data plan links, or the app data deletion page, without installing anything.

3. How Do We Use Your Information?

The information we collect is used only for the following purposes:

4. Cookies and Tracking Technologies

Our website uses cookies and similar technologies to improve user experience. Here's an explanation of the cookies we use:

4.1 Types of Cookies We Use

• Essential Cookies: Required for basic website functionality (saving language preferences, managing sessions)
• Measurement Cookies: Google Analytics for website traffic analysis, and Microsoft Clarity for session recording (see sections 5.1 and 5.9)
• Personalised advertising cookies: we do not use them. The site shows ads, but not ads tailored to you from your prior visits to other websites, and there is nowhere on the site that can switch that on (see section 5.2)
• Functional Cookies: Saving your preferences (e.g., language choice, arrivals/departures view)

4.2 Consent and Cookie Management

On your first visit a cookie notice is shown, carrying a "Got it" button, a close button (×) and a link to cookie settings. The notice itself accepts nothing and refuses nothing: all three ways out of it - "Got it", the close button, and doing nothing at all (it closes by itself after about eight seconds) - simply dismiss it so it does not come back, and change nothing about what is running. There is exactly one place that switches measurement off: the "Measurement" toggle in the cookie settings dialog, reachable at any time from the link at the foot of the site. Until you turn it off there, measurement cookies - Google Analytics and Microsoft Clarity - are running, and so is our own internal measurement of the eSIM store (section 2.4), which uses no cookies and does not identify you. Personalised advertising is not part of that choice at all, because we do not use it.

Personalized advertising cookies are not loaded at all until you accept them. The block is set at the top of every page, before the first third-party tag loads, not afterwards. If you do nothing, they stay off.

Measurement cookies run by default, and dismissing the notice does not switch them off. You can switch them off at any time in the settings dialog, and back on there. Switching measurement off in the settings dialog does not merely block cookies - the measurement tools are never loaded at all: not Google Analytics, not Microsoft Clarity session recording, and not our own internal measurement. No data about your visit leaves the browser for any of them, rather than simply not being stored in a cookie.

Your choice is stored in your browser and applies to later visits too. You can change it at any time through the "Cookie Settings" link at the bottom of the site.

Visitors from the EU/EEA, the UK and Switzerland are shown Google's own consent dialog (CMP), in accordance with EU law and Google's consent policy.

In addition, you can control and delete cookies at any time through your browser settings. Please note that blocking certain cookies may affect website functionality.

• Chrome: Settings → Privacy and Security → Cookies and Site Data
• Firefox: Options → Privacy & Security → Cookies and Site Data
• Safari: Preferences → Privacy → Manage Website Data
• Edge: Settings → Cookies and Site Permissions

5. Third-Party Services

Our website uses third-party services for various purposes. Here's a full breakdown:

5.1 Google Analytics

We use Google Analytics to analyze website traffic and performance. This service collects anonymous information about visitors, including:

• Number of unique visitors
• Pages viewed and duration
• Traffic sources (Google, direct links, social media)
• General demographic information (country, city, language)

How to Opt-Out: You can switch "Measurement" off in the Cookie Settings dialog (see section 4.2), or install the Google Analytics Opt-out Browser Add-on.

5.2 Advertising

The site displays ads via Google AdSense, which is one of the ways we fund its operation. Important to know:

• Ads are shown against the content of the page you are reading, not against who you are or which other sites you have visited
• We do not ask Google for personalised advertising, and we declare that to it on every page load
• We do not pass identifying personal information you gave us (such as name or email) to advertising vendors

The decision: we gave up personalised advertising. The ads on this site are tailored to nobody, and there is no way to turn that on.

There is nothing here to opt out of, but for completeness: you can manage personalised advertising across the web via Google Ads Settings or at www.aboutads.info.

5.3 Affiliate Links

The site currently carries no live affiliate links. The eSIM offers you see are our own store (see section 2.3), not a referral to an external provider.

If we display affiliate links to external services in the future they will be marked as such: if you click one and purchase a service, we receive a commission from the provider at no extra cost to you. Such a link carries an anonymous attribution identifier only, letting the provider know you arrived from our site, and we pass it no personal information about you. Once you move to an external provider's site, its own privacy policy applies.

5.4 Airline and Courier APIs

When you search for flight, cargo, or shipment information, our website communicates with external APIs from:

• Airlines: El Al, Wizz Air, Ryanair, Turkish Airlines, Lufthansa, British Airways, easyJet, and more (78+ airlines)
• Couriers: DHL, FedEx, UPS, TNT, Aramex, and more

We do not share your personal information with these services. Only tracking or flight numbers are sent to retrieve public information.

5.5 Progressive Web App (PWA) and Notifications

Our website offers PWA features that enable:

• Saving the website to your device's home screen
• Partial offline functionality
• Alerts about changes to a flight you selected - by push, email, or Telegram, at your choice

Important: All notification channels require you to actively sign up and give explicit consent, and you can unsubscribe at any time. Push notifications are delivered via a dedicated third-party notification provider, which stores an anonymous device identifier for this purpose; email alerts are sent via a third-party email delivery provider; Telegram alerts are delivered through the Telegram platform.

5.6 Infrastructure and Operations Providers

To operate the site we rely on third-party providers: server hosting, a secure database, email delivery, and push notification delivery. These providers process the information solely on our behalf, are bound by confidentiality, and may not use it for their own purposes.

5.7 eSIM Store: Payment Processing and the eSIM Supplier

A purchase in the eSIM store involves two additional providers:

• Licensed Israeli payment processor: Payment is taken on the processor's secure, PCI-DSS-compliant payment page. Your name, email address, phone number and the transaction details (product and amount) are passed to it in order to process the charge and issue the accounting document. Credit card details are entered directly with the processor and never reach us.
• International eSIM supplier: The package is provisioned through a wholesale eSIM supplier. It receives only the details of the purchased package and an internal order number - no name, email, phone or any other identifying detail. Use of the cellular line at your destination is also subject to the policies of the local networks it operates on.

5.8 The Android and iPhone Apps: Notifications and Distribution

On Android, notifications in the app are delivered through Google's notification service (Firebase Cloud Messaging). For that purpose we store your device's notification identifier, and we pass Google that identifier and the message itself (the flight number and the update). We pass Google no name, email address or other identifying detail, and no advertising profile is involved. Downloading and installing the app happens on Google Play and is additionally subject to Google's terms and privacy policy.

On an iPhone, notifications are sent by our server directly to Apple's notification service (Apple Push Notification service), with no Google service involved. Apple receives the device's notification identifier and the message itself (the flight number and the update, or the data plan alert), and the content of the live flight card: the flight number, destination, time, status, terminal and counters. We pass Apple no name, email address or other identifying detail. Downloading and installing the app happens on the App Store and is additionally subject to Apple's terms and privacy policy.

5.9 Microsoft Clarity

We use Microsoft Clarity to understand where people run into difficulty using the site, and in particular during checkout in the eSIM store. The tool records the course of a visit - scrolls, clicks and movement between screens - so we can watch the recording afterwards and fix what did not work. We do not pass Clarity your name, your email address or any other identifying detail you gave us; the data is stored and processed on Microsoft servers outside Israel and is also subject to Microsoft's own privacy policy.

How to Opt-Out: Switching "Measurement" off in the Cookie Settings dialog prevents the tool from loading at all - it is never fetched and records nothing.

6. Data Storage and Retention

6.1 Where Is Information Stored?

All information is stored on secure servers located in data centers with high security standards. We use reliable hosting providers that comply with international data security standards.

6.2 Data Retention Period

• Flight Alert Subscriptions: Deleted automatically once the flight has departed or landed. If you subscribed to several flights, each subscription is deleted separately at its own time
• Cargo (AWB) Alerts: Deleted when tracking of the shipment ends
• Contact Form Submissions: Not stored in any database of ours - the enquiry is delivered as an email to our service inbox, where it is kept for up to one year
• Statistical Signup Log: A record with no name and no email address (device identifier + flight number only), used to count trends. Deleted automatically after 12 months
• Your answer to the marketing question (on the device identifier): The answer, its time and the IP address it was given from are deleted automatically after 12 months, unless you actually joined the marketing list - in which case the consent evidence moves to your consent record
• The marketing list: Your consent record is kept for as long as you are on the list. After you withdraw, the record is not deleted but marked as withdrawn, and is kept as proof that you asked us to stop (this is how we make sure you are never re-added and never sent another message); you may request its full deletion by contacting us
• Google Analytics Data: As configured on our account - event data is retained for two months and user data for 14 months
• eSIM Store Usage Measurement: Records with no name, no email address and no IP address (a browser-generated random identifier + the step taken). Deleted automatically after 12 months
• The App's eSIM Check Summary: Kept for 90 days from receipt and then deleted automatically. It is linked to the order only, not to the device identifier
• The eSIM Plan's Handling Log: Each record is deleted automatically 90 days after the last time its action happened. It is linked to the order only
• The Live Flight Card Identifiers and the Reminder Record (iPhone): The identifier that lets a live card be shown on the device is kept while you are using the app. Each card's update identifier, and the record of reminders already sent before a flight (so none is sent twice), are deleted automatically 14 days later. The delete-data action deletes all of them at once
• The App's Device Identifier and Notification Identifier: Retained while you are using the app. The delete-data action in the app's settings erases them immediately, together with every active follow. Uninstalling the app erases the identifier from the device itself, and the record held by us can be deleted at the app data deletion page
• The eSIM Gift Record: a one-way fingerprint of the device identifier that already received the gift, and of the account identifier if you signed in for it, together with the order reference. Kept even after a deletion request, as explained in section 2.6, so that a one-time offer cannot be claimed twice. It holds no name, no email address and no identifier that can be recovered
• The link between the device and an eSIM order, and the messages sent: the link is deleted when the plan is removed from the app, by the delete-data action, and automatically 120 days after it was made. Service messages that were sent are deleted 90 days after sending
• The gift reminder link: the gift's order reference and the pseudonymous identifier the reminder is sent to, as explained in section 2.6. Deleted after 60 days
• Server Technical Logs: Rotated and overwritten automatically by volume; they are not archived long term
• Cookies: Google's measurement cookie expires after 400 days (about 13 months) and the browser deletes it then. You can delete cookies earlier through your browser settings, or keep them from being set at all in the Cookie Settings dialog
• eSIM Store Orders: The order record is retained for the package's validity period and afterwards for support purposes; accounting documents (receipts) are retained as required by Israeli tax and bookkeeping law (up to 7 years), so we cannot delete them before that period ends even at your request

Beyond these periods, you may ask us at any time to delete information we hold about you. We will do so unless the law requires us to keep it (accounting documents, for example), or unless it is the eSIM gift record above, which is a one-way fingerprint only and is kept so that deletion itself cannot become the way to claim the gift a second time.

7. Information Security

We implement advanced security measures to protect your information:

• SSL/TLS Encryption: All communication with the website is encrypted using SSL certificate (green lock in browser)
• Firewalls: Protection against cyber attacks and intrusions
• Regular Backups: Automatic system backups in case of technical failures
• Continuous Security Monitoring: Tracking suspicious activity and taking immediate action
• Access Restrictions: Only authorized system administrators can access data

8. Sharing Information with Third Parties

We do NOT sell or rent your personal information to third parties. Please note: the site displays ads and contains affiliate links as detailed in section 5 - in that context, advertising vendors use cookies in your browser, but we do not pass them identifying personal information you gave us. In addition, we may share information in the following cases:

• Legal Requirements: If required by law, court order, or legal process
• Protecting Our Rights: In case of violation of terms of use or suspected illegal activity
• Service Providers: Sharing minimal information with technical service providers (server hosting, database, email delivery, notification delivery, analytics) who are bound by confidentiality
• Business Sale: In case of merger, acquisition, or sale of the website, information may be transferred to the acquiring party

9. Your Rights Under the Law

In accordance with Israeli Privacy Law and GDPR (if applicable), you have the following rights:

9.1 How to Exercise Your Rights?

To exercise your rights, please contact us through the contact page on our website. We will respond to your request within 30 days of receipt.

10. Children's Privacy

Our website is not intended for children under 13. We do not knowingly collect personal information from minors. If you are a parent or guardian and discover that your child has provided us with personal information, please contact us and we will delete the information immediately.

11. Changes to Privacy Policy

We reserve the right to update this privacy policy from time to time. Any material changes will be posted on this page with the update date indicated. We recommend visiting this page periodically to stay informed of changes.

12. International Data Transfers

Some of our providers - database hosting and notification delivery, as well as the measurement tools from Google and Microsoft - store and process data on servers located outside Israel. Such transfers are made in accordance with the Israeli Privacy Protection Regulations (Transfer of Data to Databases Abroad), 2001 - where the destination country ensures an adequate level of protection, or under a contractual undertaking by the provider to protect the data at a level consistent with Israeli law. In all cases, we ensure the information is protected in accordance with this privacy policy.

13. Contact and Inquiries

For any questions, requests, or complaints regarding privacy and your personal information, you are welcome to contact us:

13.1 Privacy Protection Authority (Israel)

If you believe your privacy rights have been violated, you can file a complaint with the Privacy Protection Authority:

• Website: gov.il - Privacy Protection Authority
• Submitting an enquiry or complaint: public inquiries form
• Email: ppa@justice.gov.il

The Authority publishes its current contact details on its own website; those should be relied on.

14. Consent to Policy

Using the TLV Flights website constitutes consent to this privacy policy. If you do not agree to the terms outlined here, please refrain from using the website.