Airport SprintAirport Sprint
Airport Sprint / Goldhawk Labs

Privacy policy

How Airport Sprint handles your information

Airport Sprint is operated by Goldhawk Labs. Contact support@airport-sprint-leaderboard.com for privacy questions or requests. This policy covers the Airport Sprint iPhone and Android apps and airport-sprint-leaderboard.com.

Android-specific storage and controls

On Android, the current sprint, saved trips, latest and gate location fixes, account credential and pending uploads are encrypted with AES-GCM in app-private storage. The encryption key stays in Android Keystore. Android cloud backup and device transfer are excluded. Android saves the latest usable location and gate fix, not a GPS route. Location runs only during an explicitly started sprint and stops at gate arrival, cancellation or the twelve-hour limit. The ongoing notification provides timing and checkpoint controls; it does not display coordinates or a flight number. Android Settings control location and notification access.

Android creates its own random account credential and installation identifier. Uninstalling removes the local encrypted data and keys, but does not delete server-side data. Optional verified phone recovery can restore the public account and server records; it cannot restore private Android trip history.

Use You → Delete account and public data on Android to remove the server account, profile, public posts and associated recovery records. This action deliberately keeps private timing history on that phone and removes old account credentials from attached flight receipts. Delete a saved private trip separately from its receipt, after removing any public post or resolving a pending upload. Support can receive account-deletion requests through the contact details on this page, subject to an ownership check.

The Android app does not send aggregate usage diagnostics and contains no analytics or advertising SDK. Flight-experience summaries are sent only after you turn on Share flight record, as described below. The aggregate diagnostics description below refers to iPhone. The shared server descriptions for optional flight lookup, public profiles and scores, image screening, phone recovery, moderation and hosting apply to both apps. A chosen avatar photo is resized to 96 pixels, redrawn without its original metadata, and requires explicit consent before OpenAI screening. Shared score images contain score facts and a built-in character; they do not include a profile photo or username.

Trips and precise location

The app asks for location permission to detect nearby airports and check a recorded gate arrival against a matched flight. Recording starts when you start a trip. At the gate tap, the iPhone app may wait up to three seconds for a fresh location fix before stopping recording; the recorded gate time remains the original tap time. Recording also stops when you discard the trip, if permission is removed, or after twelve hours of continuous recording. You can explicitly resume GPS for a longer trip. The recording timeout does not limit the duration of a valid trip. iOS settings let you change permission at any time. Poor or approximate GPS can prevent a trip from qualifying for public sharing.

GPS coordinates, route history, exact private trip timestamps, and saved private flight history stay on your iPhone. Private trip files use iOS file protection and are excluded from device backups. They are not uploaded to the Airport Sprint application database or placed in shared widget storage.

The Lock Screen Live Activity contains timing information, the airport when available, and a verification summary. It does not contain GPS coordinates or a flight number. Information shown on your Lock Screen may be visible to someone who can see your phone.

Private sessions and flight lookup

The iPhone app creates a random private device credential in Keychain. It is not an advertising identifier and is not synchronized through iCloud. The server stores a hash of that credential, an internal account ID, and daily request counts. A private session allows flight lookup without choosing a public username. To protect shared lookup capacity, session creation and paid flight requests also use short-lived keyed network groups. The server derives a group from the connection address and the current time window, including an IPv6 /64 group where relevant, without storing the raw address in the application database. Different people on a shared network can use the same group. These groups limit abuse, not identify a traveler or measure their activity. Per-account and service-wide limits also apply. Window-based limits stop applying when the window changes; expired group records are pruned in bounded batches during later protected requests and can remain longer when the service is inactive. These necessary safeguards operate independently of the optional usage-diagnostics setting.

Flight lookup sends the flight number and departure date through our server to FlightAware AeroAPI. When refreshing a saved outcome, iPhone can also send the saved provider flight identifier to retrieve that same departure. GPS coordinates and the private device credential are not sent to FlightAware. The application database does not retain flight numbers or raw search histories. FlightAware processes the lookup under its own privacy policy.

