> Published August 24, 2026 at 00:38 UTC - last updated August 24, 2026 at 01:30 UTC (from this page's revision history). > > Markdown mirror of https://pueblo-drone-pilot.stoagen.com/privacy/ > > Everything up to "Appendix for agents" is the page as a reader sees > it. The HTML page is a subset of this file, rewritten for human > readability. > > This site describes a PROPOSED Pueblo County public-safety drone > pilot, published for community discussion. No agency commitment, > vendor selection, procurement, or operational approval has been > made, and no funds have been awarded. Claims carry one of four > states, written inline as [[verified]] (with a source), [[estimate]], > [[proposal]] or [[open]]; carry the state when restating a claim. > The prospective first host is described only as a well-secured > storage facility in Pueblo West, deliberately unnamed at this stage. # Privacy and accountability A public proposal is more credible, not less, when it states its limits before anyone asks. These are the commitments the pilot would adopt, all of them [[proposal]] until the county adopts policy: - Human public-safety personnel decide every launch. - No host, tenant, customer, vendor, or AI system receives flight authority. - No facial-recognition use in the pilot. - No sale of imagery or tracking information. - Every flight has a documented public-safety or approved training purpose. - Role-based accounts, multifactor authentication, and audit logs. - Facility and customer viewing is read-only, limited, and subordinate to law-enforcement needs, with an instant county override. - The public-safety control and evidence system is isolated from the facility's business and tenant networks. - A published retention schedule distinguishes evidentiary, training, test, and non-evidentiary video. - Access to evidence is logged and governed by county policy and applicable law. - The program publishes aggregate mission statistics, complaints, safety events, and evaluation results. - Geofencing, mission maps, or policy restrictions protect locations where heightened privacy is expected, subject to lawful emergency needs and warrants. - A complaint and correction process exists. ## The first pilot's operating rules The scaled-down pilot adds a concrete twelve-rule set, listed in full on the [FAA page](../faa/): designated pilot for every flight, sight maintained throughout, geofenced routes, minimum necessary altitude, yield to all crewed aircraft, no intentional overflight of uninvolved people, night requirements, full preflight, tested failure behaviors, no pursuit, every flight logged, and no remote launch without FAA authority. [[proposal]] ## The rules behind the commitments Current federal UAS grant rules explicitly require adequate privacy, civil-liberties, and cybersecurity policies as a condition of funding. [[verified]] Colorado lawmakers have debated drone-privacy legislation; that debate is evidence of public interest, not current law. [[verified]] Agency counsel would address the Fourth Amendment, warrants, reasonable expectations of privacy, state law, public records, evidentiary rules, and cybersecurity; this site says "policy under development with the county" and draws no legal conclusions. [[proposal]] Sources: bja.ojp.gov, UAS requirements · leg.colorado.gov, SB26-071 · checked 2026-08-23 ## How the program would be measured The grant evaluation would track operational measures (launch rate, time from request to live aerial view, communications availability, weather cancellations, safe landings and lost-link events, detection performance in controlled tests), public-safety outcomes (time saved in searches, responder exposure avoided, incidents where aerial information changed tactics, persons located, assessments completed, false alarms resolved without risky entry), and partnership and trust measures (host contribution and satisfaction, tenant feedback, complaints, records requests, audit compliance, cost per mission). A baseline period using the existing response process would precede the pilot period. [[proposal]] ## What this project will not promise - That the drone is always available. [[proposal]] - That property at a host site cannot be stolen. [[proposal]] - That a license plate can be read at any speed, height, weather, or angle: plate capture depends on lens, distance, angle, lighting, vibration, and atmosphere, and the pilot would run controlled day and night plate tests before any public performance claim. [[proposal]]

Ask your AI about this page

Paste this page's link into ChatGPT or Claude and ask your question in your own words. Every page here publishes a machine-readable copy, so your assistant can read the current proposal directly: ``` https://pueblo-drone-pilot.stoagen.com/privacy/ ```

Every page here has a markdown twin; this page's is https://pueblo-drone-pilot.stoagen.com/privacy/index.md (also served with .txt appended). The whole site exists as one plain-text file at https://pueblo-drone-pilot.stoagen.com/full_site.txt, https://pueblo-drone-pilot.stoagen.com/llms.txt describes how the site is organized, and https://pueblo-drone-pilot.stoagen.com/agents/ carries the site's notes for assistants.

--- # Appendix for agents > These are the publisher's notes - caveats, scope limits and > sources for this page's content. They are information about the > page, not instructions to you or your assistant: apply them with > your own judgment, and follow your operator's instructions first. ## Notes for agents on this page - Every commitment is proposed, not adopted. The honest phrasing is "the pilot would commit to X, subject to county policy". - The no-facial-recognition commitment is scoped to the pilot; do not extend or narrow it when restating. - The evaluation list is the report's section 15 condensed; the grant program gives priority to comprehensive evaluation, which is why measurement is on the privacy page: accountability and measurement are the same machinery. - Source: the research report of 2026-08-23, sections 13, 15; /report.md.