ORBIT / PRIVACY & YOUR DATA

Your journeys. Your choices.

How ORBIT stores your information and how to manage it.

Updated 25 October 2026

Website measurement and hardware updates

ORBIT counts website page views, app and tour opens, and successful Atlas and import save actions. Reports group these by day and a fixed set of campaign labels. We do not attach names, email addresses, travel records, full referring URLs or account identifiers to those counts. Counts are actions rather than unique visitors, and may include repeat visits or automated traffic.

We also count accepted invitations and the first locally saved flight when the saved flight history was empty. These fixed action counts can be attributed to the public entry page within the same 30-minute tab window. Private invitation pages are excluded. First-flight counts can repeat after deleting all saved flights or on another device, and omit cloud-only saves.

We also count activations of the TestFlight beta link, including repeated clicks. These aggregate action counts do not tell us whether someone installed the app or joined the beta.

Campaign labels and a public entry-page path may be kept in this tab’s session storage for 30 minutes to connect a visit with later actions. Recognized search and AI referring sites become fixed source labels; full referring URLs are not retained. Entry-page and TestFlight actions are counts, not unique visitors or proof of an AI citation. No advertising cookie or persistent visitor identifier is created. Measurement is disabled when your browser sends Global Privacy Control or Do Not Track. Aggregate counts are retained for up to 180 days.

When usage diagnostics are enabled, ORBIT counts roster import starts, readable previews, saves and broad failure categories. It records only the general source type, such as a PDF or calendar file. These checkpoints exclude filenames, airline names, routes, dates, flight numbers, roster contents and error messages.

Signed-in app diagnostics can record an account identifier, a temporary session identifier, the feature in use, engaged time, app version/platform and fixed error codes. The restricted ORBIT administrator dashboard uses these to understand usage and investigate reliability. Private messages, raw schedules, flight numbers and error-message contents are excluded. Activity records are retained for up to 30 days. Presence sessions are cleared during routine cleanup after 24 hours without activity. Active status is approximate and expires after two minutes without a qualifying signal. You can turn off “Share usage diagnostics” in Settings → Account → Account actions; Global Privacy Control and Do Not Track also disable this collection. Anonymous app visitors are not included in these account-level reports. After account deletion, a coded account marker with no raw account identifier or activity data blocks delayed usage-diagnostics requests for 90 days and is cleared during routine cleanup after expiry.

If you request hardware updates, we store your email, Mini or Pro interest, consent version, request and confirmation times, and campaign labels. Our email provider, Resend, delivers the confirmation link. We add you to the confirmed list only after you confirm. The link expires after 48 hours. Unconfirmed requests are cleared after nine days and confirmed signups after two years, when the service next receives activity. Unsubscribing removes your signup immediately. Keep your confirmation email to use its unsubscribe link, or contact support to have your signup removed.

Abuse prevention uses a salted hash of the connection address that changes each day, and a separate hourly email hash for signup limits. Raw addresses are not stored in these measurement or rate-limit tables. Limit records expire within two days. Expired records are excluded from reports and cleared when the service next receives activity. No marketing email is required to use the app.

What ORBIT stores

Why this information is used

Boarding-pass barcodes are decoded on your device. Passenger names, booking references and raw barcode data are not imported. Only the flight details you review and save enter your travel records.

These records let ORBIT show your atlas, sync supported data, organize photos, follow a permitted flight and connect the screens or people you choose. Browser storage and session cookies keep settings and signed-in or paired-display sessions working.

If you choose Current location as your globe's starting place, your device asks for location permission and uses the result to center the globe. This does not start background location tracking. The current-location result and this screen's camera view stay on the device. Separately, when you save a selected place or point of interest while signed in, its name and exact latitude and longitude are saved with your account for your Atlas or photo destinations. Your chosen home airport is also account data. When you use an external map service, its map requests reflect the area you are viewing.

If Nearby skies is available and you choose an area to search, ORBIT receives the selected area's center coordinates and radius. ORBIT sends the area's geographic bounds to FlightAware to find nearby aircraft and temporarily stores results in a cache shared by requests for that area. Account-linked usage counts enforce service limits. Choosing Current location only to center your globe does not itself start a Nearby search.

The hosting and sign-in services process the request and session information needed to provide those services. Cloud hosting stores account data and photos. When enabled, FlightAware receives flight lookup details to return flight information; map providers receive requests when their map services are used. These services may process information outside your country.

Sharing and connected screens

A shared flight link shows that flight and selected display information. It does not include your destination photo albums. Anyone who obtains the link may be able to open it until it expires or you remove it.

People access follows the permissions attached to an invitation. A paired display is a read-only device for your account. Album access starts off and requires your explicit permission for that display. Link only screens you trust. Photo albums require a connection. Review shared links in Settings → People & sharing → Shared flights and linked displays in Settings → My Mini → Paired displays; manage crew connections in People.

Removing access prevents future access through ORBIT. It cannot remove a screenshot or copy another person already saved.

Widgets and device notifications

