v2026-08-08
Security
Authentication, tenant isolation, and operational security practices.
1. Authentication
- Passkeys (WebAuthn) preferred for staff and crew.
- WhatsApp Cloud API one-time codes as fallback / onboarding.
- Session cookies signed with a server secret; HTTPS via Caddy wildcard TLS on
*.skyroster.net.
2. Isolation & data at rest
- Host-header tenancy; reserved
adminsubdomain never serves airline OCC. - One SQLite WAL database per tenant under
data/tenants/{iata}.db; platform DB separate. - OS-level file permissions and host firewalling; secrets only in environment (never in git).
3. Application controls
- Role-based access within the tenant (admin / planner / crew self-service
/m). - Upload size limits for crew documents; stored outside public URL space where configured.
- No cross-tenant SQL: connections open only the resolved tenant file.
4. Third parties
Weather (NOAA AWC), optional FAA NOTAM, maps (OpenFreeMap / optional MapTiler), WhatsApp, and optional Gemini are used over TLS. API keys are server-side only. Weather/NOTAM outages must not block core OCC forms — errors are shown, workflows remain usable.
5. Customer responsibilities
- Assign least-privilege roles; revoke leavers promptly.
- Protect devices used for Passkeys and WhatsApp OTP.
- Classify and minimise personal data uploaded to document storage.
- Report suspected incidents without delay using the contacts below.
6. Incident response
Provider investigates security incidents affecting confidentiality or integrity of Customer data and notifies affected Customers without undue delay when required by law or contract. Card PANs are not collected by SkyRoster; fees are paid by SWIFT USD transfer to the published Receiver.