Enable DJI Flight Record API

Starting June 2020, DJI started to encrypt some flight logs with private/public keys, which require Airdata to obtain a decryption key online from DJI per each flight.

Airdata worked closely with the DJI engineering team to provide seamless integration in Airdata.

 

How it works
When you upload flights to Airdata (manually or automatically):

• Airdata will first try to read them without using the DJI API.
• If the new log file is encrypted with the new encryption, Airdata will then send the encryption keys, extracted from each encrypted log, to DJI.
• These extracted keys were randomly generated when the DJI flight app (or DJI SDK based flight app) created the flight log. Airdata does not generate those keys.
• The DJI online API service will then reply with the proper decryption keys so Airdata can decrypt each flight log.

Privacy
DJI clarified that no flight information or private information is sent to DJI. The source code of the key generation was provided to Airdata to verify this process, and to alleviate any concerns regarding privacy.
The data sent to DJI is very small and contains the encryption keys only. This process is similar to how secure websites work (Public/Private key exchange). Currently DJI GO 3 / DJI GO 4 / DJI Pilot DO NOT use this new encryption, but DJI stated that they are planning on changing this in the future.

What if I choose to disable this?
You can disable this so that no information is sent to DJI.
In this case, only very basic information will be available on Airdata, such as the flight time, the drone serial and the battery serial numbers. The detailed flight information such as the flight path, speed and battery voltages will not be available.

Changing this setting will only affect newly uploaded flights, and it will not affect flights already uploaded to Airdata.