Legal
Privacy policy
What we hold, why we hold it, and who else sees it. Written to be read, and specific enough to be checked.
Who this is between
FlightWay is operated by Hughes Technology LLC ("we", "us"). Questions about anything on this page go to admin@flightway.app and are answered by a person.
There are two different relationships here, and the difference matters. When you visit this website, we decide what is collected. When your flying club uses FlightWay, the club decides what member data goes in and what it is used for, and we process it on the club’s behalf and under its instructions.
This website
- Google Analytics runs on the public marketing pages only, under measurement ID G-8G7ZS9WH4X. It sets its own cookies and records page views and a small number of events (a call to action clicked, a checkout started, a signup completed). It is not loaded anywhere inside the logged-in app.
- A first-party event record. We record page views and call-to-action clicks in our own database with no cookie. The session identifier is a random value held in the browser tab’s sessionStorage and it dies with the tab. It is not linked to you across sites or across visits.
- Server logs. Our web server records requests, including IP addresses, as any web server does. They are used for security and diagnosis.
- Email you send us. If you email or request a quote, we keep the correspondence so we can answer it.
The logged-in application carries no third-party analytics and no advertising trackers of any kind. Members did not sign up to have anyone else observe their flying, so nobody else does.
What the application holds for a club
| Category | Examples | Why |
|---|---|---|
| Member identity | Name, email address, phone number, role and member class | To sign members in, bill the right person and send them what they asked for |
| Aviation credentials | Certificate type and number, medical class and expiry, flight review expiry | Because clubs gate booking on currency, and members ask to be reminded |
| Operational records | Bookings, flights, hobbs and tach readings, routes, fuel and oil, squawks | They are the club’s operating record and the basis of every charge |
| Financial records | Charges, dues, payments, credits, balances, statements, journal entries | They are the club’s books |
| Documents | Insurance certificates, logbook pages, receipts and anything else uploaded | Because they belong with the aircraft, squawk or member they concern |
| Device records | Passkey public keys, push notification subscriptions, notification preferences | To sign in without a password and to send only what the member asked for |
Who else receives data, and what they get
- Stripe processes payments. Card and bank details are entered on Stripe’s own pages and never reach our servers. Member payments run through the club’s own Stripe account into the club’s own bank account; our own subscription billing is a separate Stripe account.
- Our email provider delivers sign-in links, statements and notifications, and therefore receives the recipient address and the message.
- Twilio delivers SMS, but only for clubs that have bought the SMS add-on and only to members who have opted into that channel and given a number.
- Community ADS-B networks receive the club’s aircraft registrations when the live position feature looks them up. That is aircraft data, broadcast in the clear by the aircraft itself, not member data. No member identity is sent.
- Google Analytics, on the marketing pages only, as described above.
We do not sell data, we do not share it for advertising, and we do not use one club’s data to do anything for another club.
Cookies
The application sets one cookie, for your signed-in session. There are no advertising cookies anywhere on the site. Google Analytics sets its own cookies on the marketing pages; blocking them has no effect on anything you can do here.
How long we keep it
Club data is kept for as long as the club’s subscription is active, because it is the club’s operating and financial record. Financial records in particular have to survive: a ledger that deletes itself is not a ledger. After a club leaves, we keep the data for a short wind-down period so it can be exported, then delete it on request or in the ordinary course. Backups age out on their own cycle.
What you can ask for
- Members: ask your club administrator first. The club controls its own records, and it can correct, export or remove yours from inside the app. If the club cannot help, write to us and we will.
- Clubs: export the full journal, flights and roster from inside the app at any time. Ask us for anything the export does not cover.
- Anyone: ask what we hold about you, ask us to correct it, or ask us to delete it, at admin@flightway.app.
Security
Traffic is encrypted in transit. Members sign in with passkeys or a single-use emailed link rather than a shared club password. Uploaded documents are served through short-lived signed links rather than public URLs. The ledger is append-only, so a financial record cannot be quietly altered. No system is perfect, and if something happens that affects your club we will tell you rather than hope you do not notice.
Children
FlightWay is software for a club’s operations and is not directed at children. A club that enrols a junior member is responsible for whatever consent that requires locally.
Changes
If this policy changes in a way that matters, the date at the foot of this page changes and clubs are told by email. Small corrections are just made.
Last updated 18 August 2026.