Security and trust

Your data stays yours

• Access limited by account and role. Row-level security is switched on for every table in the app's database. A pilot sees their own records and those of the squadrons, schools, and companies they belong to, further limited by their role there. Hiding a button is never the only check.
• Private files, short-lived links. Flight logs, certificates, and client deliverables sit in private storage. Every download is checked against your permissions first and served through a signed link that expires within an hour, and usually within five minutes.
• Export any time. Settings → Export gives you a CSV logbook or a full JSON export of your profile, sessions, gear, parts, batteries, and maintenance records.
• Deletion you control. Settings → Danger Zone schedules account deletion with a 30-day grace period. After that your records are permanently deleted from the live database and you are removed from organization rosters. Copies can remain in backups until those backups expire.

How the app is protected

• Encrypted connections. Every connection uses HTTPS, and browsers are told to use HTTPS only (HTTP Strict Transport Security).
• Encryption at rest. The database and stored files are encrypted at rest by our infrastructure providers.
• Browser hardening. Pages ship with a content security policy that only runs our own scripts, refuse to be framed by other sites, and send a strict referrer policy.
• Passwords we cannot read. Sign-in is handled by our authentication provider. Passwords are stored only as hashes, and signing in with Google never shares your Google password with us.
• Rate limits and security logs. File downloads, client links, profile changes, and other sensitive endpoints are rate limited, and security events are logged for review.
• Verified payment events. Card details are entered directly with Stripe and never reach our servers. A payment notice that arrives without a valid signature is held for review and can never mark an invoice paid on its own.
• Checked on every change. Each change runs a dependency audit, a secret scan, security-header checks, and an automated suite of database access tests before it can ship.

Schools and students

• Roster-only student accounts. Student accounts are created only from a roster entry added by a school or district administrator, and student records are visible only to that school's and district's authorized staff. Student data is never used for advertising.

What we do not claim

• BeaconUAV has not completed a SOC 2 or ISO 27001 audit, and is not certified under either.
• BeaconUAV is not HIPAA compliant and should not be used to store health records.
• Two-factor sign-in is not yet available to users.

Reporting a security issue

If you find a vulnerability, please tell us before sharing it publicly, using the contact details in Section 11 of our Privacy Policy. Include enough detail for us to reproduce it, and do not access or change data that is not yours while testing.