English · Deutsche Version

Flight Velocity — Privacy Policy

Effective date: October 13, 2026
Last updated: October 13, 2026

Flight Velocity is built so that your flight recordings and Flight History stay on your device. Your live GPS track and recorded sensor data are not uploaded to Digital Lobby’s servers. Analytics, crash reports and personalised advertising are only used in the EU/EEA if you consent.

1. Controller

Digital Lobby
Proprietor: Mauro Sergio Rodrigues da Silva
Steinhausenstrasse 1
45147 Essen
Germany
E-Mail: info@digitallobby.de

Digital Lobby is not required to appoint a data protection officer. For any privacy question, contact us at the address above. This policy applies to the Android and iOS versions of Flight Velocity (the “App”).

2. Overview

3. Location and Flight Recording

3.1 Live location

With your permission the App uses your device location (GPS) to show ground speed, altitude, vertical speed, heading, your position on the Home map and route progress. While a recording is active, the App can keep processing location in the background or with the screen locked, as far as Android or iOS allow. On Android an ongoing notification shows that a recording is active.

Your live position is processed on your device. To display the Home map, the App loads map data for the area around your current position from Mapbox (see section 7); Mapbox therefore receives the map area being viewed, not your recorded track.

3.2 Flight History

When you tap Start, the App records on your device: timestamps, latitude and longitude, ground speed, altitude, vertical speed, heading, pitch and roll, G-force, detected flight phases, GPS/sensor quality and derived statistics (duration, distance, maximum values). The App evaluates this data automatically to decide whether a genuine flight took place. Flight History is stored only on your device; Digital Lobby does not receive it.

A flight recorded in the free version can be stored locally and become visible in Flight History once Flight Velocity Plus is active.

3.3 Nearby airport suggestions

If you turn on Nearby Airport Suggestions (off by default), your position is compared with an airport list stored inside the App. This happens on your device only.

Legal basis: performance of the contract (Art. 6(1)(b) GDPR); storage on and access to your device for these functions is strictly necessary for the service you request (§ 25(2) no. 2 TDDDG).

4. Motion Sensors

The App uses the accelerometer, gyroscope, magnetometer and, where available, the barometer for the attitude indicator, G-force, heading and altitude. These values are processed on your device and, during a recording, stored locally in Flight History. They are not uploaded. Legal basis: Art. 6(1)(b) GDPR.

5. Preparing a Flight and Route Content

5.1 Prepared flights

When you prepare a flight, the App stores origin, destination, planned route points, route maps, weather, points of interest and offline content on your device.

5.2 Highlights preview and points of interest (Wikidata)

To find places along your route, planned-route coordinates and your language are sent to Wikidata / Wikimedia. This also happens for the short highlights preview that free users see before preparing a flight. The request contains no live GPS track, advertising ID or account data. Results are cached on your device so the same route is not queried again.

5.3 Weather (MET Norway)

Planned-route coordinates are sent to MET Norway to obtain weather for the prepared route. Your live position and Flight History are not sent.

5.4 Reworded facts (Railway and Google Gemini)

To make public facts about a place shorter and easier to read, the App sends the point-of-interest identifier, its title, the selected public facts and the language to a Digital Lobby backend hosted on Railway, which may forward these public facts to the Google Gemini API. No location, Flight History, advertising ID, name, email or payment data is sent. The generated text is kept in a shared server cache (keyed by point of interest, language, content hash and prompt version) and stored on your device with the prepared flight, so it is available offline.

Legal basis for section 5: Art. 6(1)(b) GDPR. Network providers necessarily see technical connection data such as your IP address.

6. Advertising and Consent (EU/EEA)

The free version shows banner and interstitial ads from Google AdMob. Plus users see no ads. When the App starts, Google’s User Messaging Platform (a certified consent management platform under the IAB TCF) asks for your consent where required. Depending on your choices, AdMob may use your advertising ID (Android Advertising ID; on iOS the IDFA only if you also allow tracking in Apple’s App Tracking Transparency prompt), device and app information, ad interactions and an approximate location derived from your IP address to show and measure ads.

If you decline, ads are limited according to Google’s policies for non-consented traffic. You can review or withdraw your consent at any time in the App menu under Privacy Choices; on iOS you can also change tracking in the system settings.

Legal basis: consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG).

7. Maps (Mapbox)

Maps and offline maps are provided by Mapbox. To display a map, Mapbox receives the requested map area (around your current position on the Home map, or around the prepared route), your IP address and technical device information. The Mapbox SDK also sends anonymous usage telemetry; you can switch it off through the ⓘ button on the map. Legal basis: Art. 6(1)(b) GDPR; telemetry: legitimate interest of Mapbox and Digital Lobby in a working map service (Art. 6(1)(f) GDPR).

8. Analytics (Firebase Analytics)

With your consent, Firebase Analytics records how the App is used (for example: a flight was prepared, a recording was started, the paywall was shown, whether the user has Plus) together with device and app information and an app-instance ID. We do not send locations, routes, Flight History or feedback text to Analytics. Legal basis: consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG). Without consent, Analytics stays switched off.

9. Crash Reports (Firebase Crashlytics)

With your consent, Firebase Crashlytics receives crash reports (crash log, stack trace, device model, operating system, app version and an installation ID) so we can find and fix errors. In the EU/EEA Crashlytics is switched off until you consent. Legal basis: consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG). Crash data is kept for 90 days.

10. Remote Configuration (Firebase Remote Config)

The App loads settings from Firebase Remote Config so we can switch features on or off without an update. This uses a Firebase installation ID and app/device information. Legal basis: legitimate interest in operating and maintaining the App (Art. 6(1)(f) GDPR); § 25(2) no. 2 TDDDG.

