TheFlightWall Privacy Policy

Effective date: September 11, 2026 Last updated: October 28, 2026

TheFlightWall is operated by AxisNimble Inc., a Delaware corporation ("AxisNimble," "TheFlightWall," "we," "us"). This Privacy Policy explains how we collect, use, disclose, and protect personal information when you:

• visit our website at theflightwall.com or purchase from our online store (the "Site" and "Store");
• use our mobile application (the "App");
• use a physical Flight Wall display (a "Device"); or
• subscribe to TheFlightWall Plus, our optional paid flight-schedule syncing service ("Plus").

This policy forms part of our Store Terms of Service and, for Plus subscribers, our Plus Terms of Service. By using the Site, Store, App, Devices, or Plus, you agree to the practices described here.

How this policy is organized

Part 1 applies to everyone who uses the Site, Store, App, or a Device. You do not need an account for any of these. Unless you create a Plus account, we do not collect your name through the App or Device, and through the App we collect your email address only if you choose to add it to a bug report.

Part 2 applies only if you create a TheFlightWall Plus account. Plus is a separate, optional subscription that requires an account and involves your flight schedule. If you never sign up for Plus, Part 2 does not apply to you.

Part 3 covers changes to this policy and how to contact us.

For any privacy question or request, contact us at privacy@theflightwall.com.

Part 1 — Site, Store, App, and Devices (everyone)

1. Who we are and scope

AxisNimble Inc. is the controller for personal information processed in connection with the Site, Store, App, and Devices (together, the "Core Services"). Part 1 applies to information we process when you visit our Site, buy from our Store, use our App, or connect a Device to our services.

2. No-account model and identification

The Core Services do not require an account, and we never ask for your name or email address in order to use them. The one exception is support: if you send us a bug report from the App, you may choose to include an email address so we can reply to you (Section 3G). Apart from that, the personal information we process for the Core Services is associated with your Device, your App installation (Section 3I), or your network connection, not with a named account.

When you contact us for support or to exercise privacy rights about a Device, we may ask for the Device serial number, MAC address, or another device identifier to verify and fulfill your request.

3. Information we collect

We collect only what we need to provide, secure, and support the Core Services.

A. Purchase information. When you buy a Device, our Store platform and payment processor collect your name, billing and shipping address, email address, phone number, and payment card details. We receive only what is necessary to fulfill and support your order (name, shipping address, contact details, and order details). We never receive your full card number.

B. Device data.

• Device serial number or hardware identifier
• Device MAC address
• Local network IP address
• Public (WAN) IP address, received when the Device connects to our servers
• The name (SSID) of the Wi‑Fi network the Device is connected to, which the Device reports with its status
• Connectivity status, uptime, firmware version, and basic health indicators

C. User-selected configuration data.

• The geographic area you select in the App (coordinates or region) for flight tracking
• Display filters and Device display preferences

We do not collect continuous or background location from the Device or the App. If you allow the App to access your phone's location, the App uses it only to place your Device's area: when you tap the "Use my location" button on the map, and when you add the first circular area to an empty map, in which case the App uses your phone's current or last known location without asking again. Depending on the permission you grant, this location is precise or approximate. When you save the area, its centre, which can be that exact location, is stored with your Device configuration and the App installation identifier. You can move the area at any time, and you can set an area without location access by moving the map or entering a location manually.

On Android, the App also asks for location access during Device setup, because Android requires it to find and join your Device's Wi‑Fi network. The App does not send your location to us for that step, but if you granted access then, the App can later use your location as described above.

D. Wi‑Fi setup information. During setup, the App sends your Wi‑Fi network name (SSID) and password directly to the Device so it can join your home network. This is transmitted only between your phone and the Device, and the Wi‑Fi password is never transmitted to or stored on our servers. After it joins, the Device reports the network name with its status (Section 3B).

E. Site and App usage data. IP address, approximate location derived from IP, browser type, operating system, device type, access times, pages viewed, referring address, and general log information.

F. Device diagnostics. Limited diagnostic information from the Device (uptime, connection status, error logs) to monitor performance, find bugs, and improve reliability. Where feasible this is de-identified or aggregated.

G. Bug reports you send us. If you submit a bug report from the App, we receive the report type and the description you write, the App's installation identifier, your phone's platform and version, the App's version and, if it is running an over-the-air update, that update's identifier, channel, and runtime version, the relevant Device identifier, and — only if you choose to enter one — an email address so we can follow up. Email is optional; leaving it blank does not stop the report from being sent. Bug reports are handled in our support help desk (Section 5).

