Account protection
Verified email, secure server-managed sessions, production cookie controls, rate limits and optional multi-factor authentication protect account access.
Trust centre
Controls you can understand.
FlightHours is designed around private pilot records, organisation boundaries and traceable operational data. This page describes the controls implemented today without implying certifications or service commitments that do not exist.
Security and access controls
Protection is applied across identity, authorisation, tenant queries, private files and sensitive mutations.
Role-based access
Organisation actions are checked on the server against active membership and explicit permissions. Hiding a control in the interface is never treated as authorisation.
Tenant separation
Organisation-owned records are scoped to their organisation. Ordinary membership does not expose a pilot’s private logbook, medical records, documents or personal costs.
Private documents
Supporting files use private storage paths and authenticated downloads. File type, size, ownership and safety state are checked before access is granted.
Traceable changes
Important logbook, training, permission and operational changes retain revision or audit history instead of silently replacing the previous record.
Data portability
Core pilot records can be imported and exported. A subscription change does not make an owned logbook inaccessible.
Personal and organisation records have different owners.
A pilot’s private workspace and an organisation’s operational workspace are separate security boundaries. Access must be granted for a specific purpose; it is not inferred from ordinary membership.
Read how personal data is handled →Pilot workspaceOrganisation workspace
Personal logbookMembers and roles
Medicals and qualificationsFleet and resources
Private documents and costsBookings and training records
Personal goals and analyticsOperational and maintenance evidence
Operational integrity
The platform favours explicit states, bounded background work and recoverable records over hidden automation.
Validated boundaries
Browser input, identifiers, uploads and provider responses are validated before they enter trusted application flows.
Durable background work
Long-running imports, reports and notifications use bounded, retryable jobs rather than holding interactive requests open.
Conservative failure states
Unavailable provider data, incomplete evidence and ambiguous operational state remain visible instead of being converted into certainty.
Production health checks
Application, database, private storage and background-worker health have dedicated checks with sensitive operational detail withheld.
What FlightHours does not claim
FlightHours organises records and evidence. It does not certify licence eligibility, issue medical or training approval, determine airworthiness, replace an instructor or regulator, or turn tracked aircraft movement into authoritative pilot identity.
Need the formal documents?Privacy noticeTerms of service