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.

If you join the waitlist, we send your email, consent, locale, form source, and any campaign UTM parameters to the production processor identified before launch. We use this data only for beta access and messages directly related to FlyHere. We retain it until the beta programme 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 and Apple processes 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 Apple (sign-in and in-app purchases). Account data is held in the EU.

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.

So that we can see where the app fails to decide and fix those places first, each check you run is recorded with: the time of the check from your phone's clock, the outcome (allowed, conditions, prohibited, cannot determine), the codes of the zones involved, the identifiers of areas the app has no verdict for, an approximate location, the aviation data version, the app version, your language and your account identifier. The server also notes when the record reached it.

The location is rounded to two decimal places, roughly a kilometre, on your phone and before the record is stored. We do not keep, and cannot recover, the exact spot where you stood. We also keep nothing you typed, no drone serial numbers and no qualification document.

Records are made even with no signal, kept on the phone and sent once you have a network. You can switch them off at any time in Profile under “Share usage data”; nothing is then recorded or sent, and anything still waiting on the phone is discarded. We keep the records for at most 400 days.

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 production controller name will be added before release. The current contact route for privacy questions is on the Support page.