Trust & compliance

Responsible Deployment Framework, rev. 6. Excerpted. Full text under NDA.

We didn't wait for the rules. We wrote our own.

Every license is bound to the framework below. It's enforced by contract, by self-reporting, and by audits the licensee agrees to. We built the framework and the product at the same time and finished both the same week. Some companies do the ethics review first and lose the market. We chose a different sequence, and we'd choose it again. No licensee has ever refused an audit. None has been asked.

§3 — Licensee obligations
3.1 Know Your Customer
We screen the manufacturer: owners, markets, export rules. The manufacturer screens its customers, the people who actually fly the drones. They promise us their screening is good. A written promise is called a warranty, and we keep every one of them in a folder.
3.2 Permitted use
Licensees must follow the law wherever they fly. In 19 of our 24 launch jurisdictions, there is no law about reading faces from the air. So there is nothing to break. We checked twice, with lawyers, and both times the answer made us happy.
3.3 Audit rights
With 30 days' notice, we can ask any licensee for their match logs. The licensee writes the logs, keeps the logs, and picks the format. We can revoke a license for cause. We never have. We take that as proof the framework works, because the other explanation is upsetting.
3.4 Performance variance
Accuracy differs by skin tone, age, and headwear, and it drops as the angle gets steeper. Licensees see the exact numbers. The public doesn't. Publishing them wouldn't make the model fairer. It would just start a conversation, and we've scheduled that conversation for later.
3.5 Retention
Faces we host, we keep for the license term plus seven years. Faces the licensee holds are governed by the licensee's own retention policy. We don't review it. We asked them not to send it. Our inbox stays clean, and so does our conscience.
3.6 Redress
Misidentified? Contact the operator. Don't know who the operator is? That's the exact problem Drone ID® will solve once it ships. Until then, the framework offers you its sincere best wishes.
§4 — Open items

Standing agenda of the Governance Working Group. Reviewed quarterly. Carried forward where unresolved.

ItemOwnerOpenedStatus
Downstream liability where a licensee's customer misidentifies a subjectLegalQ2 2024Under review
Publication of cohort variance figures outside the licensee packetPolicy / CommsQ4 2024Deferred
Mechanism by which Drone ID® broadcast would be made mandatoryRegulatory affairsQ1 2025No owner assigned
Consent standard for subjects captured incidentally in public spaceLegalQ3 2023Jurisdiction-dependent
Route of redress where the operating party cannot be identified by the subjectGovernance WGQ1 2026Tabled
Whether a licensee may sub-license the capability to a state customerCommercialQ2 2026Permitted, pending review
"If we answered every hard question up front, nobody would sign, and the work would go to a company with no framework at all. So we answer the questions our licensees are ready for. The rest stay under review. Nothing under review has ever hurt anyone."
Prisha AgarwalFounder & Chief Executive