How FlyHere handles data

FlyHere uses no advertising and no cross-app tracking. The app requires an account because the profile and subscription belong to it. The check itself is computed on your device; your pilot profile and drones sync to the account, while the scanned credential, saved places and history stay on the phone.

The app requests precise location only for a check you start. FlyHere does not track location in the background. Maps are rendered by MapLibre from OpenFreeMap tiles (OpenStreetMap data); the tile server receives only the technical requests needed to draw the visible map, with no account and no API key. Place search in the iOS app uses Apple Maps. In the web and Android apps, confirming a search sends the place name, selected country and language to the FlyHere backend and its geocoder (OpenStreetMap Nominatim). The query contains no account or pilot profile; cached results are valid for 7 days and then scheduled for removal during regular cleanup. Do not enter personal or confidential information in place search.

If you join the waitlist, we send your email, consent, locale, form source, and any campaign UTM parameters to Cloudflare, our processor. We use this data only for the three-months-free waitlist offer and messages directly related to FlyHere. We retain it until that offer ends or you withdraw consent. You can request deletion through the Support page.

If you request a missing model, the FlyHere Cloudflare backend receives only the manufacturer, model, optional note, locale, and form source. The request is anonymous; your pilot profile, operator number, location, and uploaded credential are never sent.

If you create an account we process your email address, the name you enter, your language and whether the address is confirmed. Without those the account cannot be recovered and a password reset cannot reach you. We do not store an IP address with sessions.

For a subscription we process its status, transaction identifiers, amounts and payment dates needed for access and accounting. We never see or store card details. Stripe processes web payments, Apple processes iOS in-app payments, and Google Play processes Android in-app payments. Stripe receives the account email and the internal account identifier needed to attach the subscription.

In the referral programme we store who introduced whom and the reward amounts. A referrer never sees the email addresses or names of the people they brought, only dates and reward counts.

Processors: Cloudflare (hosting and database), Resend (outgoing email), Stripe (web payments), Google (sign-in, if used, and Google Play purchases), and Apple (sign-in and in-app purchases).

You can delete the account at any time from the Account page. Payments and rewards stay in the accounting record because the law requires it, but they stop being tied to an active profile.

While you are signed in, your profile belongs to your account, so that signing in on a new phone brings it with you. Only what a flight check needs is synchronised: your drones, whether you are a registered operator, your operator registration number, the type of your qualification and its validity.

The scan of your qualification document is never synchronised. It stays in protected storage on your phone and does not leave the device. There is not even a column for it on the server.

Usage sharing is on by default and can be switched off in Profile under “Share usage data”. When enabled, completed checks produce records containing the check time, outcome, zone and unknown-area identifiers, data and app versions, language, and coordinates rounded to two decimal places on your device. Records made while signed in are linked to your FlyHere account. We use them to identify gaps and improve coverage. They do not include your credential scan or drone serial number.

Records can wait on the device while offline and upload when a connection is available. Switching sharing off discards pending optional records and stops new optional usage records. Account/profile sync, purchase verification, check authorization and security records continue. Web and Android also send a separate daily total by platform and outcome without an account identifier. Turning off usage sharing does not disable that aggregate counter.

Usage records are scheduled for deletion 400 days after the server receives them. Cleanup runs every 15 minutes and deletes related unknown-zone records as well. A failed cleanup or a backlog is retried in later runs. Deleting your account removes the account link from these usage records; it does not immediately erase every earlier record.

Rounding applies to optional usage records. Map tiles, place searches, official-map links and other features have separate data flows described above; do not put sensitive personal information into place-search queries.

To operate the service and investigate account or payment problems, internal notifications may include your email, signup or activation time, app build, subscription product, status and expiry. They are delivered to FlyHere's internal operations channel through the configured provider, which may use Telegram. Delivered notification records are deleted from FlyHere's outbox after 30 days; undelivered records remain for retry. Copies held by the channel provider have separate retention. These notifications are independent of optional usage sharing. Contact Support to exercise your data rights.

In Profile you can delete history or all local data, including your profile, local pilot credential, drones, place suggestions, cache, and the widget’s last result.

The controller is Jan Kluz, IČO 22532501, the legal entity identified at web checkout and as Seller on the App Store. The contact route for privacy questions is on the Support page.