Aviagent is EASA Part-CAMO airworthiness-compliance software. We treat the fleet and compliance data operators entrust to us as regulated records. This page describes the security practices in place today — real practices, not certifications we have not earned.
1. Data Protection
- Encrypted in transit — all traffic is served over HTTPS (TLS 1.2+), behind Cloudflare.
- Encrypted at rest — data is stored in managed PostgreSQL with AES-256 disk encryption.
- Hosted in the EU — application and database run in the Frankfurt (EU) region.
- Tenant isolation — every organisation’s data is strictly scoped to that organisation; queries are org-bound by default.
2. Authentication and Access
- Multi-factor authentication is required on every account (email one-time code, authenticator app, or SMS).
- Bot-verification and rate-limiting on login — sign-in is protected by Cloudflare Turnstile and request throttling.
- Role-based access control — permissions are scoped by role within each organisation.
- Accounts are provisioned by us, not open self-registration — access requests are reviewed before an account is created.
3. Auditability and Data Provenance
- Append-only audit trail — access and changes are recorded and are not silently rewritten.
- AI-assisted fields are labelled with their provenance, in line with EU AI Act Article 50 transparency — you can always see what was machine-written versus authority-sourced.
4. Email and Sender Authentication
Transactional email (one-time codes, activation, password reset) is authenticated with SPF and DKIM; DMARC monitoring is in place.
5. Analytics on Our Public Websites
Our public websites use self-hosted analytics running on our own EU infrastructure. No cookies are set, no cross-site identifier is stored, and no analytics data is shared with a third party. There is no analytics of any kind inside the authenticated application, where customer fleet and compliance data lives.
6. Responsible Disclosure
Found a vulnerability? Please report it privately to postnospam[at]aviagent[dot]ai. Our machine-readable policy is published at /.well-known/security.txt (RFC 9116). We investigate every report and will acknowledge good-faith research.
7. What We Do Not Claim
We describe practices we can stand behind today, and we do not display certification badges we have not earned. Questions about our security posture? postnospam[at]aviagent[dot]ai.