Aerovue — Privacy Policy
In short
FlightLog keeps your flights on your phone. Where you are stays on your phone too: unless you switch on the online logbook, we never store your position. Backups you keep in the cloud are encrypted on your phone before they leave, with a key only you hold — we cannot read them. The online logbook is different, and off until you switch it on: it keeps your flights with their tracks, your routes and your aircraft on our data service, so that your phones and FlightLog on the web (app.krimsoft.net) stay in step — and we can read what is kept there.
Signing in needs an email address and nothing else — no password, no name, no payment details. There is no advertising, no analytics and no tracking, and we do not sell data. FlightLog is built to meet the EU's General Data Protection Regulation (GDPR); the same applies under the UK GDPR and Switzerland's data protection act. This policy says what leaves your phone, when, and where it goes.
Who is responsible
FlightLog is published by KrimSoft, a trade name of Omnimation BV, the Netherlands, which is the controller for the data described here. KrimSoft runs FlightLog's data service on Cloudflare: it holds accounts and their licences, passes on airspace, reporting points, NOTAMs, weather, maps and live traffic, keeps the encrypted cloud copies, keeps the online logbook of those who switch it on, and serves FlightLog on the web.
Your club's GlidingApp link runs through a service your club manages. For what happens there, and in the club's GlidingApp administration, your club is responsible.
Your position
• FlightLog uses your position on your phone: to show it on the map, to record a flight's track, and to notice a takeoff and a landing.
• By default it follows your position only while the app is open, or during a flight you set up with Go fly, until shortly after the landing. Automatic flight detection, which follows your position in the background to log a flight without Go fly, is off unless you switch it on — always, in Settings, or for one visit to an airfield when the app asks you there. A visit ends by itself once you leave the field.
• Your position is never stored by us. Where a feature needs to know roughly where you are, only a coarse square of about 50 km goes to the data service — for live traffic and for the NOTAMs around you — or the map tiles of the area on screen. These requests are answered and forgotten: the data service keeps no logs of them, and nothing in it ties them to you.
• Crew detection is the one exception: shortly after a take-off, the take-off's place and time and your track for its first minute go to the data service, so that it can tell which of your club's gliders took off with you. It answers and keeps nothing. See below.
• When you look up the places along a planned route, the route's points go to the data service, which answers and keeps nothing.
• You can withdraw location access at any time in the phone's settings. FlightLog then cannot show your position or detect flights.
What stays on your phone
• Your flights, routes, aircraft and their documents, pilot papers, the club's fleet and members, hour meter readings and your settings.
• Air pressure from the phone's barometer, for the altitude of a flight.
• Photos you take of an hour meter, a logbook page or a document.
• The club access code, your GlidingApp link and your recovery code, in the phone's secure storage.
All of this stays on your phone unless you switch on the online logbook, which keeps your flights, routes and aircraft on the data service as described below. Photos and test data stay on your phone even then.
What leaves your phone, and where it goes
• Signing in: your email address goes to the data service, which mails you a six-digit code through Resend. The address, the model name of the device you signed in on, your plan and when you last used the app are kept; the code never is, only what it hashes to. We can see these account details, to look after licences. They hold no location and no IP address.
• The cloud copy: flights, routes and backups are encrypted on your phone (AES-256-GCM) with a key made from your recovery code, and kept in the data service (Cloudflare R2). The key never leaves your phone; without it nobody — not us, not Cloudflare — can read them. They are filed under a one-way hash, not under your name. You can erase the whole copy from the app.
• The online logbook, only when you switch it on: your flights with their tracks, your routes with their pilot log and loadsheet, and your aircraft go to the data service (Cloudflare D1 and R2) and are kept there with your account, not encrypted with your recovery code, so that the service can keep your phones and the web in step. We use them for nothing else, and look at them only when you ask us to help. Switching it off asks whether to delete the online copy; erasing your account deletes it.
• FlightLog on the web: signing in at app.krimsoft.net works as in the app, with your email address and a code; an address without an account gets one. The browser keeps a copy of your online logbook in its own storage, to open it quickly, until you sign out.
• Your GlidingApp flights on the web, only when you link GlidingApp as a member there: the data service asks your club's service for your own flights in the club's GlidingApp administration, and for the track of one you open, and passes them on to your browser, keeping nothing of them. The browser adds them to your online logbook, where they are kept as described above. Nothing is sent to GlidingApp.
• Live traffic: the coarse square around you — half a degree, some fifty kilometres — goes to the data service, which listens to the Open Glider Network and other receivers for the aircraft in it. ADS-B positions are fetched by your phone from adsb.lol for that same coarse area around the aircraft, never for your exact position. For an aircraft you tap, its call sign and the coarse square go to the data service, which asks adsb.im for its route.
• Crew detection, only for a member of a club that has it, with the phone linked to their GlidingApp account — on unless you switch it off in Settings → GlidingApp: after a take-off, its place and time and your track for the first minute go to the data service, which compares them with the gliders the Open Glider Network heard taking off, answers which of your club's gliders it was, and keeps nothing. Then that glider, the take-off time and, if you tapped a seat tag, your seat go to your club's service, which fills in the crew of that launch in the club's GlidingApp administration, keeps your report as long as it keeps its record of changes to GlidingApp, and shows your name to a member who flew with you. With the switch off, none of this is sent.
• Reading photos, documents and logbook pages: a photo of an hour meter, the photographed pages of a logbook, the first rows of a spreadsheet logbook, or the pages of a document you choose to have read, go through the data service to Anthropic (Claude), which reads them and returns the result. FlightLog stores none of it: the data service passes it on and keeps nothing, and the result comes back to your phone alone. Photos are sent without their location data. These readings need you to be signed in, so that the service can count them per account.
• Feedback: your message, with your name and email address if you give them, the app's version and any files you choose to attach, are mailed through the data service and Resend to the app's maker. When you send a flight, its files carry no position, track or place unless you switch that on — the app shows you which files go.
• Help, only when you ask it a question (signed in): the text of your question, earlier questions and answers of the same conversation, the app's platform, version and language go through the data service to Anthropic (Claude), which answers from FlightLog's user manual. A spoken question is turned into text on your phone, by the phone's own speech recognition; the sound of your voice never leaves the phone, only the text does. Each question and its answer are kept for 90 days, with the app's platform, version and language but without your account, device, email address or IP address, so that we can see what pilots ask and improve the manual; then they are deleted. To keep to the daily limit of questions, the data service counts them per account for that day only.
• Weather, NOTAMs, airspace and maps: airfield codes to aviationweather.gov (NOAA); KNMI's observations, airspace, reporting points and NOTAMs through the data service, by country, airfield or coarse square; map, chart, terrain and satellite tiles of the area shown, from the data service and from the chart and image providers (Neway Data, EOX, PDOK, Digitaal Vlaanderen, SPW Wallonia, Geobasis NRW, Apple). Text you type into the map search goes to Apple (iPhone) or to the phone's search service (Android).
Every service contacted sees your phone's IP address, as with any internet connection. The data service does not store it; it is used only for an hour to limit abuse. Each provider's own privacy policy applies to what it receives.
Processors and transfers
We use Cloudflare (hosting and storage), Resend (email) and Anthropic (reading photos and documents, and answering questions to Help) as processors. Some of them are in the United States; transfers are covered by the EU–US Data Privacy Framework or the EU's standard contractual clauses.
Files you share
Backup files, flight exports, aircraft profiles and daily cards go only where you save or send them. A backup file is not encrypted: keep it somewhere private.
How long
Data on your phone stays until you delete it or remove the app. The cloud copy stays until you erase it. The online logbook stays until you delete it from the app or erase your account. Your account stays while you use it; an account unused for a long time is warned by email before it and anything belonging to it is cleared away. Feedback is kept as long as needed to deal with it. Questions to Help and their answers are kept for 90 days without your account, device or address; the count of your questions for a day is deleted within a day after that day is over.
Your rights
Under the GDPR you have the right to access, correct and erase personal data about you, to restrict or object to its processing, and to receive it in a usable form. Most of it is on your phone, where you control it yourself; the cloud copy you can erase from the app, and a backup file gives you all of it. To see or erase your account, or feedback you sent, contact us. For data held by your club's service or gliding.app, contact your club. You may also lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens), or with the authority where you live.
Young pilots
FlightLog is meant for pilots and student pilots. If you are under 16, ask a parent or guardian before you use the features that send information from your phone.
Changes and contact
When this policy changes, the app asks you to accept the new version. Questions about privacy can be sent to us from the app, under Settings → Help → Feedback & suggestions.