Lachez

Privacy Policy

Effective from 17 November 2026

Česká verze

Lachez is a tracking service for hot air balloon events. During a flight, the pilot shares the position of their balloon so that the ground crew can locate the landing site and spectators can follow the flight on a map. This policy describes what personal data is processed about the pilot and how it is handled.

1. Data controller

Colegio Solutions s.r.o., company identification number (IČO) 24792161, registered office at Na Paloučku 21, 250 84 Sibřina, Czech Republic.
Contact address for data protection matters: info@lachez.eu

2. Data we process

When a pilot starts sharing their location, whether in the application or on the website, a single record is transmitted approximately every ten seconds, comprising:

ItemDescription
NameText entered by the pilot, typically the pilot's name or the name of the balloon
Balloon codeAn identifier for the balloon chosen by the pilot, for example its registration
PositionLatitude, longitude and altitude obtained from the GPS module of the mobile phone
TimeThe moment at which the record was captured
Event and flight codeIdentification of the event and flight to which the record belongs

Together with the position record, technical device data is also stored for diagnosing application errors: the application version, the operating system version, the device type (model) and a random application-installation identifier (stored with each position record). The app sends the same identifier with requests in which a pilot or crew code is entered (viewing a briefing, links, looking up an event) as protection against code guessing; for invalid code attempts the server stores it together with the IP address, and otherwise does not store it for these requests. For a pilot's private space, the type of device from which the pilot transmits is stored as well. This is not the IMEI, serial number or an advertising identifier. We do not process pilots' telephone numbers, e-mail addresses, contacts or photographs; the exception is the contacts an organiser lists in an event briefing (see section 5). If the pilot reads an event or space QR code from a photo or file, the image is processed on the phone only and is not sent anywhere; the application does not need access to the photo library for this.

If a member of the ground crew starts sharing for a chase vehicle, the vehicle name entered by the crew, the balloon the vehicle is following and, for the duration of sharing, the vehicle's position (latitude and longitude), speed, heading and time are stored.

Feedback. You may optionally add an e-mail address to a message sent from the application. We use it solely to reply to your message; it is stored for at most 180 days and then deleted. The e-mail address is not passed to third parties. Earlier deletion can be requested at info@lachez.eu.

In-app purchases. A pilot may unlock a second and a third balloon in their private space by a one-time purchase in the application. The purchase is made exclusively through the Apple App Store or Google Play; payment details (card, account) stay with the store and the operator never receives them. After the purchase, the application sends the proof of purchase issued by the store to the server, which verifies it with the store. In doing so we process: the platform (App Store / Google Play), the product identifier, the transaction identifier assigned by the store, the time of purchase, the verification result, the code of the private space the purchase belongs to, and the random identifier of the application installation. The purpose is to unlock the purchased balloon slot, to allow the purchase to be restored on a new phone and to handle complaints; the legal basis is performance of the contract (Article 6(1)(b) GDPR) and, for accounting records, compliance with a legal obligation.

3. When location is transmitted

Exclusively for the period during which the pilot activates sharing using the "Start sharing location" button, and until they end it using the "Stop sharing" button. The application requests location permission before first use; without that permission, no data is shared.

Sharing continues while the application is in the background or the phone is locked. Without this, sharing would end the moment the pilot puts the phone in a pocket. On Android devices a permanent notification is displayed throughout; on iPhone devices, the location indicator remains visible in the status bar.

If sharing runs for a long time without a flight, the application asks the pilot whether to continue: two hours after sharing started if the balloon has not yet taken off, and one hour after landing. If the pilot does not answer, the application ends sharing by itself, at the earliest six hours after the start without a take-off, or three hours after landing. During a flight, the application only asks after eight hours and never ends sharing by itself. Until then, the application continues to record the position, including any journey from the landing site. We therefore recommend ending sharing once you have landed.

4. Purpose and legal basis of processing

The purpose of processing is to support the running of a balloon event. The ground crew needs to locate the landing site, which cannot be determined in advance because it is dictated by the direction and strength of the wind. Spectators and the organiser gain an overview of the event as it unfolds.

The legal basis for processing is the legitimate interest of the organiser and the operator in running the event, comparable to a published start list or the live tracking of competitors at sporting events. Sharing a location is at the same time always voluntary and entirely at the pilot's discretion, as they activate and end it themselves.

