PRIVACY / PRODUCT ANALYTICS

Anonymous usage analytics

Analytics are opt-in. Declining does not limit the mission planner.

What may be collected

Page or workflow stage, mission category, selected aircraft model, evidence/completion state, sortie count, export format, structured error code, anonymous browser/session identifiers, and event time.

What is excluded

Mission geometry, coordinates, address or map search text, mission/site names, free-text notes, regulatory contact fields, flight logs, calibration values, and exported mission contents are not permitted in analytics payloads.

Your choice

The browser stores granted or denied consent locally. Clear site data to reset the choice. Collection also remains off when UASyard has no configured analytics endpoint.

Owner requirements

The analytics endpoint must reject unknown properties, limit access and retention, document its processor and hosting region, and support deletion where applicable. Product analytics never establish flight safety, regulatory authorization, or model accuracy.