Privacy Notice

Operational teams wield personal information authenticating identities delivering notifications coordinating introductions probing abuse escalating safety workflows counsel enumerates narrowly.

Aggregated dashboards measure feature uptake so engineers troubleshoot cohorts sized large enough analysts cannot realistically re-identify individuals absent supplementary joins.

Hosting, email, observability, fraud-vendor assistants listed inside onboarding appendixes—or successor URLs—receive minimum-necessary excerpts governed by contractual confidentiality pledges refreshed periodically.

Mobile phone numbers collected for optional operational text alerts (SMS) are used only to deliver those alerts and related verification. We do not sell mobile numbers or share them with third parties for their marketing. Carriers and messaging providers (for example Twilio) and verification providers (for example Google for Firebase phone verification) process numbers solely to send or verify messages you request.

FLT LVL 410 confines compelled disclosures subpoenas statutes demand after commercially reasonable counsel review unless emergency statutes forbid delay.

Rows persist according schedules counsel aligns with subpoena horizons fraud investigations ordinarily spanning finite months absent statutory elongation.

Legal holds lengthen retention where litigation regulatory exams or safety inquiries remain open counsel monitors closures diligently scheduling purges afterward.

Controls entail encryption segregation least privilege alerting tabletop rehearsals though internet-connected software never attains flawless immunity attackers evolve rapidly.

FLT LVL 410 notifies affected parties timelines statutes decree messaging counsel drafts balancing transparency versus premature factual conclusions.

Residents exercising GDPR-, UK GDPR-, CPA-, or analogous rights may email the privacy-facing alias counsel publishes requesting access portability rectification erasure restricting processing objections accompanied by corroborating identity artefacts.

FLT LVL 410 fulfills commercially feasible responses absent conflicts statutes impose declining requests counsel documents rationale contemporaneously operators review.

FLT LVL 410 uses cookies, local storage, and similar technologies to keep you signed in, remember preferences, and measure how the product is used. Product analytics are delivered through Google Analytics 4 and PostHog (US Cloud). We send typed events and page views—not free-form autocapture—and tie them to your Firebase account identifier after sign-in so engineers can troubleshoot flows and improve reliability.

PostHog may record limited session replay on routes where replay is enabled. Replay is disabled on admin screens, messaging and conversation threads (including pilot and operator message inboxes), and operator transaction detail—not on every billing, payout, or payment screen. Typed input is masked by default, and elements marked for masking or exclusion are omitted. Session recording starts only when analytics consent allows it and stops when you opt out.

You can limit analytics and session recording at any time. The footer privacy control and declining analytics in local storage (when signed out) stop browser-side Google Analytics 4 and PostHog, including session replay. Browser Do Not Track (DNT) and Global Privacy Control (GPC) signals apply the same browser-only opt-out—they do not by themselves stop server-side event capture. Signed-in users can also toggle opt-out under Security → Privacy & analytics; that account setting stops server-side analytics for your account (including Google Analytics Measurement Protocol and server PostHog) in addition to the browser controls.

Declining cookies or analytics may limit personalization and make some troubleshooting harder, but core authentication and trip workflows remain available. We describe these tradeoffs in-product when you change your choices.

Privacy inbox temporarily resides at privacy-beta@fltlvl410.com until counsel substitutes durable escalation paths routed through ticketing.

Suspected vulnerabilities warrant coordinated disclosure emailing security-beta@fltlvl410.com counsel rotates addressing later roadmap milestones independently.

Material modifications surface via product banners onboarding modals plus archived superseded drafts counsel steward alongside version constants developers embed.

Continued Pilot or Operator journeys after conspicuous postings constitute pragmatic acceptance notwithstanding non-waiver principles statutes preserve vigorously.