Tenant isolation
Every record carries its organization, and every query filters by it. Ids from the browser are never trusted without also matching the organization.
FAA Ready holds records your certificate depends on. This page describes, in plain terms, what we do to keep them isolated, intact and yours. It does not claim anything we have not built.
Every record carries its organization, and every query filters by it. Ids from the browser are never trusted without also matching the organization.
All traffic to the application and the API uses HTTPS (TLS). Connections from the application to the database and to our processors are encrypted too.
Records live in a managed PostgreSQL database with automated backups and point-in-time recovery, so a mistake can be rolled back.
Signatures store the signer, time, IP address, meaning and a SHA-256 hash of the signed content. Every mutation is written to an append-only audit log.
Owner, admin, manager, employee, read-only auditor and supplier roles. Access checks run on the server for every action; the client is never trusted.
Keys are issued per organization with named scopes, shown once, stored hashed, and can be revoked at any time from Settings.
Outbound webhooks carry an HMAC signature over the payload so your systems can verify they came from FAA Ready and were not altered.
Every table exports to CSV, every binder to PDF, and the read-only API returns your records in JSON. Export is available during and after your subscription.
FAA Ready does not currently hold a SOC 2 report, ISO 27001 certification or any other third-party attestation, and does not claim to. If your organization needs one, tell us; we would rather say so plainly than imply it.
If you believe you have found a vulnerability, write to us with the details and steps to reproduce. A person reads that inbox, will acknowledge you within two business days and will not take action against good-faith research.