ECZ-ID Drone Insurance Readiness
Organise drone / UAS operational evidence for insurance review.
Free, local-first. No source upload. No sign-in to run a check.
- Surfaces Drone / UAS operations and related evidence — locally, by filename and path.
- Builds a local, claim-free evidence summary you can review and share.
- Routes to Resolver lookup, implementation guidance and supported setup.
Useful for
Useful across many legitimate roles. Commonly used by:
- Drone / UAS operators
- Brokers and risk engineers
- Compliance reviewers
- Insurer-facing stakeholders
Relevant when you are gathering flight-log / Remote-ID / authorisation evidence, you are building an evidence pack before an insurance conversation, you are reviewing operational authorisations.
What you can do in under a minute
- Open or scan the workspace — run
ECZ-ID Drone Insurance Readiness: Review / Scan Workspace.
- Review the evidence — observed and not-observed, in plain English.
- Build the Evidence Pack or continue supported setup where relevant.
What it looks for
- Drone / UAS operations evidence
- Operational authorisation evidence
- Maintenance / airworthiness evidence
- Operator / registration identifier
Example use cases
- Gathering flight-log, Remote-ID and operational-authorisation evidence.
- Building an evidence pack before an insurance conversation.
Example result
ECZ-ID Drone Insurance Readiness
- flight-log.csv ............ present
- sora-authorisation.md ..... present
- airworthiness evidence .... not observed, review recommended
What results mean
Results describe observed evidence and public-proof posture — never a safety, approval, certification or compliance verdict:
evidence observed · evidence not observed · review required · no public proof reference found yet · re-check before reliance · your local policy decides.
There is no “pass/fail”. Local policy decides what is sufficient, and you should re-check before reliance.
Insurance review note
This tool organises technical and operational evidence for insurance review. It does not provide insurance, legal or underwriting advice, determine insurability, issue a quotation or guarantee that cover will be available.
Recommended next steps
- Show evidence — observed and not-observed, no verdict.
- Build Evidence Pack — a local, claim-free document you can review and save explicitly.
- Open implementation guidance — Developer Gateway.
- Open Resolver — read-only public proof lookup.
- Request Resolver Proof — for a third-party target (claim-free request).
- Begin supported setup — hand off to TrustOps (metadata only).
- Re-check later — re-run before you rely on a result.
Privacy & permissions
| Question |
Answer |
| Files read |
Filenames and paths during a normal scan |
| File contents read |
No — detection is filename/path only |
| Anything uploaded |
No source, prompts, secrets or tool payloads leave your device |
| Network destinations |
Only links you click, and an optional user-initiated public interface refresh |
| Telemetry |
None |
| Retention |
None |
| Workspace Trust |
Respected; scanning is gated by VS Code Workspace Trust |
See the bundled PRIVACY.md for the full notice.
Frequently asked questions
Is this extension free?
Yes. Every local check is free — you never need to sign in or pay to run one.
Does it upload my source code?
No. Detection is filename/path only; no source, prompts, secrets or tool payloads ever leave your device, and there is no telemetry.
Does this decide whether I can get insurance?
No. This tool organises technical and operational evidence for insurance review. It does not provide insurance, legal or underwriting advice, determine insurability, issue a quotation or guarantee that cover will be available.
Does a missing item mean something is wrong?
No. “Evidence not observed” is neutral — your local policy decides what is sufficient.
What does it do when the public interface service is unavailable?
It keeps working from a bundled fallback contract. A refresh is optional and user-initiated.
What it does not do
- No source / prompt / secret upload, and no telemetry.
- Provides local evidence review and guidance only - it does not issue ECZ-ID proof, activate services, grant access, or make approval, safety, insurance or compliance decisions.
- Makes no safety, approval, certification or compliance claim.
- Makes no insurability, underwriting, premium or cover claim.
- Runs no checkout or payment — commercial actions happen only in TrustOps.
Install & first use
- In your editor's Extensions view, search for ECZ-ID Drone Insurance Readiness (publisher EcoCitizenz) and install it.
- Open a project and trust the workspace.
- Run
ECZ-ID Drone Insurance Readiness: Review / Scan Workspace and review the evidence.
Free vs supported setup
- Free, local-first: an organised evidence pack for insurance review (Insurance Readiness only), an evidence summary, and routes — no sign-in and no purchase to run a check.
- Supported setup (TrustOps): maintained ECZ-ID identity, public proof and lifecycle for drone insurance-readiness evidence — relevant when you need a resolver-verifiable result others can check, not just local review.
- You never need to buy anything to get local value; supported setup is a separate, optional step handled entirely in TrustOps.
Machine-readable facts
| Field |
Value |
| Product |
ECZ-ID Drone Insurance Readiness |
| Identity |
ecocitizenz.eczid-drone-insurance |
| Publisher |
EcoCitizenz |
| License |
Free; see the bundled LICENSE.txt |
| Version |
0.1.1 |
| Page family |
functional-extension |
| Purpose |
Organise drone / UAS operational evidence for insurance review. |
| Applicable audiences |
Drone / UAS operators; Brokers and risk engineers; Compliance reviewers; Insurer-facing stakeholders |
| Applicable scenarios |
you are gathering flight-log / Remote-ID / authorisation evidence; you are building an evidence pack before an insurance conversation; you are reviewing operational authorisations |
| Primary command |
ECZ-ID Drone Insurance Readiness: Review / Scan Workspace |
| Inputs |
Drone / UAS operations evidence, operational authorisation (for example SORA), maintenance / airworthiness, operator / registration identifiers |
| Outputs |
An organised evidence pack for insurance review (Insurance Readiness only), an evidence summary, and routes |
| Data handling |
Filenames and paths only; no source / prompt / secret upload; no telemetry; retention none |
| Network behaviour |
Only links you open, plus an optional user-initiated public-interface refresh (GET, allowlisted ECZ-ID host) |
| Result states |
evidence observed; evidence not observed; no public proof reference found yet; review recommended; re-check before reliance; local policy decides |
| Limitations |
Does not issue proof, approve, certify, insure, underwrite, determine compliance, or run checkout |
| Canonical machine discovery |
https://machine.ecocitizenz.org/.well-known/ecz-machine.json |
| Public proof |
https://resolver.ecocitizenz.org |
| Documentation |
https://developers.ecocitizenz.com |
| Supported setup |
https://trustops.ecocitizenz.com/start |
| Re-check |
Re-run before reliance |
Links & support
ECZ-ID is independent trust infrastructure. Third-party names describe compatible ecosystems only and do not imply endorsement or affiliation. Local policy decides whether the evidence you review is sufficient.