For a leaderboard submission, our server temporarily processes a recorded gate timestamp and an encrypted schedule receipt to check the timing. It retains the verification result, provider provenance, an elapsed boarding-deadline margin when eligible, and a request fingerprint used to recognize retries. It does not retain the raw receipt, scheduled departure, flight number, or exact gate timestamp in the application database.

On iPhone, for a selected flight attached to a finished trip, or a cancellation you explicitly save, the app also sends an encrypted receipt so we can retain private flight-experience statistics: the operating airline's codes, departure airport, cancellation and diversion results, delay durations, whether those durations are estimates or actual results, and whether the provider has reported a final outcome. These summaries are associated with your private account, including when you have no public username, to support your statistics and possible future badges. They stay private unless you turn on Share flight record in the app. That setting publishes only flight totals and delay, cancellation, diversion and available verified 7700 counts or rates on your profile and the Chaos leaderboard. Your selected home airport determines your local comparison. Turning sharing off removes these public summaries and Chaos rankings while retaining your private records. The Lord, Lady or Sovereign title is your choice; it appears when the published record meets the title threshold. They do not contain the flight number, provider flight ID, destination, route, scheduled or actual flight timestamps, travel date, GPS, or public trip ID. An opaque reference prevents duplicate counting and lets later results replace earlier estimates. A lookup observation version orders updates; it is not a flight timestamp. These are account-linked summaries, not fully anonymous data.

On Android, turning on Share flight record enables a bounded foreground refresh of selected flights saved on the phone. The app sends the same encrypted receipts and retains the same account-linked summaries described above. Android can refresh these outcomes when you reopen the app or use Refresh flight record.

Searching alone does not add an experience. Only the selected flight from a finished trip, or a cancellation you explicitly save to private history, contributes. You can save a canceled flight before starting a timer without enabling GPS or recording a gate arrival. Saving a cancellation during a timer stops GPS and retains any recorded route only on your phone. Pending results may be refreshed when you reopen the app, within the normal flight-lookup limits; missing results remain unknown. A canceled flight can contribute even though it cannot qualify for a public score. We also retain provider-supplied operating airline codes with published scores for future airline statistics, without showing the codes on current public responses.

Optional aggregate diagnostics

The iPhone app sends aggregate usage counts to help us find errors and improve app flows. This setting is on by default. You can turn it off at any time under You → Privacy & my data → Share usage diagnostics; doing so stops further sends and clears pending diagnostic counts on your phone. A saved choice to turn it off is preserved across app updates. Counts already combined into server totals cannot be separated back out for an individual person.

Diagnostics contain the UTC day, app build, major iOS version, predefined action or error category, a coarse response-time bucket where relevant, and a count. Examples include a flight lookup returning no match, a trip waiting to upload, or a score image failing to render. These are totals of attempts and outcomes, not a history of an individual person's activity.

Diagnostic payloads do not contain account or installation identifiers, usernames, recovery numbers, profile content, trip IDs, flight numbers, airports, GPS, exact event timestamps, raw error messages, screenshots, or session recordings. They use a separate request without account credentials or installation headers. We do not add an advertising identifier or a third-party analytics SDK.

Pending counts are combined on your phone before sending. Only counts for the current and previous UTC day are eligible to be sent; older counts are discarded the next time the app processes its queue. Server storage combines accepted counts into daily buckets without storing individual event rows or linking totals to a profile. Expired daily buckets are removed incrementally on accepted diagnostic uploads after 90 days; physical deletion can take longer while the service has no upload traffic. Operator reports omit breakdowns with fewer than five recorded actions. Hosting providers process the connection information needed to deliver a request and may retain IP addresses and request metadata in operational logs, separate from our aggregate usage tables.

Optional phone recovery

You can add a US or Canadian phone number under You → Add a recovery phone number. This is optional. We attach it to your account only after you verify a texted code. We use it only to verify your recovery method and restore account access, including when you change or remove the number. We do not display it publicly or use it for marketing.

