SkyNexus Limited (Company Number 17114302) is the data controller responsible for your personal data. We are a private company registered in England and Wales at 38 Salisbury Road, Worthing, BN11 1RD.
We are registered with the Information Commissioner’s Office (ICO) under registration reference ZC111428.
Our Data Protection Officer is Noel Doherty. If you have any questions about how we handle your data, you can contact us at privacy@skynexus.voyage.
This policy covers the SkyNexus iOS app and the SkyNexus website. SkyNexus lets you reconstruct and keep your personal flight history — a private archive of the flights you have taken, built from your Apple Wallet passes, a CSV file you import, booking emails you forward, or flights you add by hand. It also lets you keep a private log of aircraft you have spotted.
We collect what we need to give you your flight archive and your spotting log, a record of how you use the app so that we can improve it, a note of the milestones your archive reaches and of the flights we match to an aircraft, the state of any SkyNexus Plus purchase, whether your installation of the app came from one of our adverts on the App Store, and — if you allow notifications — the device token Apple issues so that we can send them. We do not use your data to track you across other companies’ apps or websites, we do not give advertising networks your data (the one question the app asks Apple’s advertising service is described below), and we do not sell your data.
| Data | What it is | Why | Lawful basis |
|---|---|---|---|
| Name & email (Sign in with Apple) | Your name and email are provided by Apple when you first sign in. If you choose Apple’s Hide My Email, we receive and use only the private relay address. Apple returns these to us once, at first sign-in only. | To create and secure your account and to contact you about your account. | Contract (GDPR Art 6(1)(b)) |
| Account identifier | A user ID that links your account to your saved flights. Sign in with Apple is the only sign-in method; there is no password. | To operate your account and associate your flight history with you. | Contract (GDPR Art 6(1)(b)) |
| Your flight history (the content you create) | The flights you add, and the details shown on your cards — flight number, date, route (origin/destination), airline, aircraft type, and similar travel facts — together with what you add to a flight yourself, such as a note, a postcard title and style, a name you give to a place and where it is, your seat and cabin class, and whether you have flown it yet. These are saved to your account alongside the flight. | This is the product: your personal, private flight archive. | Contract (GDPR Art 6(1)(b)) |
| Flight details you bring in | There are four ways to add a flight. From Apple Wallet — you share a boarding pass from your Wallet and the app reads the travel details from it on your device. From a CSV file that you import. By forwarding a booking confirmation email to a private address the app generates for you. By typing the flight in yourself. When you type a flight, we may look it up with a flight-data provider, sending it only the airline code, flight number and date — nothing that identifies you. A pass or a booking email can also carry sensitive details such as your name, booking reference (PNR), seat or sequence number. The app does not pull your name, booking reference or sequence number out of a pass or an email in order to keep them. A short, fixed list of details is deliberately kept, because each one makes your own record richer: your seat, the aircraft’s registration, and — when the flight came from an Apple Wallet pass — your boarding group, the flight’s status, and any reason the airline gave for that status. Your seat and the registration are shown to you on your own card. And nothing of that kind — including the seat and the registration — is ever included in a card you share (see “Sharing a flight card”). All of it is deleted when you delete your account. | To build your archive from records you already have, rather than making you type everything twice. | Contract (GDPR Art 6(1)(b)) |
| Your spotting log (the content you create) | While Spotter is switched on, your spotting sessions are backed up to your account automatically — there is no separate backup switch, and it happens whenever the app goes into the background. What is saved is: the date and, if you record one, the time; the place name you gave the session and the coordinates of where you were standing; any notes you wrote; and the aircraft you logged (registration, type, airline, flight number, route, serial number and the direction you noted, where you recorded them). Turning Spotter off stops it. In the app, only you can see your spotting log. It is not shared with anyone beyond the providers that store our data unless you choose to share a sighting (see “Sharing a sighting”), and it is never used to advertise to you. All of it is deleted when you delete your account. | To keep your spotting log safe and let you recover it if you lose or change your phone. | Contract (GDPR Art 6(1)(b)) |
| Usage data (how you use the app) | A record of what happens inside the app — sessions starting and ending; the steps of adding a flight, including the point where you stopped if you didn’t finish; imports; opening a share preview; opening the app from a notification; tapping a detail on a card; seeing the Plus screen or starting a purchase; and seeing or tapping one of our own in-app promotions. Each event is saved against your account, along with the app version, a session identifier, and a little detail about the event itself — which promotion you saw, how you were adding a flight and the step you reached, whether it was your first, and whether something failed. It records what you did in SkyNexus and nothing you do anywhere else, apart from the App Store advert answer described under “How you found SkyNexus”. The in-app promotions are our own — no advertising network is involved in them, and none of this is shared with advertisers or used to target you. We keep it for as long as you have an account, and everything tied to your account is deleted when you delete it. | To understand how the app is used and improve it. | Legitimate interest (GDPR Art 6(1)(f)) |
| Notifications | The app asks first, and then iOS asks. If you allow notifications, iOS issues a device token for your phone and we store it against your account, with the platform, whether it came from a development build or a release build of the app, the date it was stored, and a date that is refreshed each time the app opens while notifications are allowed and each time Apple accepts a notification from us for it. We use the token to send two kinds of notification: a milestone (your 10th or 100th flight), and an enrichment (when we have worked out which aircraft you flew on). A notification carries the milestone reached or the aircraft type, and the airline, flight number, route and date of that flight. Apple delivers it, and may hold it for up to 24 hours if your phone is offline. Whether or not you allow notifications, when your archive passes 10 or 100 flights, or one of your flights is verified against our aircraft records, we record which flight that was, when, and what happened to the notification — sent, not sent, or superseded. If we tried to send one, we also record, for each of your devices, when, the build it was for, whether it went, Apple’s response and any identifier Apple assigned it. We do not keep the text we sent. Opening the app from a notification is recorded as usage data. Your answer to the app’s question is kept on your phone, and your answer to iOS is held by iOS; we keep no record of either beyond the token itself, which we only receive if you allowed them. Turning notifications off in iOS Settings means your phone will not show them, but until the token is removed (see below) or you delete your account we may still hand a notification to Apple and record that we did. Signing out of the app removes the token for that phone; if Apple tells us the token is no longer registered to your phone, we delete it; and you can email privacy@skynexus.voyage to have it removed. Every token registered to your account, and the records above, are deleted when you delete your account. |
To tell you about a milestone in your archive, or that we have found the aircraft you flew on. | Legitimate interest (GDPR Art 6(1)(f)) for storing the token, sending, and the records above. Whether a notification is shown is controlled by the permission you give iOS, which iOS holds; we receive no record of it beyond the token |
| SkyNexus Plus (if you buy it) | Apple takes the payment; we never see your card or payment details. When you buy while signed in, the app gives Apple an identifier for your SkyNexus account, so that Apple’s later messages about the purchase can be matched to it. Apple then tells us — through the app, and through notifications its servers send to ours — which product you bought, its status, when it renews or ends, whether a free trial was used, whether it was a test purchase, and Apple’s transaction numbers for it. We store these against your account, with whether you currently have Plus. If we have given you Plus free of charge, we record that, the kind of badge that comes with it, the reason, any note we add, who granted it, when, and when it ends. If we offer you free Plus before you have an account, we hold the email address you will sign in with, use it to apply the offer when you sign up, and delete it when you delete your account; if you never sign up, ask us and we will delete it. Your subscription records, and our log of Apple’s notifications about them, are deleted when you delete your account. | To give you the Plus features you paid for, and to end them when your subscription ends. | Contract (GDPR Art 6(1)(b)) |
| How you found SkyNexus (App Store adverts) | When a new installation of the app first opens, it asks Apple’s advertising-attribution service whether the app was installed after one of our adverts on the App Store. The question uses a one-off token that iOS creates for this purpose; it does not use the Advertising Identifier, and Apple’s answer contains no name, email address or device identifier. If the answer is yes, it describes our advert — our account with Apple, the campaign, ad group, keyword and advert, where on the App Store it appeared, whether it was a first download or a re-download, when it was seen or tapped, and the country or region. Otherwise the answer is no, or that it could not be worked out. The app keeps asking over its first few launches until it has one answer, then stops for good. If the app can tell it was already in use on the phone before this feature arrived — because it holds your flights or you are signed in — it records that and asks Apple nothing. We save the answer as a usage event, linked to your account once you sign in, and delete it with your account. We use it only to judge whether our adverts are worth paying for; beyond Apple, which answers the question, and the providers that store our data, it is not shared with anyone, and it is not used to target you. | To measure whether our App Store advertising works. | Legitimate interest (GDPR Art 6(1)(f)) |
No tracking. The app contains no third-party advertising, analytics, or crash-reporting SDKs. We do not use the Advertising Identifier (IDFA) and we do not present the App Tracking Transparency prompt. The app does use Apple’s own advertising-attribution service, during its first launches after installation and until it has an answer, to learn whether you arrived from one of our App Store adverts — see “How you found SkyNexus” above. While Spotter is switched on, the location you record for a spotting session is saved to your account — it is used to show you where you were standing, it is not shared with anyone beyond the providers that store our data unless you choose to share a sighting (in which case only a rounded pin is shown — see “Sharing a sighting”) or ask for an export of your own log, and it is never used to track you or to build a profile. In App Store terms, your data is not used to track you.
If you choose to share a flight card, the shared version is deliberately stripped of the personal details on your own record, with one deliberate exception we want you to know about: your @handle is shown on the image. It is there so that a card cannot be passed off as someone else’s, and apart from anything you choose to write yourself, it is what points back to you. Apart from that, a shared card carries only non-identifying travel facts — such as the flight number, date, route, airline, aircraft type, and card styling. It never includes the name you signed in with, your booking reference, seat, frequent-flyer number, passport or identity data, or the aircraft’s registration. Milestone captions (for example “100th flight”) never include your name.
If you choose to add your own words to a shared card (such as a caption) or set a display name, that text is content you are choosing to make visible to others, and it is governed by our Terms of Use. To help keep shared content safe we screen submitted text against a list of prohibited terms, and you can report anything abusive — see Support & Safety.
If you choose to share a sighting from your spotting log as an image, it shows your SkyNexus @handle, the day, the aircraft — its type, and its registration and serial number where you logged them — the airline, flight number, route and direction where you logged those, and a pin for where you were standing, rounded to about a kilometre. Your notes, the name you gave the place, the time and your exact position are left out. The image is not sent anywhere until you choose where to share it.
On our website we use Cloudflare Web Analytics to understand how visitors use the site. Cloudflare states that it sets no cookies and does not fingerprint visitors to produce them. What we see is aggregate — such as visits and page views per page, where visitors came from, the browser, operating system and country, and how quickly pages loaded. We see nothing that identifies you individually. Cloudflare receives the request details needed to produce those counts, including your IP address, and keeps them under its own terms. Cloudflare is also our hosting provider and appears in the table below.
The pre-launch waitlist is closed. On 9 September 2026 we deleted every record it held — email addresses, consent records, IP addresses and referral details — from the three places they were stored (a Cloudflare database, our Supabase database and a Smartsheet sheet), and on 12 September 2026 we removed the sign-up service and its database. We hold no live waitlist data. Copies in our Supabase database backups age out within 7 days of the deletion; Cloudflare and Smartsheet may hold their own recovery copies of the deleted database and sheet for a period under their terms; and Resend, which sent the confirmation emails, may keep its own delivery logs under its policy. There is no longer any way to join.
We share your data only with the service providers we need to run SkyNexus. We do not sell your data to anyone. Email you send us is received and stored by our email service provider.
| Provider | Role | Data location |
|---|---|---|
| Apple | Sign in with Apple (authentication). Apple also processes any in-app purchase you make and tells us its status, delivers our notifications to your phone, and answers the app’s question about whether it was installed from one of our App Store adverts. | Per Apple’s privacy policy |
| Supabase | Authentication and the database that stores your account and flight history | EU (Ireland) |
| Cloudflare | Website hosting, DNS and security; website analytics (above); running parts of our service, including importing a CSV file you choose and looking up a flight you type; and receiving the booking emails you forward — the text of the message, up to its full length, is machine-read by a language model running on Cloudflare’s network to pick out the flight details; we do not store the message; Cloudflare handles it to route and read it, and anything it retains is under its own terms | Cloudflare’s global network |
| Resend | Sent the confirmation email when people joined the waitlist, which is now closed; may retain its own delivery logs | United States |
We keep your core account and flight data in the EU (Ireland). Some of our service providers process data outside the UK and EEA. Where data is transferred outside the UK and EEA, Cloudflare’s and Resend’s data-processing agreements incorporate the EU Standard Contractual Clauses and the UK Addendum for those transfers. Apple’s delivery of our notifications is governed by the Apple Developer Program agreement; we do not rely on Standard Contractual Clauses for it.
We keep your account and flight history for as long as your account exists. You can delete your account at any time from within the app (Settings → Delete account). Deletion is immediate and permanent in our live systems: it removes your account and all associated flight records (including any SkyNexus Verified badge history), spotting sessions and sightings, boarding-pass data (including any raw barcode), app events tied to your account, your subscription records and the Apple purchase notifications we hold linked to your account, and any notification tokens, notification records and delivery records, in a single step. We do not keep a shadow or “soft-deleted” copy. Our rolling database backups still hold your data until they age out, within 7 days; what we do keep after that is set out below. We do keep two things that name you or your account, and we keep them for as long as SkyNexus runs: a deletion record — the account identifier that was yours and the time it was deleted — and the @handle you used. We are not going to call either of those anonymous. The identifier is the one that keyed your data, so it is still personal data, and we would rather tell you that than claim more than we can stand behind. We keep the record to show that the deletion happened, and the handle so that nobody else can take a name that still appears on a card you shared. (Legitimate interest, GDPR Art 6(1)(f).)
Deleting your account does not cancel a SkyNexus Plus subscription. Apple manages the subscription, so cancel it first in your iPhone’s Settings (tap your name, then Subscriptions); otherwise Apple may keep charging you.
Three further things are kept without your account identifier, and we would rather say so plainly. Where a flight you added also contributed a provenance record to our reference database of aircraft and flights, that record is not deleted — the link to you is removed from it. What remains describes the flight, not you: which flight record it relates to, the date, the kind of source it came from, and when it was created. It carries no name and no account identifier. We stop short of calling it anonymous: because it keeps a date and a flight, it could in principle still be correlated, and we would rather tell you that than claim more than we can stand behind.
For most of your flights, the flight’s basic facts — airline, flight number, date and route — are also held in a separate table that carries no account identifier and can be shared by everyone who took the same flight. When you delete your account, the link from your account to those facts is deleted, and the facts remain, the same way the provenance record above does. If you want these, or the provenance record, removed as well, ask us at privacy@skynexus.voyage before you delete your account, while we can still tell which are yours.
Apple subscription notifications. While a subscription stays active, and sometimes afterwards (for example after a refund), Apple sends us notifications about it — renewals, expiry and similar. After your account is deleted we still receive and record them. They carry the product and Apple’s transaction references but no account identifier, and once our backups have aged out (within 7 days) we hold no record that connects them to you. We stop short of calling them anonymous: Apple can match those references to your Apple ID. We record each one, with the transaction details Apple sends, so that we never act on the same notification twice. We have not yet set a deletion date for them; we keep them while they serve that purpose and will update this policy when we set one. (Legitimate interest, GDPR Art 6(1)(f).)
Emails you have sent us stay in our mailbox after you delete your account; ask us if you want them deleted.
Our database backups are retained on a rolling basis for up to 7 days. When you delete your account, the live data is removed immediately, and any copies held in backups are no longer available once they age out of that 7-day window.
Under UK GDPR and EU GDPR, you have the following rights over your personal data:
To exercise any of these rights, email privacy@skynexus.voyage. We will respond within one month.
SkyNexus is not directed to children under 13 and we do not knowingly collect their personal data. If you believe a child has provided us with personal data, contact us and we will delete it.
If you are unhappy with how we have handled your data, you have the right to lodge a complaint with a supervisory authority.
In the UK, this is the Information Commissioner’s Office (ICO), Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF. Our ICO registration reference is ZC111428.
If you are in the EU, you may complain to the data protection authority in your country of residence.
We do not use your personal data for automated decision-making or profiling.
We will update this page if our data practices change. The “last updated” date at the top of this page will reflect the most recent revision.