Privacy Policy
Last updated: November 16, 2026
FocusFlight is a focus timer that turns focus sessions into simulated flights. You can study without an account. If you choose to sign in with Google, we save your completed flights so you can access your flight log on other devices.
This policy explains how FocusFlight handles information when you use focusflight.io. Contact the FocusFlight operator at admin@focusflight.io with privacy questions or requests.
1. Information we handle
- Guest flight history: completed routes, airport information, study duration, simulated distance, completion date, flight number, and airline are saved in your browser’s local storage.
- Optional Google account: when you sign in, Google shares account information such as your account identifier, email address, name, and profile picture with our authentication provider, Supabase. We do not receive your Google password. The current sign-in requests basic identity, email, and profile information, not access to Gmail, Drive, or Calendar.
- Traveler profile: you can choose a nickname and an optional home airport. We store these with your account to personalize greetings and default departure selections across devices. Your home airport is private. Your nickname is public only when you opt into a challenge; editing it updates your challenge name without resetting your score.
- Account flight history: completed flights are associated with your account and stored in Supabase. You can choose to move existing guest flights into your account.
- Optional focus challenges: if you join, we store your chosen public nickname, enrollment time, and server-recorded flight starts and completions. Your challenge nickname, rank, and total study time are public. Your email, private flight log, and routes are not shown on the leaderboard.
- Usage and technical information: service providers may process IP addresses, browser and device details, request logs, and identifiers when delivering the site. When analytics is enabled, we collect page views and study events such as flights selected, started, completed, or abandoned, along with route and duration information. We also measure account-panel openings, feature use, profile-save success or failure, weekly-goal changes and milestones, and optional positive/negative passport feedback. These events use feature states, numeric targets, and fixed categories; we do not intentionally include your email, nickname, saved home airport, or free-text feedback. When you sign in, we send PostHog your internal FocusFlight account identifier to connect your activity across sessions and devices, including prior browser activity where supported. Guests use a browser-generated identifier. Signing out resets the analytics identity before subsequent guest activity.
- Messages: if you email us, we receive your email address and anything you include in your message.
Choosing an airport does not request your device’s precise location. Flight activity is a simulation and does not describe actual travel.
2. How information is used
We use account information to authenticate you, show your signed-in account, and keep each account’s history separate. We use your saved profile to personalize the app and remember your home airport. Personal study stats are calculated from your completed flight log, including imported flights. We use flight data to display your routes and study totals and synchronize your log across devices. Usage information helps us understand how the timer is used and diagnose problems. We use messages to answer your requests.
Your account flight log is private. Joining a study challenge opts you into a public leaderboard showing your chosen nickname, rank, and challenge study total. Challenge records are separate from private history, and imported history does not contribute to challenge scores. We do not use Google account information to personalize advertisements. We do not intentionally send Google email addresses, names, or profile pictures to our analytics integration; the internal FocusFlight account identifier is used for signed-in analytics as described above.
3. Local storage and sign-out
The app stores guest history, cached account history, pending sync changes, pending challenge completions, device-local active-flight recovery snapshots (route, boarding details, timer, session identifier, and challenge registration state), optional weekly focus targets, whether you have submitted passport feedback, and authentication session information in browser storage. Signed-in weekly targets are stored privately in Supabase and cached on your device, with pending edits retained for retry. Guest targets stay on that device and are not automatically imported into an account. Removing an account target retains a cloud removal marker so older devices cannot silently restore it. Recovery snapshots and account caches are separated by user ID. A saved flight keeps counting elapsed time while the app is closed and can be resumed only from the same browser and account; recovery snapshots do not sync across devices. Signing out returns to the guest log but does not erase cached account history from that device. On a shared device, sign out and clear the site’s browser data when finished.
Clearing site data removes local copies and may erase unsynced flights. It does not by itself delete history or goals already stored in your account.
4. Providers and sharing
We use providers to operate the service:
- Google and Supabase: Google sign-in, account authentication, and cloud history storage. See Google’s Privacy Policy and Supabase’s Privacy Policy.
- PostHog: usage analytics, when enabled. Our integration uses a browser-generated identifier for guests and a stable internal FocusFlight account identifier for signed-in users, enabling account-level analysis across devices and sessions. The SDK keeps identity information in local storage; it does not intentionally attach your Google email or name, enable session recordings, or automatically capture clicks. Technical request information may still be processed. See PostHog’s Privacy Policy.
- Google AdSense: advertising, when enabled. Google and its partners may use cookies or device identifiers to deliver and measure ads. See how Google uses information from partner sites and Google’s ad settings. Where a consent message is presented, use its privacy choices to manage consent.
- Mapbox, Google Fonts, and GitHub Pages: maps, fonts, and website hosting. These providers receive technical request information to deliver their services. See Mapbox’s Privacy Policy and GitHub’s Privacy Statement.
These standalone privacy and terms pages do not load the app’s analytics, advertising, maps, or Google Fonts scripts. Hosting still processes requests needed to serve the pages.
Information may also be disclosed when required by law or necessary to protect the service, its users, or others. Providers may process information in countries other than your own.
5. Retention and deletion
Challenge enrollment and scoring records are retained to show final standings until you request deletion or we discontinue the feature. Clearing your private flight log does not remove your challenge score.
Guest history remains on your device until you clear it or your browser removes it. Your profile, account weekly target (including removal markers), and account history are retained to provide personalization and synchronization unless you request deletion or we discontinue the service.
Clearing history while signed in hides the flights known to that device across synced devices. Synchronize first to include flights from other devices. The current system retains deleted flight records and deletion markers in cloud storage to prevent stale offline copies from restoring them; clearing the visible log is not full account-data deletion.
For account and associated cloud-data deletion, email admin@focusflight.io from the address used to sign in. We may need to verify your request. Copies may remain temporarily in provider backups or logs, or where retention is required by law. Clear the site’s browser data on your devices to remove local copies as well.
6. Your choices and requests
You can use guest mode, decline to import guest flights, sign out, clear your visible flight history, and remove local site data through your browser. You can also revoke FocusFlight’s access in your Google Account settings; revocation does not itself delete stored flight history.
Depending on where you live, you may have rights to access, correct, export, or delete personal information, object to certain uses, or withdraw consent where processing relies on consent. Send requests to admin@focusflight.io.
7. Security
We use encrypted connections and account-based database access controls to protect cloud history. No online service or browser storage is completely secure. Keep your Google account and devices secure, especially when using a shared computer.
8. Changes and contact
We may update this policy as the service changes. The date above identifies the latest revision. Contact admin@focusflight.io with questions about this policy or your information.