Your Travel Data, Explained.

Account Identity

When you sign in, SkySage receives your email address and, when available, your display name from its managed authentication provider. Those details identify your workspace and keep its records separate from other users.

Profile And Preferences

If you create a profile, SkySage stores the display name, home airport, preferred currency, personal points valuation, and onboarding state you provide. Saved Places store the label, type, and complete address you enter so trip location fields can reuse it.

Portfolio And Research

SkySage stores manual program balances and labels you add. A saved search can include its name, origin, destination, travel dates, cabin, traveler count, optional cash fare, and decision strategy.

Optional Linked-Account Data

If a supported loyalty connection is available and you authorize it, SkySage may store connection and consent status, a provider account identifier, normalized program balances, account labels, expiration dates, and sync status. Manual balances stay separate from linked balances.

Trips, Rides, And Selected Photos

When you save a trip, SkySage stores its stamped flight legs, itinerary details, lodging and confirmation notes, planned rideshare details, and photo-album settings. Photos are uploaded only after you select or capture them; private SkySage copies are stored with the trip and organized by itinerary day. An uploaded file can retain embedded camera time, device, or location metadata unless you remove it before uploading.

While you edit an itinerary, SkySage also keeps a signature-specific draft in browser storage on that device. Starting a different itinerary loads a separate draft. Clearing browser site data removes device-local drafts.

Optional Anonymous Insights

If you turn on Contribute Anonymous Insights in Personalization, SkySage creates pseudonymous records from completed searches and saved trip decisions. These records may include airport codes, cabin, traveler count, trip length and distance, coarse provenance, modeled cost and savings totals, and conventional award CPP. They do not include your email, name, trip name, addresses, confirmation numbers, notes, loyalty balances, payment identifiers, or provider-account identifiers.

For signed-in travelers who have enabled contribution, SkySage may also record allowlisted product actions—such as opening a Sage Guide entry or completing a calculator—with only a coarse result category. Signed-out Guide visitors are not tracked, and Guide search text, calculator inputs, routes, budgets, Wallet data, and Decision Record payloads are never included.

SkySage uses a secret-keyed pseudonymous identifier rather than your account identity in these records. The owner dashboard returns aggregate statistics only, and detailed destination, route, or program breakdowns stay hidden until enough distinct contributors exist. Your personal transfer-adjusted CPP is not mixed into the peer Award CPP benchmark.

SkySage also summarizes limited operational counts from records needed to run the service, such as signed-in accounts, saved-trip adoption, current plan access, connection adoption, and billing-webhook health. Sensitive route, destination, cost, savings, and redemption cohorts use only the optional contribution records described above.

Plan And Billing Records

When you use paid enrollment, SkySage may store the Stripe customer, Checkout Session, payment or subscription status, selected plan, entitlement dates, and the saved trip attached to a Trip Pass. Those records let SkySage provision access, prevent duplicate fulfillment, display billing status, and provide account support.

The public Cash vs. Points Check is available without a SkySage account. It calculates from the cash price, award price, point currency, and other assumptions currently entered on the page.

Those inputs are not saved to browser storage or a SkySage account, are not sent to provider-search services, and are not included in SkySage's signed-in anonymous-insights program. Reloading or leaving the page ends that public comparison.

SkySage relies on a managed authentication provider and Sites infrastructure to deliver the product. When you run a provider search, the route, dates, traveler count, cabin, and currency may be sent to configured flight or award-data providers such as Duffel, Amadeus, or seats.aero.

Checkout and billing management are hosted by Stripe, with Link acting as seller of record for Managed Payments. You leave SkySage to enter payment information on a Stripe-hosted page. Stripe and Link may receive your email address, selected plan, billing details, payment method information, and transaction data under their own privacy terms. SkySage receives limited identifiers and status information needed to confirm payment and manage access, not your full card or bank-account number.

Cash and award quotes you type manually into the cash-to-reward checklist stay in the current browser session. Route, date, passenger, cabin, and selected flight-preference inputs are sent server-side to each configured flight-search provider so it can return matching inventory. API credentials remain server-side.

If you choose to link AwardWallet, you leave SkySage for its consent flow. SkySage requests supported read access and does not ask for your loyalty-program password. External services govern the information they process on their own systems.

If Google Photos or OneDrive linking is configured and you authorize it, SkySage stores an encrypted provider token and sends only photos you select to SkySage-created albums or app folders. Disconnecting stops future access but does not delete albums or files already stored by that provider.

When you use the generic Uber handoff, SkySage copies only the visible pickup address to your device clipboard. A prefilled Uber link receives mapped airport coordinates only and does not change the clipboard. Lyft receives no route parameters, so its clearly labeled handoff attempts to copy the visible pickup, drop-off, local time, and flight context for you to paste and confirm.

SkySage checks The Points Guy's public current-transfer-bonus table to discover dated promotions. It sends no profile or trip data with that server-side check. Editorial bonus data is labeled as unverified and must be confirmed with the bank and loyalty program before transfer.

Provider results can be incomplete, cached, unavailable, or change after retrieval. Always reprice cash fares and verify award availability with the relevant provider before booking or transferring points.

• No card numbers stored by SkySage. Payment-method entry occurs on Stripe-hosted pages; do not type card or bank details into a SkySage workspace or support field.
• No loyalty passwords. Entering a loyalty-program password into SkySage is never required.
• No separate SkySage password. Signed-in access uses a managed authentication provider rather than a password managed by SkySage.

• Edit or remove any Saved Place without changing addresses already stamped into a trip.
• Remove a manual balance or saved search individually from the workspace.
• Delete an individual saved trip and remove its private SkySage photo copies from the Trips page.
• Disconnect AwardWallet to remove the connection and its synced balances from SkySage. This does not delete your AwardWallet account.
• Disconnect a photo provider to remove its SkySage token. Existing external albums and files remain under that provider's controls.
• Turn Contribute Anonymous Insights off at any time. SkySage removes your pseudonymous search, trip-fact, redemption-observation, and coarse product-use event records; previously calculated de-identified aggregate statistics cannot be separated back into individual contributions.
• Choose Delete all SkySage data in your workspace profile to delete your SkySage profile, Saved Places, balances, saved searches, saved trips, private photo copies, and linked-account metadata. Your secure sign-in session remains active.

Trip, photo, and workspace deletion removes the related user-visible SkySage metadata immediately and durably queues each underlying private photo object for removal. If private storage is temporarily unavailable or an upload was already in flight, SkySage retains only the minimum storage-deletion reference needed to retry; that cleanup record remains until object deletion succeeds and cannot be used to display the deleted photo.

Pseudonymous completed-search and coarse product-use event records expire after 30 days, are excluded from analytics after expiration, and are pruned during subsequent analytics activity. Current trip facts and award observations remain only while contribution is enabled and the related account or trip exists. Turning contribution off or deleting all SkySage data removes those subject-level analytics records.

Deleting workspace data does not by itself cancel a SkySage+ subscription or erase transaction, tax, fraud-prevention, de-identified aggregate, accounting, or temporary private-storage cleanup records that SkySage or Stripe must retain. Use Manage billing to cancel a subscription before deleting workspace data. Deleting SkySage data also does not delete data held independently by your authentication provider, airlines, loyalty programs, or other providers.

This notice will change when the product’s data practices materially change. The date at the top shows when this explanation was last updated.

For privacy questions or help using a deletion control, email privacy@skysagetravel.com or visit SkySage Support. Do not send passwords, payment details, full account numbers, or API credentials in a support request.