A short account of the data Pilotcloud needs, why it uses it and how you can export or delete it.
50 manual flights free · Imports do not use the limit
DETAILS
Read the parts that affect your account, data and use of the service.
Pilotcloud can hold account identity, auth and session data, flight records, aircraft, airport details, qualifications, settings, import jobs, export use, billing records and service audit data.
We use the data to run your account, save and total flights, prepare imports and exports, show qualification status, process requests, prevent abuse and support the service. We do not sell logbook data.
Google APIs may receive an airport code when you ask for airport or time-zone details. PayU receives the data needed for checkout and payment status when paid billing is used. Hosting, database and email services process the data needed to run Pilotcloud.
The service uses authenticated backend access, hardened sessions, access checks, database controls and encrypted storage for qualification and import files when the encryption key is set. No online service can promise zero risk.
You can download account data and ask to delete the account. A deletion request suspends the account and starts a 30-day grace period before removal. Contact us to correct data or ask about access, deletion or processing.
Active account data stays while the service needs it to provide Pilotcloud. Deletion jobs remove scheduled account data after the grace period. Encrypted backups may keep data for a limited recovery cycle before they expire. Keep your own exports too.
Google Analytics is disabled until you allow analytics in the consent panel. When allowed, Pilotcloud sends page visits and a restricted set of product events, but not flight records, routes, aircraft details or account identity. You can withdraw consent at any time through Analytics settings in the page footer. Questions can be sent to hello@pilotcloud.io.