Cookie Notice
The storage and cookies we use, and how to choose.
Draft: the operator's company details and contact addresses on these pages are placeholders. They must be replaced before any ads run or real claims are taken.
Version 2.0 · Last updated 21 Nov
1. In short
FlyHandled uses only what it needs to work. We use no advertising cookies and no tracking cookies. Most of what we keep stays on your device.
2. Strictly necessary (always on)
- fh.locale, fh.lang and fh.alang (cookies, 12 months): your language, so every page reads the same.
- fh.theme (cookie and local storage): dark, light or the system's appearance.
- fh.session and fh.others (cookies, 30 days, not readable by scripts): keep you signed in, and the other accounts you added on this device.
- fh.code (cookie, 10 minutes, not readable by scripts): a pending sign-in or reset code, kept only as a one-way hash.
- fh.cp (cookie, with your session): that your account has accepted the current Terms, so the app shows the right screen from the first moment.
- fh.user (cookie, 12 months): that this device uses the app, so the address flyhandled.com opens the app instead of the website.
- Your flights, settings, claims you started and documents (local storage, until you delete them or your account): kept on this device under your account's own name, so two accounts on one device never mix.
- fh.tab.account (session storage, this tab) and fh.account.last (local storage): which account a tab is on and which one you used last.
- Short memories of the screen (session storage, this visit): where you were, what you had open, whether the opening screen has played.
- fh.simDays (local storage, 60 days at most): the country your phone connects from on the days you open the app, codes and days only, to suggest a change of your phone's country; never sent.
3. Counting how the app is used
Without any cookie or anything stored on your device, we count how the app is used and where visits come from, as totals that name no one. Do Not Track and Global Privacy Control turn it off. Keeping your own timeline of app use with your account happens only if you turn on "Ajută-ne să îmbunătățim aplicația" in Settings; it stores nothing extra on your device.
4. Third parties
When a map loads, the map tiles' provider receives your IP address to send the tiles. The payment page is our payment provider's, which may set its own strictly necessary cookies for security and fraud prevention. A partner's page you open is the partner's, under its own cookie policy.
5. Your choices
Settings, Privacy, holds your choices. You can also clear cookies and site data in your browser; this signs you out on this device and removes what is kept there.
Company details in [brackets] are placeholders to be completed before launch.