Security overview
Flightdesk holds student records, signed agreements and compliance documents for flight schools. This page describes how we protect them today. Formal documentation, including a security questionnaire, a data processing agreement and a subprocessor list, is being finalized for general availability. Ask us for the current versions.
Sign-in without passwords
Staff and students sign in with a one-time code sent to the address their school has on file. Requests are rate limited per address and per network, and the form gives the same neutral answer whether or not an address is known. No passwords are stored anywhere. Sign-in e-mails carry the school's name, come from the school's own sender when it has one, and link only to the school's own site.
One organization per school
Each school is its own organization with its own hostnames, branding and sender address. Access is enforced in the database with row level security. Server code uses a service role that never reaches the browser, and this product site never reads a school's data.
Who can see what
Roles exist for owner, general manager, admissions, compliance, chief instructor, assistant chief instructor and CFI. A CFI sees only their own students. An audit log records who changed what and when.
Documents and signatures
Uploaded documents are reviewed by a staff member before they count. Signatures produce a signed PDF with an audit trail under ESIGN and UETA. Documents are served only to signed-in people whose role allows it, through short-lived links.
Integrations and API
Credentials for Dropbox, Google Drive and S3 are encrypted at rest. API keys are scoped to one organization, shown once and stored hashed. Webhook deliveries are signed with a timestamped HMAC, and the developer reference describes how to verify them. The developer reference and the OpenAPI document are shared with school administrators and their integration partners on request.
Infrastructure
Flightdesk runs on managed infrastructure in the United States. Traffic is encrypted in transit. Backups and encryption at rest are provided by the database provider, and e-mail goes through a transactional provider.
What we do not claim
We do not currently hold a third-party security certification and we do not publish uptime or incident figures. Ask us and we will tell you where things stand.
Report a concern
Write to us at brandon@stratus.finance.