FlightPush · Trust Center
Updated 2026-07-13A direct description of the safeguards FlightPush uses today and the limits of those safeguards.
Section 01
FlightPush uses Supabase authentication and row-level security, Stripe-hosted payment processing, server-side authorization for protected actions, rate limiting on sensitive routes, dependency and secret scanning, and production error monitoring.
FlightPush does not store complete payment-card numbers on its own servers. Stripe processes payment credentials under Stripe’s own security and privacy program.
Section 02
This page is a transparency statement, not a claim of SOC 2, ISO 27001, PCI certification by FlightPush, or an independent security audit. Those claims will not be published unless they become true and verifiable.
Section 03
Security concerns should be sent privately to support@flightpush.co with enough detail to reproduce the issue. Do not publicly disclose personal student information or attempt to access data that is not yours.