Who operates Airgeek
Airgeek is operated by Airgeek LLC, based in Washington, United States.
Email airgeekjx@gmail.com for support, privacy questions, or account deletion requests.
Information we handle
- Accounts. Google sign-in through Supabase Auth supplies an account identifier, email address, and, where available, your display name and profile photo. We do not receive your Google password.
- Saved selections. Account-backed saved filters and private Custom Airport Boards include their names, airport, criteria, and any My Flight anchor you select. Older browser-only presets and display preferences may remain on your device.
- Optional click analytics. If you allow analytics, PostHog receives page views, named button interactions, generalized page routes, coarse browser/device categories, referrer hostnames, foreground engagement time and click coordinates on public pages. Private-board identifiers, form contents and account identity are excluded. Session replay is disabled. An anonymous browser identifier and your allow/decline preference are stored locally in this browser, allowing returning-browser and session analysis after permission. This does not identify a named person. Change that choice using the optional analytics controls on this page. Do Not Track and Global Privacy Control prevent this collection.
- Flight alerts. We store alert names, airports, schedules, criteria, and pause state. When delivery is enabled, your verified account email receives matching flight information. Evaluation jobs, matches, and delivery records support processing, deduplication, and retries.
- Payments. When you request a subscription total, Airgeek sends your billing address to Stripe to calculate tax. Quote tokens contain no address; the tax calculation and address evidence are retained by Stripe. Stripe hosts checkout and billing management and processes payment details, billing addresses and applicable tax information. Airgeek stores account-linked Stripe customer and subscription references, subscription status and paid-period information, checkout references, and webhook event receipts to reconcile payments and manage Free or Plus access. Our server handles the billing and payment-state information needed to provide those features, resolve support requests and investigate payment failures. We do not receive full card numbers or card security codes. Payment details are entered on Stripe-hosted pages.
- Feedback and support. Feedback includes your topic, message, airport/view context where available, submission time, and notification status. Guest feedback does not require sign-in or have an account association. Local fixture previews do not transmit feedback. Email support includes your email address and message. Avoid sending passwords, card details, or sensitive personal information.
- Service and security information. Hosting and diagnostics services process request metadata, which can include IP address, browser information, timestamps, page routes, and errors. First-party telemetry records limited interactions, performance, and service outcomes. Feedback abuse controls store counts associated with a keyed hash of the IP address rather than the raw address in feedback tables.
Why we use information
We use account and saved-selection information to provide the features you request; alert criteria and your verified email to provide requested notifications; billing references to process purchases and manage Free or Plus access; and feedback and correspondence to answer questions and improve the service.
We use service information to operate and secure Airgeek, prevent abuse, investigate failures, and understand aggregate usage. Where data-protection law requires a legal basis, we rely on performance of our agreement for requested account, alert, and paid features; legitimate interests in security, reliability, and responding to enquiries; legal obligations for required records; and consent for optional activities where required. You may object to processing based on legitimate interests and withdraw consent for future optional processing.
Cookies and browser storage
Session cookies maintain sign-in. Browser storage remembers settings such as theme and Local/UTC display and may contain older filter presets. Account-backed filters are stored with your account. Clearing site data removes device-local information; signing out does not necessarily clear it or delete account data.
Vercel Web Analytics measures website use without third-party analytics cookies, as described in Vercel’s privacy documentation. Sentry collects errors and sampled performance diagnostics. These services are distinct from the cookies needed for sign-in.
Optional click analytics, if offered, are controlled through the analytics preferences shown in the application. Declining optional measurement does not remove access to the flight boards. You can also use browser controls to remove stored site data or restrict cookies; restricting session cookies can prevent sign-in.
Services involved and sharing
- Google authenticates your account and may serve your profile photo. Support messages sent to our Gmail contact are handled by Google’s email service.
- Supabase provides authentication and database storage for accounts, saved selections, billing references, alert processing, feedback, and service records.
- Vercel hosts the application and provides hosting logs and Web Analytics.
- Sentry receives errors and sampled performance diagnostics. Application filters reduce identity, headers, cookies, request bodies, private content, and URL query information in diagnostic payloads.
- Stripe processes payments, subscriptions, customer billing management, and tax calculations where enabled. Payment information is entered on Stripe-hosted pages.
- Resend delivers enabled flight-alert and feedback notification emails. It receives recipient addresses and message content. Feedback notifications go to our configured support inbox; flight alerts go to the requesting account’s verified email.
- PostHog, when optional click analytics are enabled, measures named control interactions and public-page click heatmaps after permission. That integration excludes form contents and private selection details and does not enable session recording.
AeroDataBox supplies shared airport activity through server-side requests, including through RapidAPI. Your Google identity, email address, and private criteria are not sent as part of those flight-data requests. Airport activity and Events history are shared flight information rather than a record of your physical location.
We do not sell personal information or use it for targeted advertising. We may disclose information where necessary to meet a legal obligation, protect the service or others, or handle a business transfer subject to applicable protections.
Providers may process information in the United States and other countries. The location depends on the service and project configuration and may differ from where you live. Contact us for information about the processing locations and transfer arrangements relevant to your request. Provider handling is also described in their privacy notices.
Retention and deletion
Account records and saved selections remain while needed to provide your account. You can delete saved filters and boards through their controls, pause or delete alerts, and request account deletion through our contact email, including when account controls are unavailable. Support can assist with the process. Deletion is subject to records needed for legal obligations, payment reconciliation, security, and resolving disputes. Deleting an account does not erase records Stripe is required to retain.
Alert processing retains pending evaluations until completion. Its cleanup removes completed evaluations after seven days, completed email records after 30 days, and old match keys after 32 days. Operational alert metrics and health samples are pruned after seven days and alarm history after 90 days. Delivery records awaiting reconciliation remain until reviewed. These cleanup periods apply when scheduled processing runs; an interruption can delay removal. Shared airport observations can remain for other users.
First-party diagnostics cleanup removes detailed telemetry older than 24 hours and hourly summaries and operational alert history older than 90 days when maintenance runs. Provider-hosted diagnostic logs follow each provider’s configured retention. Backup copies expire or are replaced under the backup process and may outlast active records; if a backup is restored, applicable deletion requests must be reapplied.
Feedback and support correspondence are retained while needed to investigate and resolve the request, prevent repeated abuse, or maintain a necessary record of a decision or dispute. Our support process calls for reviewing retained messages and removing information no longer needed for those purposes; automatic age-based feedback deletion is not implemented. Feedback rate-limit counters older than 48 hours are removed during retry processing. Because guest feedback is not linked to an account, account deletion does not automatically identify or delete it; include its submission reference when requesting removal.
Billing records are kept as needed for subscription management, accounting, tax, fraud prevention and dispute handling, including any legally required retention. Account deletion removes account-linked application records through the deletion process, subject to necessary retained records; it does not erase records Stripe must retain. Refund, cancellation and support records may be retained to resolve the request and document the outcome. We do not promise immediate deletion from provider systems or backups. Applicable deletion requests must be reapplied if a backup is restored.
Device-local information remains until you remove it or clear site data. Deleting server information does not clear your devices.
Your choices and requests
You can browse public airport activity without signing in. You can manage saved selections and alert delivery from their controls and cancel renewal through Manage billing.
Depending on applicable law, you may request access, correction, deletion, a copy or portability of your information, restriction of processing, or object to processing. Where processing relies on consent, you may withdraw it without affecting earlier lawful processing. You may complain to the data-protection authority where you live or work or where an alleged infringement occurred.
Email us with the request type and the account email or feedback reference involved. We may verify your identity to protect your information. Do not send passwords, payment-card details, or identity documents unless a secure verification method has been agreed. We respond within the periods required by applicable law and explain any permitted extension or reason we cannot fulfil a request.
Email airgeekjx@gmail.com for support, privacy questions, or account deletion requests.
Changes to this notice
Updates appear here with an effective date. We communicate material changes as required by applicable law.
For flight-data provenance and limitations, see Data Sources & Limitations. Subscription and cancellation rules appear in the Terms of Use.