.dfr Package Methodology

Drone Action 360 Inc. · DFR Canada service · Version 1, October 28, 2026

This document explains how a .dfr package is made and why one can state, and check for oneself, that it has not been altered since. It is written for anyone who has to rely on a package: judge, prosecutor, lawyer, police officer, expert. It requires no technical knowledge.

1. What a .dfr package is

A .dfr package brings together everything recorded during a drone operation: the camera video, the drone’s position, the messages exchanged between responders, the photos, the voice notes and the mission events. It also contains a player that replays the operation on any computer, with no Internet connection and no software to install. To check the package, rely on the player Drone Action 360 provides itself, or on OpenSSL (section 7).

The package is created automatically by the DFR platform at the end of the mission. No one assembles it by hand.

2. How the operation is recorded

The video. The drone sends its image live to the platform, which records it as the responders saw it on screen. This recording is the only one that exists of what was seen during the operation.

The position. The drone sends its GPS position about every two seconds during the flight. The platform keeps it with the time of the measurement.

Messages, photos and voice notes. Each message is kept as it was sent, with its author and its time. Voice notes are kept as audio; an automatic transcription comes with them to help find one’s way.

Time. Messages and video are timed by the clock of the platform’s server. Positions are timed by the drone when they are measured; its clock agrees with the server’s to within about one second.

3. When each item is protected

Each file receives a digital fingerprint: a string of 64 characters computed from its content, with a public and standardised method (SHA-256). Two files that differ by a single character produce two completely different fingerprints. A digital fingerprint works like a fingerprint: it identifies one specific file and reveals any change.

The platform takes each item’s fingerprint as early as possible:

  • Photos, files and voice notes: as soon as the platform receives them, during the operation.
  • Videos: as soon as the camera stops streaming, its recording is stored and receives its fingerprint.
  • Messages, positions and events: at sealing, which takes place automatically as soon as all the mission’s videos are stored.

For each file, the package states at which of these three moments its fingerprint was taken.

4. How the package is sealed

At the end of the mission, the platform:

  1. Draws up the inventory of every file in the package, with the fingerprint of each. The player, the map and this document are part of the inventory: they are protected too.
  2. Signs the inventory with Drone Action 360’s signing key. This key is kept in a hardware security module, in a Microsoft Azure data centre in Canada. It cannot leave it: no one, including at Drone Action 360, holds a copy. The certificate that comes with the signature is issued by SSL.com, a recognised certification authority, after verification of the company’s identity.
  3. Has the inventory timestamped by DigiCert, an authority independent of Drone Action 360. The timestamp token attests that the inventory existed, in this exact form, at the stated time.
  4. Attaches the proof, as supplied by SSL.com, that the signing certificate was valid at the time of signing.

In addition, Drone Action 360 keeps the fingerprint of every signed inventory in a register that the database refuses to modify or delete.

5. Why the package can be said to be unaltered

  • A modified file no longer has the fingerprint recorded in the inventory. The change shows.
  • A modified inventory, written to record a new fingerprint, no longer matches the signature. The change shows.
  • A new signature would require Drone Action 360’s key, which cannot leave its security module.
  • DigiCert’s timestamp fixes the time at which the package existed in this form. It does not depend on Drone Action 360.

These protections travel with the package everywhere: on a USB key, on a server, with a third party. Whoever has handled it, any change, even of a single character, is detected.

6. What the method establishes, and its limits

The method establishes that the content of the package is what the platform recorded, and that it has not changed since each fingerprint was taken. It has limits worth knowing:

  • A fingerprint protects a file from the moment it is taken. Before that moment, the file is in the custody of the platform, which records it automatically.
  • The time of positions comes from the drone; it agrees with the server’s to within about one second.
  • The position is the drone’s, not that of what the camera is looking at.
  • Addresses shown are the closest to a position. They are approximations.
  • Transcriptions of voice notes are automatic and have never been corrected. The audio prevails.
  • What is done after sealing stays in the platform and does not enter the package: views of the file, downloads of the package and markers added in the replay. Drone Action 360 keeps the register of these actions.

7. How to check for yourself

With Drone Action 360’s player. The player that counts is the lecteur-dfr.html file that Drone Action 360 places in the service’s storage, next to the packages, or provides with a package downloaded from the platform. Open it, then open the package in it: it redoes every check, namely the signature, the validity of the certificate, the timestamp and the fingerprint of each file. The button at the top of the screen gives the verdict, and the verification panel shows the details of each proof. The player contained in a package travels with it: it replays the operation, and its verdict is worth what the package’s origin is worth.

Without the player. An expert can redo everything with free public tools (OpenSSL), with no Internet connection and without asking Drone Action 360 for anything. The exact commands are given in the player’s verification panel.

Drone Action 360’s certificate is issued to Drone Action 360 Inc., in Longueuil (Quebec, Canada); a company of the same name registered elsewhere has another certificate. The certificate and its fingerprint are published at https://droneaction360.ca/en/certificats, for comparison.

8. Versions of this document

Each package contains the version of the methodology in force when it was sealed, protected by the same signature as the rest of the package. The current version is published at https://droneaction360.ca/en/methodologie.

Version Date Change
1 October 28, 2026 First version