H. Terms acceptance. When you accept our terms in the App, we record the App's installation identifier, your phone's platform and version, your IP address, and the time, as evidence of acceptance. We take your IP address from the App's connection to our servers. Older versions of the App instead find it by first sending a request to ipify (api.ipify.org), a third-party service that receives your IP address with that request and returns it to the App; the App then sends it to us.

I. App installation identifier. The App creates an installation identifier and sends it with its requests to our servers, for example when it saves your Device configuration, records terms acceptance, sends a bug report, looks up airports or airlines, registers for notifications, or reports in-app message events. From App version 4.0, a new installation identifier is a one-way hash of an identifier that your phone's operating system gives our App (the identifier for vendor on iOS, the Android ID on Android). We do not receive the operating-system identifier itself. Because of this, the installation identifier can stay the same if you delete and reinstall the App. An App that already had an installation identifier from an earlier version (a random value) keeps using it.

J. Push notifications (optional). Notifications are off unless you turn them on in the App. If you turn them on:

• your phone gets a push token from Apple Push Notification service (iOS) or Google Firebase Cloud Messaging (Android, which also creates a Firebase installation identifier), and the App sends it to Expo's push notification service in exchange for an Expo push token (Section 5);
• the App sends us the Expo push token, a random credential that the App creates and keeps on your phone (we store only a one-way hash of it), and a notification profile: platform, App version and over-the-air update identifier, App language, the country or region code from your phone's language and region settings (not your location), the number and models of Devices set up in the App, and your Plus subscription status (none, active, or lapsed);
• the App registers the Devices set up in it for notifications: it sends each Device's key, and we store the Device identifier with a one-way hash of that key, so that we can ask you to approve a request to link one of those Devices to a Plus account.

We use this information to send the notifications described in the App (requests to approve linking your Devices, and product announcements, which may include announcements about Plus) and to choose which phones receive which announcement. We keep a record of each notification we send and of the App installations and push tokens it was sent to. You can turn notifications off at any time in the App or in your phone's settings.

K. In-app messages. The App can show messages from us. When a message is shown, dismissed, or one of its buttons is tapped, the App sends us that event, the message identifier, and the App installation identifier. We store the event with a keyed one-way hash of the installation identifier instead of the identifier itself, and use these events to count how many App installations viewed, dismissed, or tapped each message.

L. Camera. The App asks for camera access only to scan the QR code on a Device during setup; you can enter the Device's details manually instead. The QR code is read on your phone, and the App does not save camera images or send them to us. On Android, the App reads the code with Google ML Kit, which sends Google diagnostic and usage information about the scanner (such as device and app information, a per-installation identifier, performance metrics, and error codes), but not camera images or the content of the code (Section 5).

4. How we use information

Device operation. Connect and authenticate the Device; fetch and display flight data for your selected area and filters; deliver firmware and software updates.

Security and service integrity. Keep the service connected and stable, prevent abuse, detect anomalies, and troubleshoot.

Orders, support, and communications. Fulfill and support your order; respond to support requests; send technical notices, updates, security alerts, and administrative messages.

Notifications and in-app messages. If you turn on notifications, send you requests to approve linking your Devices and product announcements (which may include announcements about Plus), and use the notification profile in Section 3J to choose which phones receive which announcement. Show in-app messages (which may also include announcements about Plus) and count how many App installations view, dismiss, or tap each in-app message (Section 3K), to understand how our messages perform.

5. How we share information

We do not sell, trade, or rent personal information, and we do not share it for cross-context behavioral advertising. We share information only:

• with service providers that act on our behalf under contract — hosting and network providers (including Cloudflare, which carries traffic between the App and our servers and delivers App updates), flight-data providers, our Store platform and payment processor, shipping carriers, and support and diagnostics vendors — who may use it only for the purposes we specify. Support requests and App bug reports, including any email address you choose to give us, are handled in Help Scout, our support help desk;
• with the providers of third-party services the App uses, which receive information directly from your phone when the App uses their service:
  • Expo, Apple Push Notification service, and Google Firebase Cloud Messaging receive push tokens and related identifiers to deliver notifications, only if you turn notifications on (Section 3J);
  • on Android, the Google Maps SDK for Android draws the map in the App. When the map is shown, Google receives your IP address, device and App information, a Maps SDK identifier, how you use the map (for example, where it is centred and zoomed), and crash information from the Maps SDK, under the Google Maps Platform terms and the Google Privacy Policy. On iOS, the App uses Apple's maps;
  • on Android, Google ML Kit receives diagnostic and usage information when you scan a Device's QR code (Section 3L);
  • ipify receives your IP address when you accept our terms in an older version of the App (Section 3H);
