BEACONUAV OPERATIONS DOCS // V2.4
FIELD MANUAL / 46

Privacy & security

Who can see your data, how access is scoped, and what controls protect your BeaconUAV records.

Personal records are private

Your sessions, personal gear, parts, batteries, profile, and personal ledger are private by default. BeaconUAV checks the signed-in account before returning or changing those records.

Another pilot's private data is not merely hidden in the interface; the service refuses access outside the account and organization boundaries.

What a squadron can see

Joining a squadron shares only the records intended for that organization's workflow: shared gear, sessions bound to shared gear, roster context, and any organization analytics your role permits. Your personal hanger and private sessions remain personal.

Per-member grants and role templates control shared gear editing, ledger visibility, analytics, and administration. Organization SSO, invitations, policies, and compliance documents have their own administrator boundaries.

Client and portal links

Client document and delivery links expose an allowlisted view of the relevant job, not the internal workspace. Downloads are checked against the live link and use short-lived access to private files. Revoking or rotating a link ends its client access.

Clients do not see internal costs, margins, identifiers, private notes, or unrelated jobs.

Notices and browser state

The Notices bell keeps read state in the browser. That state is not an organization record and does not grant access to a notice. Sign-out clears the authenticated session and local query state; anything you explicitly downloaded remains wherever your device saved it.

Exports and deletion

  • CSV and JSON exports contain your own account data and are available from Settings.
  • Account deletion has a 30-day grace period so you can cancel before personal records are purged.
  • Organization-owned shared records follow the organization's retention and membership rules; leaving a squadron does not erase its shared history.

Sign-in

Passwords are handled by the authentication service, and Google sign-in does not expose your Google password to BeaconUAV. Use a real inbox for confirmation and password recovery.

Info:

BeaconUAV's access controls are designed to protect the records in the product. They do not make an uploaded compliance document, client link, exported file, or device secure after you copy it outside the service.