11. Subscriptions (Flight Velocity Plus)

Plus is sold as a monthly or annual subscription through the Apple App Store or Google Play. Payment is handled entirely by Apple or Google; we never receive card or payment details. To manage your subscription status we use RevenueCat, which processes a random App User ID, purchase and subscription information and receipts or purchase tokens. Your subscription status is also cached on your device. Legal basis: Art. 6(1)(b) GDPR.

12. Optional Feedback

After a flight the App may ask for optional feedback. If you answer, your selection, an optional comment, the app version/build and the platform are stored in Cloud Firestore. We do not attach your name, email or Flight History. Please do not include personal data in the comment. Legal basis: consent by submitting (Art. 6(1)(a) GDPR).

13. Ratings and Update Notices

The App may show Apple’s or Google’s own rating dialog; your rating is handled by the store and we only see it publicly in the store. To tell you when a new version is available, the App checks the store listing (app ID and country; the store sees your IP address). Legal basis: legitimate interest in keeping the App up to date (Art. 6(1)(f) GDPR).

14. Notifications and Local Settings

The App uses local notifications (for example for an active recording or new route content). No push service is used. Settings such as units, language, tutorial status, prepared flights and cached subscription status are stored on your device and removed when you delete the App or its data.

15. Service Providers and Recipients

Data is processed by the following providers, as described above:

ProviderPurposeDataLegal basis
Google AdMob + User Messaging Platform (Google Ireland Ltd. / Google LLC)Advertising in the free version; consent managementAdvertising ID (where permitted), device/app information, ad interactions, approximate location derived from IP, consent signalsConsent (Art. 6(1)(a) GDPR, § 25(1) TDDDG); consent management itself: legal obligation / legitimate interest
Firebase Analytics (Google)Usage statisticsApp events, device/app information, app-instance IDConsent (Art. 6(1)(a) GDPR, § 25(1) TDDDG)
Firebase Crashlytics (Google)Crash reportsCrash logs, stack traces, device/OS/app version, installation IDConsent (Art. 6(1)(a) GDPR, § 25(1) TDDDG)
Firebase Remote Config (Google)Remote app configurationFirebase installation ID, app version, device/OS informationLegitimate interest in operating the app (Art. 6(1)(f) GDPR); § 25(2) no. 2 TDDDG
Cloud Firestore (Google)Optional feedbackSelected answer, optional comment, app version/build, platformConsent (Art. 6(1)(a) GDPR) by submitting
RevenueCat, Inc. (USA)Subscription and entitlement managementRandom App User ID, purchase/subscription information, receipts or purchase tokensContract (Art. 6(1)(b) GDPR)
Apple App Store / Google PlayDistribution, purchases, ratings, update checkStore account and payment data (processed by Apple/Google); for the update check: app ID, country, IP addressContract (Art. 6(1)(b) GDPR); update check: legitimate interest (Art. 6(1)(f) GDPR)
Mapbox, Inc. (USA)Maps and offline map contentMap area around your current position or the prepared route, technical/network data, SDK telemetry (can be switched off via the map’s ⓘ button)Contract (Art. 6(1)(b) GDPR); telemetry: legitimate interest (Art. 6(1)(f) GDPR)
Wikidata / Wikimedia Foundation (USA)Points of interest and public facts along the routePlanned-route coordinates, languageContract (Art. 6(1)(b) GDPR)
MET Norway (Norway)Weather for prepared routesPlanned-route coordinatesContract (Art. 6(1)(b) GDPR)
Railway Corporation (USA)Hosting the Digital Lobby text backendPublic point-of-interest facts, language, technical connection dataContract (Art. 6(1)(b) GDPR)
Google Gemini API (Google)Rewording public point-of-interest factsPoint-of-interest title and public facts (no personal data)Contract (Art. 6(1)(b) GDPR)

16. Transfers Outside the EU/EEA

Some providers (Google, RevenueCat, Mapbox, Wikimedia Foundation, Railway) may process data in the USA or other third countries. Transfers are based on the EU-U.S. Data Privacy Framework where the provider is certified, or otherwise on the European Commission’s Standard Contractual Clauses (Art. 46(2)(c) GDPR). Norway (MET Norway) is part of the EEA.

17. Retention

18. Do You Have to Provide Data?

You are not legally or contractually required to provide personal data. Without location permission the speed, position and recording functions do not work. Without consent the App works fully, but with non-personalised ads and without Analytics and crash reports.

19. Automated Decisions

The App automatically evaluates sensor data to detect flight phases and genuine flights. This does not produce legal effects or similarly significant effects for you (Art. 22 GDPR).

20. Your Rights

Under the GDPR you have the right to:

Right to object (Art. 21 GDPR)

Where we process data on the basis of legitimate interests (Art. 6(1)(f) GDPR), you have the right to object at any time, on grounds relating to your particular situation. We will then stop the processing unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing serves the establishment, exercise or defence of legal claims. To object, write to info@digitallobby.de.

Most App data never leaves your device, so we cannot access it; you control it directly by deleting it in the App or deleting the App. Where server-side data is stored without a name or account, we may need additional information to identify it.

21. Children

The App is not directed at children under 16. We do not knowingly process personal data of children based on their own consent. Contact us if you believe this happened.

22. Security

Connections to our backend and to providers are encrypted (HTTPS). We use appropriate technical and organisational measures; no transmission or storage is completely secure.

23. Changes

We update this policy when the App, its providers or the law change. The current version and its date are always available here and in the App menu.

24. Terms of Use and Contact

Use of the App is also subject to the Flight Velocity Terms of Use. Questions: info@digitallobby.de.