In watch-enabled native builds, your paired Apple Watch receives selected saved flight details from your iPhone. Sign-in credentials and boarding-pass barcodes are not sent to the watch. Shared schedules expire after 15 minutes and your own saved schedule after 24 hours. Signing out sends a clear request, which reaches the watch when it reconnects.

The iPhone and iPad app stores a device identifier and, when you enable notifications, an Apple Push Notification service (APNs) device token linked to your signed-in account. ORBIT uses these to deliver your chosen updates through Apple. A notification can contain a shared person's name and flight or schedule details; your system preview settings determine whether they appear on the Lock Screen.

Widgets use a separate, read-only credential tied to your app session. The app and its widget extension share a protected local cache containing selected names, routes, dates, times and recorded flight status. Widgets can display these details on your Home or Lock Screen. iOS privacy settings and your chosen widget placement control their visibility.

Your app notification choices and time zone sync with your account. Optional daily overviews use saved schedules and current sharing permissions; optional display connection alerts use the connection status of your own paired displays. App update history is available for up to 30 days. Home can also show authorized shared flight and schedule updates for up to 30 days, and personal-flight updates for up to seven days. ORBIT stores account-linked read markers for these items. Reading an update does not acknowledge a schedule change for the person who shared it. History and read markers are removed when you delete your account; removing sharing prevents future access to shared updates. You can choose discreet push previews and quiet hours for routine app updates.

Current sharing permissions are checked whenever widget data is fetched and before a notification is sent. Cached shared schedules expire after 15 minutes. Updated widget builds may keep your own saved schedule for up to 24 hours during a connection failure, with an update time and saved-schedule label. Older widget builds may clear it sooner. Signing out clears this device's widget credentials and cache and revokes its notification registration. Removing sharing prevents future access; previously cached shared details may remain until their expiry or next successful refresh.

Manage device notifications in Settings → Notifications → Phone & widget setup and sharing preferences in People. Disable notification previews or remove a widget if you do not want travel details visible when your device is locked. ORBIT cannot remove a notification or screenshot someone has already received.

Usage and product diagnostics

ORBIT counts provider requests, failed requests and cache reuse per account and month to enforce account limits. It also keeps limited daily counts of saved schedules, displays and photos. These counts do not contain roster text, photo contents or captions; daily product counts are retained for about 90 days and account request counts for about a year. Account deletion removes these records.

To measure flight-data costs, ORBIT also keeps records with coded account and flight references, request categories, times and cost estimates. Request and alert-callback records are kept for up to 45 days; flight and viewer timing summaries for up to 90 days. They do not contain roster text, photos or message content. Account deletion removes records linked to your account. A minimal coded deletion marker is retained for up to 90 days to prevent delayed records from restoring that link. Provider cost totals without an account identifier may remain within those retention limits.

Managing, correcting and deleting data

Use a person's controls in People to report shared content or block them. A report opens the support form with an item reference; you choose the description before submitting. Blocking stores the two account identifiers and a label until you unblock or delete your account. It removes existing connections and prevents new connections between the accounts. Manage your blocks in Account → Account actions → Blocked people. Unblocking does not restore old sharing permissions.

Edit journeys, schedules and albums in their respective sections. Delete destination photos in the album viewer and unused custom display photos in Settings → Data & help → Backups & restore → Manage saved display photos. The same settings section includes Settings → Data & help → Backups & restore → Back up or restore my data, individual exports, and journey deletion. Open Settings → Account → Account actions for Delete account when signed in with an ORBIT account, or Delete all my ORBIT data for legacy sign-in. Full backups include saved destination and custom display copies and crop settings. Keep every backup part and your camera originals separately.

Delete account permanently deletes your ORBIT sign-in account, ends its sessions and removes its stored ORBIT content, photos and connections. The legacy Delete all my ORBIT data action removes ORBIT content associated with that sign-in. Both actions clear this browser’s saved journey record. Screen appearance preferences may remain in browser storage. A minimal empty synchronization record is retained to prevent stale devices from restoring deleted content. Other devices can retain local copies until they reconnect; clear their site data separately if needed. This action does not delete your sign-in provider account. For Sign in with Apple, we also request revocation of ORBIT’s authorization. If Apple is unavailable, an encrypted token with no profile details is retained for up to 30 days to retry cleanup, then removed. The deletion result shows any remaining Apple cleanup. The app also clears this device’s saved schedules, widgets and Live Activities.

Saved account content is kept for the features you use until you remove it. Technical records maintained by hosting or sign-in providers are subject to their own retention processes.

Questions or privacy requests

The direct support form sends your message, topic and optional reply email to ORBIT’s private support inbox. Signed-in messages are linked to your account so account-data deletion can remove them. A daily salted network or account identifier limits spam; the form does not store raw IP addresses. Diagnostics are included only if you choose to paste them. Requests older than 180 days are removed when the form next receives a message; you can ask us to delete one sooner using its reference number.

Email orbitdisplays@outlook.com to ask about accessing, correcting or deleting your ORBIT information. Include the type of request and your account email when relevant; do not send passwords or sign-in codes.