• for legal and safety reasons: to comply with law or legal process, enforce our terms, or protect the rights, property, or safety of users, the public, or AxisNimble;
• in a business transfer such as a merger, acquisition, or sale of assets, subject to this policy; or
• at your direction or with your consent.

Text-messaging originator opt-in data and consent are excluded from all of the above and are never shared with third parties.

6. IP addresses

When your Device, the App, or your browser connects to our services we automatically receive your IP address. We use it to enable connectivity, maintain stability, prevent abuse, and troubleshoot. IP addresses are retained for the period in Section 7.

7. Data retention

• IP addresses and server logs: up to 90 days, unless needed longer for security or legal reasons.
• Device configuration (area, filters): for as long as needed to operate your Device; deleted on request or when you stop using the service. We may keep minimal records where the law requires.
• Wi‑Fi passwords: never transmitted to or stored on our servers.
• Diagnostics logs: up to 180 days, in de-identified or aggregated form where feasible.
• Bug reports and support conversations: for as long as needed to resolve the issue and keep a support history, and deleted on request.
• Terms-acceptance records: for as long as we need to evidence that the terms were accepted.
• Push notification registrations: a push token and its notification profile are kept while they are in use. When you turn notifications off in the App, the App replaces the token, or the push service reports that the token is no longer valid (for example, after the App is deleted and we next try to send a notification), they are deleted 90 days later, except for the copies kept in the notification and link-request records described below. The Devices registered for notifications are removed when you turn notifications off in the App; if the App is deleted while notifications are on, they do not currently have a set deletion period. A one-way hash of each push token, and of the App's notification credential, is kept without an end date so that a token cannot later be claimed by a different App installation. Records of the notifications we send (including the App installations and push tokens they were sent to) do not currently have a set deletion period; records of requests to approve a Device link are deleted when the requesting Plus account is deleted (Section 18) and otherwise do not currently have a set deletion period.
• In-app message events: 90 days.
• Order records: for as long as required for tax, accounting, warranty, and consumer-protection obligations.

8. Lawful bases (GDPR / UK GDPR)

Where the GDPR or UK GDPR applies, we rely on:

• Contractual necessity — to fulfill your order and provide the Device and App functionality you request (including saving your Device configuration and displaying maps);
• Legitimate interests — to secure our services, prevent abuse, and improve reliability; to show in-app messages and count aggregate message views, dismissals, and taps (Section 3K); and for diagnostic and usage data needed to operate third-party map and QR-scanner components in the App (Sections 3L and 5);
• Legal obligations — to comply with applicable law and keep records of terms acceptance (Section 3H); and
• Consent — where you grant App-level permissions (for example, location or camera access, or opting in to push notifications and the associated notification profile in Section 3J) or where the law requires it. You may withdraw consent at any time in the App or through your phone's settings.

9. International data transfers

We process and store information in the United States. If you are in the EEA or UK and your information is transferred outside your jurisdiction, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses (with the UK Addendum where applicable).

10. Your privacy rights

GDPR / UK GDPR. You may have the right to request access, rectification, erasure, restriction, objection, and portability, and to withdraw consent where processing is based on consent.

CCPA / CPRA (California). You may have the right to know, delete, and correct personal information; to opt out of sale or sharing (not applicable — we do not sell or share for cross-context behavioral advertising); and to non-discrimination for exercising your rights.

Notice at collection. In the past 12 months we have collected these categories of personal information:

