Use less data. Protect it more.
This notice describes the FareSift public beta. The beta does not request passport numbers, known-traveler numbers, or payment-card data.
Data we use
Trip constraints, signed-in traveler preferences, watch rules, support requests, subscription intent, launch-list email and consent, optional savings-review or partnership requests, outbound seller clicks, referral codes, and first-party product events.
Attribution
FareSift stores limited first-touch campaign information on your device and records referral codes, campaign labels, landing path, and referring domain with product events. It does not store a full referring-page URL or expose your searches through a share link.
Why we use it
To operate the product, calculate traveler-specific cost, save searches, measure reliability, attribute eligible partner referrals, evaluate requests, respond to support, and enforce legitimate fare eligibility.
AI boundary
Direct identifiers, payment hints, passport-like tokens, known-traveler numbers, and raw documents must be removed before any production AI call. Prices, rules, eligibility, and transactions remain deterministic.
Retention and choices
Account export is available after sign-in. Launch emails include an unsubscribe route when outbound email is activated. Deletion, legal-hold, and jurisdiction-specific rights workflows must pass production review before paid services activate; contact support for a beta privacy request.
Storage and processors
Public-beta records are stored in the application’s managed database and protected in transit and at rest by the hosting platform. Payment data is not collected. Approved airfare, email, and payment processors will be named here before their services activate.