What we store and why
CyberPlane stores your sign-in identity, aircraft details, uploaded originals, page transcriptions, AI outputs, work and payment records, activity history and submitted inquiries. These support your workspace, evidence search, recovery downloads and requested assistance. Only upload records you have authority to share.
The public waitlist stores your email, optional name, role, consent version and signup time for launch and early-access updates. Signup does not create an aircraft workspace or subscribe you to a paid plan. Temporary hashed request counters help limit abuse; the waitlist does not store raw IP addresses. The configured operator can review the list. Automated launch emails are not active in this development release.
Owner and aircraft-permission checks protect access to aircraft and document APIs. The configured CyberPlane operator can see submitted inquiry details to handle your request. Hosting and service operations require access to stored data; this is not a system where only you hold the decryption key.
Records may contain names, signatures, certificate numbers and financial information. Keep unnecessary sensitive information out of inquiry notes. Request help with access, correction or deletion. There is no self-service account deletion or published automated backup deletion schedule in this pilot.
Encryption is one layer
Files uploaded through the Cyberplane uploader are encrypted with AES-256-GCM before object storage. Existing originals connected from private Vercel Blob storage retain Vercel’s storage protections and are delivered through short-lived, file-specific links after an aircraft permission check; they do not use the Cyberplane original-file encryption layer. The service derives owner-specific keys and can decrypt files for authorized retrieval. Search text, extracted fields, messages and metadata are stored separately in the application database; they do not use the original-file encryption layer.
Authentication, ownership checks, request-origin checks and file-integrity comparisons are implemented. Independent security assessment, separate owner key custody, automated external backups and stronger operational controls remain work to complete. We do not claim DoD certification, FedRAMP authorization, CMMC assessment or FIPS-validated cryptography.
How AI uses your records
Cyberplane selects relevant indexed text and preparation notes from the records you are permitted to access, then supplies them with your question to an AI model. It can help locate and explain maintenance entries, compare supplied details and suggest questions for human review. Answers link to source pages. The model is not specially trained or fine-tuned on your aircraft’s logbooks.
Where shared Vault chat is enabled, selected logbook text, preparation notes, your question and recent chat context are sent through Vercel AI Gateway to OpenAI’s GPT-4.1 mini. Requests require providers that do not use prompts for training; this is a routing control, not a blanket guarantee of zero retention across every service. Shared usage limits apply. Original PDFs and downloads remain available when the AI allowance is unavailable.
Standard text recognition runs in your browser. AI vision extraction uses the connected provider. The separate owner workspace also supports an optional funded OpenRouter connection. If you enable it, selected page text, page images for extraction, aircraft context, work/payment entries and conversation context may be sent through OpenRouter to the chosen model provider. Your key is stored encrypted.
Requests ask OpenRouter to exclude providers that collect data. This is a routing setting, not a guarantee of zero retention across every service. Review OpenRouter’s privacy policy and the selected provider’s terms before processing sensitive records. You can disconnect that owner-provided OpenRouter connection in Settings and keep using originals, text search and recovery downloads. Shared Vault chat is configured separately by the operator.
Answers use selected excerpts, not a full archive audit. The displayed source coverage is a count of retrieved pages, not a completeness or correctness score. A source citation does not establish that the answer interpreted the source correctly.
What a Bitcoin timestamp proves
When you request a timestamp, Cyberplane submits a salted file fingerprint to public OpenTimestamps calendars, which build proofs anchored in Bitcoin’s blockchain. The original document remains in private storage, off-chain. A pending receipt is not yet a confirmed Bitcoin proof. When confirmed, a portable .ots proof can support independent evidence that those exact file bytes existed by the anchoring time.
Keep the original file and its proof to verify that version independently of Cyberplane and check whether a later copy has changed. No Bitcoin purchase or wallet is required. The timestamp does not verify authorship, the historical date printed in a logbook, the truth of a maintenance entry or airworthiness. It cannot reconstruct a lost document. Read about the open standard.
What survives without CyberPlane
A successfully downloaded recovery kit contains ordinary original files, an offline HTML index, readable history, JSON, integrity checks and any available timestamp proofs. Those downloaded files can be used without our service.
Downloads are manual. Keep current copies in a separate location you control, protect access to them, and try opening the offline index. A kit only covers what was successfully included at download time. Its ordinary files are not encrypted by CyberPlane once exported.
Download a synthetic sample · Export your records
