FlightFames privacy policy
Effective October 7, 2026. FlightFames is operated by Moses Olamuyiwa Afolabi. Contact hello@flightfames.com for privacy questions.
Public flight board
You can browse flight information without an account. Selected airport codes are sent to AirLabs by our server. Our application does not attach your email or account identifier to those requests. Provider records are cached and may be partial or stale as labeled. Airport selection does not guarantee coverage.
Android test build
The current native Android test build is a public flight board. It sends selected airport codes to FlightFames over HTTPS and stores the last airport, display direction and one public flight snapshot locally for offline viewing. You can clear this cache in the app. It does not request location, contacts, camera, microphone, storage or notification access. The next Android test build adds email registration, verification, password recovery, sign-in, saved flights and account deletion through the same HTTPS account service as the website. Its session stays in memory for up to one hour and is discarded when the app restarts; passwords and session tokens are not saved to device storage. Purchases, advertising and push alerts remain disabled. Device testing of these account flows is still required. Opening support or privacy links uses your browser or email app and their privacy practices apply. Our hosting provider may process technical request information such as IP addresses for service operation and security.
Accounts and saved trips
Public email accounts use Firebase Authentication for password handling, verification and password recovery. Existing accounts can still use the hosting platform’s sign-in service. We receive a site-specific user identifier, email address and, when available, a display name. We store your account email and creation time, flights you save, followed-flight preferences, notification history and any registered push-device tokens. A saved flight is a bookmark, not a reservation or proof of travel. Passwords are sent securely to Firebase and are not stored in the FlightFames application database.
Support
Signed-in contact messages are stored with your account identifier, email, message and timestamp so the owner can respond. Emails sent to hello@flightfames.com are forwarded to the owner’s Gmail inbox. Do not include passwords, payment information or sensitive travel documents.
Service providers and advertising
The website uses Sites hosting and its Cloudflare database, Firebase Authentication and the hosting platform’s existing account authentication, AirLabs flight data, and Porkbun forwarding with Gmail for email support. Firebase Cloud Messaging is referenced by the notification code, but mobile push delivery is not enabled or verified in the current release. External sponsor images and links can make requests to the sponsor’s hosting provider; their privacy practices apply. Stripe test billing is being configured for FlightFames Plus. When checkout opens, Stripe handles payment details; we store Stripe customer and subscription identifiers, subscription status, paid-access expiry and processed event identifiers. Card numbers are not stored in FlightFames. Public subscription purchases remain closed. The current release has no connected behavioral advertising network or application analytics. Hosting and email providers may process technical access logs and retain backups.
Storage and security
Provider credentials stay on the server. Account actions are checked on the server. The sound preference is saved locally on your device. Sign-in services may use cookies to maintain your session. Account-linked records remain until you remove them or delete your account; notification history and support messages currently have no automatic retention limit. Shared flight records expire from usable caches according to the displayed freshness controls.
Your choices and deletion
In My trips, you can remove saved flights and delete your FlightFames profile, saved flights, followed-flight preferences, notification history, device tokens and account-linked support messages. Successful deletion removes those records and local billing mappings from the application database, and cancels any FlightFames Stripe subscription immediately. Stripe retains payment records under its own retention requirements. For public email accounts, it also deletes the FlightFames Firebase sign-in account. An existing hosting-platform sign-in account belongs to that separate service and remains. You can also request deletion by email without signing in. Support-mailbox copies, provider logs and backups have separate retention; see the deletion page for the current limits.
Future releases
We will update this notice before introducing mobile push delivery, analytics, billing or advertising SDKs. Google Play privacy declarations will be checked against the final Android release.