Data & privacy
AvFees shares what a stop costs, never who flew it. Everything stored comes from a fixed list of fields, so free text, and the personal data in it, has nowhere to go.
Kept
- Airport (ICAO)
- FBO or airport authority
- Aircraft class (not type or tail)
- Fee type
- Amount and currency
- Date observed
- Fuel volume that waives a fee, if stated
Dropped at intake
- The invoice file itself (only its SHA-256 fingerprint is kept)
- Tail numbers and registrations
- Operator and customer names
- Crew and passenger names
- Trip, account and invoice numbers
- Free-text notes
Consent before anything is shared
No operator's invoices are shared until that operator has agreed. Only keys cleared for it can contribute. Every contribution is held as pending_consent: it is credited to the contributor, but it is not returned by any lookup or used in any projection. When the operator's consent for a submission is recorded, that submission is published. The record says where the consent is written down.
Where it lives
AvFees runs on Microsoft Azure. The app reaches its database through a managed identity rather than a stored password. API keys are stored only as hashes and are shown once, when they are issued.
Questions or removal requests
Contact ForIT, which operates AvFees.