Privacy and data handling

UDAI protects the privacy of participants while providing the transparency required for safe airspace management.

Data categories

Public registry data

Non-sensitive data required for public safety and coordination. Examples: airspace zone definitions, asset model specifications. Available to authenticated users.

Operational data

Data generated during missions and flight operations. Examples: flight-plan bounds, telemetry frames. Restricted to the owner Organisation, authorised Airspace Monitor entities, and regulatory bodies.

Sensitive personal data

Information that identifies individual users or pilots. Examples: name, email, phone, remote pilot certificate number. Restricted to the user’s primary Organisation and platform administrators.

Handling principles

UDAI operates under Trust by Design.

Purpose limitation

Data is used to manage the national drone registry, ensure safety and deconfliction, and fulfil regulatory compliance.

Data minimisation

Only fields defined in the data models are collected. No additional tracking is gathered beyond what is necessary for safety and institutional operations.

Retention

• Active records. Maintained while the User or Organisation remains active.
• Historical data. Mission history and flight-session logs are archived according to institutional retention schedules.
• Deactivation. Records marked Inactive or Banned in the enums are protected under regulatory guidelines.

Rights

Users and organisations may review registered data through the Users and Organisations APIs, request corrections to inaccurate registry information, and understand the context of airspace access rejections issued by an Airspace Manager.

For procedure questions, contact Drone Federation India as described in Support.