5. Who has access to the data

  • Anyone in possession of the link to the event. The live event map is publicly accessible; the link contains the event code and is distributed by the organiser. The map displays the name, current position, altitude, speed and track of the flight.
    The display of altitude and speed can be disabled for an individual flight. A pilot may request this from the event organiser, who will hide these values. The server then does not publish them at all, including in the data from which the map is rendered.
  • Anyone to whom a pilot sends the live map link of their private space. The link from the “Share live map” button shows only the flights of that day in that space (name, position, altitude, speed and track of the flight); it does not show flights from other days, and a new link is issued for the next day.
  • The event organiser, who additionally has access to the list of flights for their event, may download the tracks in GPX format and may delete an individual flight. The organiser also sees the application version, the operating system version and the type of device from which a flight is transmitted.
  • The operator, to the extent necessary to run the service and resolve technical issues.
  • The pilot of the balloon being followed. The position of a chase vehicle is visible only to the pilot of the balloon the crew is following; the public map does not display vehicles.

Technical device data (application version, operating system and device type) is visible only to the event organiser and the operator; the public map does not display it.

Event briefing. The organiser may store a briefing with an event: contacts of people (name, telephone number and role), a QNH note and a PDF document. The briefing is shown in the app and on lachez.eu only to the event's pilots and crews who enter the pilot or crew code, and only once the event is paid; the public map and the event list do not display it. The organiser is responsible for the listed people agreeing to the publication of their contact. The app stores the briefing PDF in the app's private storage on the phone when you start sharing your position or when you tap the PDF button (only the latest version per event). The app also keeps the briefing text (contacts, QNH note) in the app's private storage on the phone each time you open the briefing, so that it can be shown even when the app cannot reach the server, including before takeoff and offline during a flight (only the latest version per event). Neither copy is included in backups. A copy on the phone is deleted as soon as the app, on its next contact with the server, finds that the briefing or the event no longer exists (at the latest the next time you start sharing or open the briefing), otherwise when the app is uninstalled; the phone may also delete it on its own when storage runs low.

Area data. If the pilot downloads the area around a take-off site in advance (“Download an area…”), or the application downloads it around their position, power lines, obstacles and terrain are stored in the application's private storage on the phone so that they work without signal. The copy is not backed up and is deleted when the application is uninstalled; the phone may also delete it by itself when storage runs low. When the data is downloaded, the Lachez server does not store who requested it or from where; to protect against overload it keeps only the IP address and the number of requests per minute, for no longer than 2 days.

Members of an organiser's team. An organiser may invite helpers (team members) to the console, either for the whole account or for a single event only. About a team member we process the e-mail address, the scope of access (account or a specific event), the dates of addition and removal, and the information on who added the member. The team member is informed of the invitation by e-mail and signs in to the console by a link sent to their own e-mail address, in the same way as the organiser. The purpose of processing is joint management of the event and securing access to the console; the legal basis is performance of the contract with the organiser and the legitimate interest of the organiser and the operator in joint management of the event and in protecting access against abuse. Data on team members is visible to the organiser and the operator; it is not shown to other team members or to the public. For an event to which they have access, a team member sees the same as the organiser, including flight data (see section 5); they do not see orders, invoices or account settings. The organiser may remove a team member at any time, and access ends immediately. A record of a removed member is kept for a further 12 months after removal for protection against abuse, and data on all team members is deleted together with the organiser’s account. A team member may ask for removal or erasure of their data by contacting the organiser or info@lachez.eu. The organiser is responsible for inviting to the team only persons who genuinely take part in preparing or running the event, and for making them aware of this policy.

We do not sell the data, we do not disclose it to advertisers or data brokers, and we do not use it for profiling.

6. Retention period

Individual recorded positions are deleted no later than 90 days after they were captured. The exception is flights that the pilot or the event organiser explicitly marks to be kept (so that the flight card, profile and track remain available); this mark can be removed at any time, after which the flight is deleted under the normal retention period.

Technical device data and chase-vehicle data, including vehicle positions, are retained for no longer than 90 days; records of invalid code attempts (the random application-installation identifier and the IP address) are retained for no longer than 1 day; for a flight marked to be kept, the flight's technical data is retained for as long as that protection applies. The list of devices of a pilot's private space (the random application-installation identifier and the device type) is deleted 90 days after the device last transmitted in the space, and always when the space is deleted.

After that period, only material from which no individual person can be identified is retained in relation to the event:

  • the name of the event, the date on which it was held, the number of balloons and flights, and the total distance flown;
  • a map image showing the shapes of the tracks, without names and without time data, trimmed to the flight itself, that is, excluding the segments before take-off and after landing.

This material serves as a record of the extent to which the Lachez service has been used.