Twilio Verify processes the number and verification requests to send and check the codes you request. Standard message and data rates may apply. See Twilio's privacy notice. Our database stores the number encrypted, a keyed lookup hash, its masked ending, and verification time. These records remain linked to your account.

Temporary verification records include the encrypted number, masked ending, provider verification identifier, purpose, requesting credential hash, timestamps, and attempt count. Codes expire after ten minutes; our server does not store the texted code. Expired temporary records are deleted on the next recovery start or code check. Short-lived request counters use keyed digests of numbers, credentials, and IP addresses to limit abuse. These counters are pruned after expiry on recovery activity. Twilio and hosting providers may retain operational records under their own policies.

You can change or remove your number in Phone recovery after verifying your current number. Removal or full account deletion removes the recovery association and invalidates pending challenges for that account. Short-lived abuse counters can remain until expiry. Unverified temporary entries also expire and are pruned as described above.

Recovery restores your server account, including profile, posts, awards, and retained private flight-experience summaries. It replaces your account credential and revokes the old phone's server access. It does not back up or restore precise routes and exact private trip history kept only on the old phone. If you skipped setup or no longer control the verified number, we cannot promise to restore access.

Public profiles and scores

Choosing to publish a score creates or uses a public username. The server stores the username, any optional avatar, bio, social profile links and home airport you supply, random trip IDs, departure-airport codes, elapsed home-to-terminal and terminal-to-gate times, verification results, eligible boarding-deadline margins, and the day the trip was posted. The posting day is not the travel date.

Public profiles and boards show these public fields and statistics derived from published trips, including personal records, averages, airport personality, and Founding Flyer awards. They can be viewed on the public website without signing in. A username is a public pseudonym, not a guarantee that nobody can identify you. Optional social links can reveal your identity or connect your profile to another service. Avoid putting sensitive information in your username, bio, or avatar.

The app resizes avatar uploads and the server validates them and removes optional PNG metadata. Before uploading a new photo, the app asks your permission to send it to OpenAI for content moderation and image screening. You can choose a built-in avatar instead. Uploaded avatars stay private until screening or manual review approves them. Built-in avatars do not need that check. An approved avatar is a publicly shared image. Deleting the avatar does not remove copies someone may already have saved.

Image sharing and external services

Score images are generated on your phone and omit your username, avatar, flight number, exact trip timestamps, route, and private account key. When you select a destination in the iOS share sheet, that service receives the image you choose to share. Saving an image adds it to Photos after the permission iOS requires. Social services and your Photos/iCloud settings govern any later storage or sharing. Airport Sprint does not sign in to social accounts or post automatically.

Opening an optional social profile link takes you to an external service governed by that service's policies.

Hosting and website preferences

Our app backend and website use Cloudflare hosting. Older Airport Dash links use Porkbun’s URL-forwarding service, which processes the connection information needed for that redirect. We have disabled Workers application and invocation logging, tracing, and Logpush for the production service. Cloudflare still processes connection information to deliver and protect requests and may retain security, infrastructure, billing, or backup records under its own policies. Earlier Sites hosting retained operational request logs, which could include IP addresses, request URLs and headers, response status and server timing. Moving the service does not delete those historical records. These provider records are separate from aggregate usage tables and are not represented as anonymous; turning off usage diagnostics does not remove them. The Airport Sprint application database does not store raw IP addresses; session, lookup, recovery and moderation abuse limits use short-lived keyed groups or digests. App code does not intentionally log GPS, private credentials, phone numbers, codes, or raw verification evidence. Cloudflare privacy policy.

The website uses browser-local storage to remember interface preferences such as the chosen livery and filters. The app uses local preferences for its settings. Airport Sprint has no advertising, advertising identifiers, or third-party analytics SDKs, and does not sell personal information or use it for cross-app advertising tracking.

Retention and deletion

Private phone history remains until you delete it or the app's local data is removed. The Keychain credential may survive reinstalling the app, depending on iOS behavior. Uninstalling the app does not delete your server-side profile or posts.

