Key takeaways
- Ownership of drone data is decided by the contract, not by who pressed the shutter — if the agreement is silent, you are relying on assumption rather than a right.
- Ask for the raw imagery and logs, not only the finished report. Without them, any future re-processing, audit or dispute depends on your contractor still having the files.
- Retention cuts both ways: too short and the file is gone when a claim arrives; too long and confidential site imagery sits on somebody else's storage indefinitely. Name a period.
- Publication consent belongs in writing. Most industrial sites have marketing, security or client-confidentiality reasons that no operator can guess at.
Most drone contracts in Alberta industry cover the flight and the deliverable. Almost none of them cover what happens to the data afterwards — who owns it, who can publish it, how long the operator keeps it, and what you get if you ask for everything back three years from now.
That gap does not matter until it suddenly does: an insurance claim, a contract dispute, a regulator asking for the record of a site on a specific date, or a photo of your facility turning up on a contractor's Facebook page. This is the set of questions worth settling before the first flight, not after.
Ownership is whatever the contract says it is
There is a common assumption that the client automatically owns everything captured over their own site. There is an equally common assumption on the operator's side that the person who created the imagery holds the copyright in it. Both can be arguable, and arguing about it after the fact is the expensive way to find out.
The practical fix is one clause. It should say who owns the delivered outputs, who owns the raw capture, and what licence the other party keeps. A workable and very common arrangement on industrial work looks like this:
- The client owns the deliverables outright — the orthomosaic, the point cloud, the surface model, the report — and can use, copy, share and re-process them without asking.
- The client also receives, and owns or holds a full licence to, the raw imagery and flight logs.
- The operator keeps a limited internal licence for record-keeping, quality assurance and defending its own work — not for publication.
What matters is less which model you pick than that it is written down. A silent contract is not a neutral contract; it just means the answer gets decided later by whoever has more leverage.
Ask for the raw data, not only the report
The deliverable is a processed interpretation. The raw imagery, the GNSS observations and the flight logs are the underlying evidence, and they are what any future question has to go back to.
Reasons this comes up in practice:
- Re-processing. Software improves, project coordinate systems change, and a survey flown for one purpose is often re-processed later for another. That is only possible with the raw capture.
- Audit and dispute. If a volume, an as-built or an inspection finding is challenged, the defensible answer is the original data and the processing record — not a PDF.
- Continuity. Contractors change. Companies get acquired. A survey you cannot retrieve is a survey you will pay to fly again.
Raw data is bulky, so agree the delivery mechanism at the same time: a drive, a transfer link with a stated expiry, or your own cloud storage. "We can send it if you need it" is a promise about somebody else's future disk space.
Retention: name a period, in both directions
Retention is usually left entirely to the operator, which produces one of two bad outcomes. Either the files are deleted after a job closes and are gone when you need them, or they sit on a contractor's storage forever, including imagery of a site you consider sensitive.
Set a period deliberately. The right length depends on why the data exists:
- Volumetric and production surveys generally need to outlive the reporting cycle they feed, because the comparison that gets questioned is usually period over period.
- Inspection records tend to need to survive as long as the asset's own maintenance and integrity records do.
- As-built and construction capture often needs to reach as far as the applicable limitation and warranty periods for the work it documents.
- One-off marketing or visual capture rarely needs long retention at all.
Then say what happens at the end of it: deletion, secure destruction with written confirmation, or return. Retention on an industrial job is a records-management decision, and your own document-retention schedule is usually the right thing to align it to.
Publication consent, in writing, per job
Drone operators want portfolio imagery, and the imagery is genuinely good. But an aerial photo of an industrial site is not a neutral picture. It can show plant layout, security arrangements, stockpile positions, equipment counts, work in progress a client has not announced, or a facility whose location the operator's client would rather not advertise.
Blanket permission buried in terms and conditions is not a serious answer to that. What works:
- Publication is off by default and requires written approval for each specific image or clip.
- The approval names what may be shown and what must be excluded or blurred — signage, plates, faces, adjacent operations.
- Naming the client is a separate permission from showing the site.
- Permission can be withdrawn, and the operator takes the material down when asked.
Where a site is on someone else's lease or a project has a prime contractor, the party who can grant that permission may not be the party who hired the drone. Worth checking before the request, not after publication.
Confidentiality and site rules
On most industrial work the drone contractor is a subcontractor inside an existing compliance structure, and the data obligations flow from that structure rather than from anything aviation-specific. Expect and ask for:
- An NDA or the confidentiality provisions of your master service agreement extended explicitly to captured data, including on the operator's own laptops and cloud accounts.
- Named sub-processors. If processing happens in a third-party cloud service, that is another organisation holding your site imagery.
- Data location, where it matters to you. Some clients require Canadian storage; that has to be stated up front because it constrains which processing tools can be used.
- A breach-notification expectation — who tells you, and how fast, if the operator's storage is compromised.
None of that is exotic. It is the same set of questions any IT or procurement group would ask of a vendor handling company records, and drone data is company records.
Personal information is a separate problem
Site data is commercial information. Anything that identifies a person — a worker's face, a licence plate, a neighbouring residence — is personal information, and in Alberta private-sector organisations handle that under provincial and federal privacy legislation depending on the organisation and the activity.
Rather than trying to settle the legal analysis in a flight plan, deal with it operationally. Plan flight lines and camera angles to keep neighbouring property out of frame where it is not needed. Tell site personnel that flights are happening. Blur or crop incidental identifiable detail before anything is circulated widely, and be conservative about imagery of areas outside the client's own boundary. Transport Canada's rules govern how the aircraft is flown; they are not a privacy compliance programme, and the two get conflated regularly.
The clause list
If you take one thing from this into your next drone scope, take this list. Six lines in a contract prevents every conversation above:
- Ownership of deliverables and of raw capture, stated separately.
- Raw data delivery — what you receive, in what format, by when, and how.
- Retention period, what happens at the end of it, and who confirms deletion.
- Publication — written, per-item consent; client naming treated separately.
- Confidentiality extended to captured data, with sub-processors and storage location named.
- Personal information — how incidental capture is minimised and handled.
Any competent commercial operator will already have positions on all six. The ones worth hiring will tell you what they are without being asked twice.
If you are writing a drone scope of work and want a straight answer on how we handle ownership, retention and site confidentiality, get in touch — and if you are still assembling the wider vendor package, our guide to vetting a commercial drone contractor covers the certificate and insurance side.