A pilot may also request the event organiser to delete their flight at any earlier point, including during the event itself.

The event briefing (contacts, QNH note, PDF) is deleted together with the event; the organiser can edit or remove it at any time.

Records of in-app purchases (section 2, In-app purchases) are retained for as long as the purchase applies, that is while the private space exists or the purchase can be restored, and thereafter for the period required by accounting and tax regulations.

7. What the service does not use

  • User accounts, registration or passwords. The application does not require an e-mail address or a telephone number; an e-mail address can be added optionally to feedback only (see section 2).
  • Analytics or advertising tools. The application contains no Firebase, no Google Analytics and no other measurement library.
  • Cross-application or cross-site tracking, and no advertising identifiers.

8. Recipients of the data

RecipientScope of access
Active24 (hosting)Operates the server on which the data is stored. Standard operation includes technical access logs, namely the IP address, time and the address of the requested page.
OpenStreetMapThe map background is retrieved from their servers (on the live map and in the event cards on the home page and in the event list). They thereby obtain the IP address of the person viewing the map and the map area being viewed, but not the position of the balloon.
Esri (ArcGIS – World Imagery satellite images)If a user selects the “Satellite” base map on the live map, satellite imagery is retrieved from their servers (in the app and on the lachez.eu website, for pilots, crews and viewers). They thereby obtain the IP address of the device and the map area being viewed, i.e. for pilots and crews usually the approximate flight area, but not the name, the balloon code or the exact position of the balloon. With the default “Map” base map, nothing is sent to their servers.
unpkg (Cloudflare)The map rendering library is loaded from here on the website. The scope is identical, namely the IP address of the visitor to the page.
Google Play, App StoreDistribution of the application and in-app purchases. The store processes the payment as a separate controller under its own privacy policy; it passes to us only the proof of purchase (transaction and product identifier, time) for verification.
Amazon Web Services (AWS Open Data – Mapzen Terrain Tiles elevation model)The application downloads elevation model tiles from their servers for the area around the balloon and for the area the pilot downloads in advance (“Download an area…”). They thereby obtain the IP address of the phone and the area for which terrain is downloaded, i.e. the approximate take-off or flight area, but not the name, the balloon code or the position of the balloon. The Lachez server also computes terrain height along the track, using the public Open Topo Data service (Copernicus EU-DEM, SRTM); it sends it only the coordinates of terrain cells, no data about the pilot.
OSRM (public server run by FOSSGIS e.V.), Nominatim (OpenStreetMap Foundation)The Lachez server uses them to find out the crew’s driving time to the balloon by road (OSRM) and the names of the take-off and landing sites (Nominatim). While the crew is sharing its location, it sends OSRM only the coordinates of the crew car and the balloon, and it sends Nominatim only the coordinates of the take-off and landing sites (and the language in which the name should be returned). They do not receive the name, the balloon code or any other data about the pilot or the crew, and they see only the IP address of the Lachez server, not that of the user’s device.
Google (Android), Apple (iPhone) – place searchWhen the pilot searches for a take-off site in “Download an area…”, the text entered is processed by the phone operating system's search service (Google on Android, Apple Maps on iPhone) under its own privacy policy; Lachez sends it only the text entered, no area or position (Apple may itself use the approximate device location under its own policy). Lachez does not store the search text or send it to its server.

9. Rights of the data subject

Under the GDPR you have the right of access to your personal data, the right to its rectification or erasure, the right to restriction of processing, the right to data portability and the right to object to processing. You also have the right to lodge a complaint with the supervisory authority, which is the Czech Data Protection Authority, Úřad pro ochranu osobních údajů (uoou.gov.cz).

Please send your requests to info@lachez.eu. Kindly state which event and which balloon the request concerns, so that we are able to identify you within the data. We will confirm the handling of your request within 30 days.

10. Children

The service is intended for persons aged 16 and over (see the Terms of Service for Pilots, Article 1.5). Balloon position sharing is initiated by the pilot, who is the holder of a pilot licence; younger persons may use the application as crew or spectators only with the consent and under the supervision of a legal guardian. We do not collect or store information about age.

11. Changes to this policy

Should this policy be amended, the effective date stated in the header will be updated. Event organisers will be informed of any substantial changes.

The application and the website are operated by Colegio Solutions s.r.o. Individual events are created by their respective organisers, who also distribute the links to them.

Lachez Terms of Service for Pilots

made with Lachez · privacy policy · who sees what · terms for organisers · data licences · what Lachez can do