Platform Security & Engineering Integrity
UAVComply separates deterministic flight-log parsing and physics math from optional narrative assistance, isolates every operator workspace per authenticated account, and states cryptographic verification limits explicitly.
SHA-256 File Custody Digest (And Its Scope)
ArduPilot .BIN and PX4 ULog .ULG/.ULOG binary logs are hashed via WebCrypto SHA-256 inside your browser. Every dossier embeds that byte-custody digest with the explicit scope note: SHA-256 proves byte identity of the uploaded file, not flight-controller authenticity or physical sensor calibration.
Authenticated Sessions & Access Controls
Browser sessions use HMAC-SHA256 signed HttpOnly cookies verified with constant-time comparison across protected API routes and Edge middleware. Google Sign-In tokens are verified server-side, passwords use salted scrypt hashes, and PostgreSQL row-level security (RLS) isolates operator records by owner ID.
Deterministic Math vs. AI Boundaries
Kinetic energy, battery per-cell sag, VO coverage geometry, aerodrome distance, contradiction findings, and SORA/Part 107 evidence completeness run deterministically in code. Optional AI drafting routes are rate-limited, require authentication, never alter raw telemetry numbers, and never train public models on customer data.
Billing Security & Workspace Scoping
Checkout sessions and webhooks are handled by Dodo Payments with cryptographic webhook signature verification and idempotency keys. Client-side fleet, logbook, and corridor caches are partitioned by authenticated user ID to prevent cross-account data bleed on shared workstations.