• Identifiers (Device identifiers, IP address, an App installation identifier, which can be derived from your phone's operating-system identifier (Section 3I), and push tokens if you turn on notifications; an email address if you choose to give one in a bug report; and, for Plus only, name, email address, and Apple or Google sign-in account identifiers)
• Commercial information (order details; and, for Plus only, subscription details)
• Internet or other electronic network activity (Site and App interactions, including in-app message views, dismissals, and taps; logs)
• Geolocation data (the area you set for your Device, which can be your phone's precise or approximate location when the App uses it to place the area; see Section 3C)
• Professional or employment-related information (for Plus only, your crew schedule, crew role, and default airline)

Where the area you set for your Device uses your phone's precise geolocation, we use and retain it only to provide the Device flight-tracking configuration you request.

Device-based verification. Because the Core Services have no accounts, we may ask for your Device serial number, MAC address, or another device identifier to verify a request about a Device. Plus requests are verified through your Plus account email (see Part 2).

Information held without an account. Records keyed to your Device or App installation — Device configuration, terms-acceptance records, bug reports, push notification registrations, and in-app message events — are not part of a Plus account, so deleting a Plus account does not delete them. To ask us to delete them, email us at the address below and tell us which phone and Device the request is about; we will delete the records we can match to them, except the hashes described in Section 7.

How to exercise your rights. Email privacy@theflightwall.com. We aim to respond within 30 days (GDPR / UK GDPR) or 45 days (CCPA / CPRA), subject to extensions permitted by law. We honor these requests regardless of where you live.

11. Security

We use industry-standard administrative, technical, and physical safeguards designed to protect your information. No electronic transmission or storage is 100% secure. The security of your Device's connection to your Wi‑Fi network depends on the safeguards you apply to your own network.

12. Children

The Site, App, and Devices are not directed at children under 13, and we do not knowingly collect personal information from children under 13. If we learn that we have, we will delete it. You must be 18 or older to purchase from the Store or to use Plus (see Section 22).

Part 2 — TheFlightWall Plus (only if you have a Plus account)

This part applies to you only if you create a TheFlightWall Plus account. Plus is an optional paid subscription that lets pilots, flight crew, and their households sync a flight schedule to a Flight Wall display via our website, the App, and linked Devices. If you use a Device or the App without a Plus account, only Part 1 applies to you.

Plus is currently offered in the United States, and Plus data is stored in the United States. As we open Plus in other regions, region-specific notices will be published alongside this one.

13. Information we collect for Plus

Account and profile information. Email address, name, password (stored in hashed form by our authentication provider — we never see or store your plain-text password), and the country you select during account setup. Your profile can also include your crew role, default airline, and default time zone.

Sign in with Apple or Google. If you sign in to Plus in the App with Apple or Google instead of a password, we receive from that provider an account identifier, your email address (with Apple, this can be a private relay address), and your name if you share it. Google also provides a link to your Google profile picture, which we store with your profile. When you sign in with Apple, we also store an encrypted Sign in with Apple refresh token, which we use only to revoke your Sign in with Apple authorization for the App when you delete your account.

Schedule data. Flight schedule information you add or import, including flights, dates and times, airports and routes, duty periods, and any notes you attach. This can come from:

• Google Calendar import — if you connect your Google account, we access your calendar on a read-only basis to import schedule events (see Section 15);
• Calendar file or URL import — ICS files you upload or calendar URLs you subscribe to;
• Manual entry — flights you add directly.

Linked Device information. Identifiers for the Devices you link to your Plus account, their link status, the display settings you set in Plus, and any custom message you choose to show on your Devices. (The Device configuration that the App saves is described in Part 1 and is not deleted with your account.)

Device link requests. When you ask to link a Device to your Plus account, we may send a notification to phones that have set up that Device in the App and turned on notifications, asking them to approve the link (Section 3J). We keep a record of the request, including your account identifier, the Device identifier, and the App installations and push tokens the request was sent to.

Billing information. Subscriptions are processed by Stripe, including a subscription you start from the App on Android or on iPhone in the United States (where the App opens Stripe's checkout page and you enter your payment details on that page, not in the App), or are billed by the Apple App Store or Google Play when purchased as an in-app purchase in the App, where we use RevenueCat to validate those purchases and keep your subscription status in sync. We do not receive or store your full card number; we store your subscription status, plan details, and store or payment transaction identifiers.

Support communications. If you email us, the contents of your message and your contact details are handled in our support help desk (see Section 17).

Technical data. Standard server logs (IP address, browser type, timestamps) generated when you use Plus, used for security and operations.

We do not use third-party advertising trackers or analytics pixels in Plus. (How the App measures in-app messages is described in Section 3K.)

14. How we use Plus information

We use Plus personal information to:

• provide the service: sync, parse, and display your flight schedule on your linked Devices;
• create and manage your account and authenticate you;
• process subscription payments and manage entitlements;
• send transactional service emails (for example, account verification and schedule re-sync notifications);
• ask the phones that have set up a Device you link to approve the link (Section 13);
• choose which App notifications to send: when the App on your phone registers for notifications, it includes your subscription status (none, active, or lapsed), and we use that status to decide which announcements (including announcements about Plus) to send to which phones (Section 3J);
• provide customer support;
• secure, maintain, and improve Plus; and
• comply with legal obligations.

We do not sell Plus personal information, and we do not share it for cross-context behavioral advertising.

15. Google user data

If you choose to connect Google Calendar, we request the read-only Google Calendar scope (calendar.readonly) and use it solely to read calendar events so we can import your flight schedule into Plus. Specifically:

• We access calendar event data (event titles, descriptions, times, and locations) only to identify and import schedule entries you choose to sync.
• We store the resulting schedule entries in your account, along with the tokens needed to keep your schedule in sync. Refresh tokens are stored encrypted.
• We do not use Google user data for advertising, and we do not sell it.
• Humans do not read your Google Calendar data except with your explicit consent (for example, in a support case you initiate), where necessary for security or debugging, or where required by law.
• You can disconnect Google Calendar at any time from the import settings, which stops further access; you can also revoke our access from your Google Account permissions.

TheFlightWall Plus' use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

16. Automated schedule parsing (AI)

To convert imported calendar events into structured flight entries, the text of imported events is processed by OpenAI, acting as our service provider under a signed data processing agreement. This processing is limited to parsing your schedule; the data is not used by us or, per that agreement, by OpenAI to train AI models. OpenAI retains the submitted text for 30 days for abuse and misuse monitoring, then deletes it. You can always review, correct, or delete the parsed results in Plus.

17. How we share Plus information

In addition to the legal, safety, and business-transfer circumstances in Section 5, we share Plus personal information only with:

• Service providers that process data on our behalf under a data processing agreement (DPA). Each provider's DPA is linked below:

• Data sources, sign-in providers, and app stores that act under their own privacy policies rather than as our processors:
  • Google provides your calendar data to us only if you connect Google Calendar (Section 15), under the Google Privacy Policy.
  • Apple (Sign in with Apple) and Google (Google sign-in) confirm your identity if you choose to sign in with them (Section 13), under the Apple Privacy Policy and Google Privacy Policy. When you delete your account, we ask Apple to revoke your Sign in with Apple authorization for the App.
  • Apple and Google Play bill and manage mobile in-app subscriptions under their own terms (Section 13); see the Apple Privacy Policy and Google Privacy Policy.

18. Plus data retention

• Schedule data is retained for as long as your account is active — historical reference is a core function of Plus.
• If you delete your account, personal data is removed from our primary systems within 30 days and ages out of encrypted backups within our backup-retention window.
• Accounts inactive for an extended period (24–36 months) may be flagged for deletion or anonymization.
• You can delete individual schedule records at any time.

19. Your Plus choices and rights

In addition to the rights in Section 10:

• Access and export: you can request a copy of your identity and schedule data in a portable format from your account settings or by emailing us.
• Correction: you can edit your profile and schedule data in Plus.
• Deletion: you can delete your account from the App or website, or by emailing us; deletion follows the timelines in Section 18. Deleting your account does not delete the Part 1 records keyed to your Device or App installation; see "Information held without an account" in Section 10.
• Email: transactional emails are part of the service; any marketing email will include an unsubscribe link.

We verify Plus requests through your account email.

20. Plus security

In addition to the safeguards in Section 11, for Plus we encrypt data in transit (TLS) and at rest, enforce per-user row-level access controls in our database, restrict internal access on a least-privilege basis with multi-factor authentication, and encrypt stored OAuth tokens. If a breach affecting your personal information occurs, we will notify you and the relevant authorities as required by law.

21. Plus is US-only for now

Plus is currently offered in the United States and Plus data is stored in the United States. Depending on your state of residence you may have additional rights under state privacy laws (such as the right to know, delete, or correct personal information, and the right to non-discrimination for exercising those rights). We honor these requests regardless of state.

22. Age requirement for Plus

Plus is intended for users 18 years of age or older. We do not knowingly collect Plus personal information from anyone under 18. If you believe someone under 18 has created a Plus account, contact us and we will delete it.

Part 3 — General

23. Changes to this policy

We may update this policy from time to time. We will post the updated version at this URL with a revised "Last updated" date, and for material changes we will notify you — by email or in the App or Plus where we have a way to reach you — before they take effect.

24. Contact

AxisNimble Inc. (TheFlightWall) Email: privacy@theflightwall.com General inquiries: contact@theflightwall.com