On iPhone, use You → Delete my profile, posts & private trips to delete your server-side session/profile and published posts, release the username, and remove the phone's private trip history, pending uploads, and account credential. This action is available even without a public username. It cannot be undone. You can also remove individual published scores, remove an avatar or optional profile information, or delete private history using the app's relevant controls.

Deleting your account also deletes private flight-experience records and removes their contributions to statistics. Deleting a private trip or all private history queues deletion of the related flight-experience summaries; if offline, that deletion completes when the app next connects. Removing a public leaderboard post alone preserves private history and its flight-experience summary. Retained private summaries remain linked to your account until you remove them or delete the account.

An airport's historical Founding Flyer claim remains after full account deletion, with the owner removed. The remaining airport and claim day are not linked to your deleted profile. Deleting an individual score does not remove an existing founding award.

Server-side account records remain until deleted; current application code does not automatically expire inactive sessions. Site-wide daily lookup totals do not contain individual account identity. Deletion removes active application records, while service providers may retain operational logs or backups under their applicable retention arrangements. Information copied by other people or shared to another service is outside Airport Sprint's deletion controls.

If you report a profile in the app or website, we store your private account identifier, the reported profile identifier and content version, the reason you select, optional details you enter, and a snapshot of the reported public profile text and avatar. We do not show the reported user who sent the report. If you contact support by email, we receive your message, reply address, and information you choose to send. We use it to respond, investigate the report, and manage any resulting moderation action. Do not send your device credential, verification code, passwords, identity documents, home address, or boarding pass. We may need to verify that a privacy request concerns your profile. Support cannot retrieve precise routes stored only on your phone or bypass account-ownership verification.

Your choices and updates

You can browse public boards without creating a public profile, choose whether to publish a score, edit or clear optional profile fields, manage location and Photos permissions in iOS, and use the deletion controls described above. Depending on where you live, you may have rights to request access, correction, or deletion of personal information. Contact support@airport-sprint-leaderboard.com to make a request.

If our practices change, we will update this policy and its effective date. Changes requiring additional permission will be presented through the relevant app or system controls.

Content moderation and hidden users

We check public usernames, bios, and social profile handles for profanity. Reports and moderation records are private and are kept for up to 90 days. Pending avatar uploads expire after 30 days; rejected candidate image data is discarded. Deleting an account removes its linked reports, uploaded avatar candidates, and moderation action records. Rate-limit counters use private account identifiers and a salted digest of connection addresses to prevent report and upload abuse. Limits stop applying when their time window ends, within two days; expired records are pruned in bounded batches on subsequent moderation activity and can remain longer while the service is inactive.

Your hidden-user list is saved on your iPhone, Android phone, or in that browser. It is not sent to us or synced through account recovery. Hiding someone removes their profile and individual leaderboard entries from that device or browser. It does not change public rankings or anonymous airport statistics. The person is not notified.

Content warnings and publishing bans

We screen uploaded avatars for harmful imagery, hate symbols, and visible profanity using OpenAI’s moderation and vision services. Unclear images or unavailable screening stay private for manual review. Built-in avatars do not require these requests.

A confirmed rejected username or avatar submission adds one strike. We warn after the first two strikes. Three strikes block public profile edits and leaderboard posting for the account and app installation. Private timing, recovery, and account deletion remain available. Duplicate network retries and screening errors do not add strikes. You can contact support to appeal; an operator can undo mistaken strikes and bans.

The app creates a random installation identifier, which is sent with profile edits, public posts, and authenticated profile status requests. The server stores a hash of it with account links, submission hashes, strike counts, and ban status. It is not an advertising identifier or hardware fingerprint and is not used for cross-app tracking. Deleting and reinstalling the app creates a new installation identifier; it does not restore a banned account.

Account deletion removes the profile and account links. We retain the installation’s hashed identifier and strike/ban records to enforce the posting restriction, including after account deletion, until those strikes are reversed or reset. These records contain the reason, date, and content hash rather than the rejected image or submitted username. Pending submissions without strikes are removed after 30 days. Temporary image-decision cache entries contain only an image hash and decision and expire after 30 days.