Public transparency: show the community your drone flights without giving up control of the scene
BabbarOps Public Transparency broadcasts a time-delayed view of the drone flights an agency selects, on a public page that needs no login. The agency chooses which aircraft appear, sets how far behind live the public feed runs, and can shut the page off at any time. Nothing is archived, so there is no public video library to manage or produce.
Every drone program eventually gets the same question, and it usually comes at a council meeting rather than on a call: what exactly are you flying over my house, and who is watching it?
Most agencies answer with a policy PDF. That is the right start, and it is rarely enough. A policy tells the community what you promise. It does not show them anything.
You have a policy, a use-of-force framework, and an annual report. What you do not have is a way to let a resident see for themselves, without handing over control of an active scene.
Start from the default: nothing is public. No feed reaches the public page because a flight happened. A feed is public only because an administrator put that aircraft on the list and left it there. Every control below narrows from there.
What Public Transparency does
It publishes a time-delayed view of the drone flights you select, on a public page that requires no login and no account. A resident opens a link and sees the same feeds you chose to share, running behind live by an amount you set.
The page opens with a plain-language disclosure: why the agency shares this, why it is delayed, that it is not real time and cannot be used to follow an incident as it unfolds, that feeds may be paused or withheld, and that the page is not monitored and is not a way to report an emergency.
What the agency controls
| Control | What it does |
|---|---|
| Aircraft selection | Per-drone opt-in. Only the aircraft you check appear on the public page. SWAT and sensitive assets are never on the list. |
| Public viewer lag | How far behind live the public feed runs. The delay is what keeps tactics, officer positions, and movement from being current. |
| Retention window | The short rolling buffer that makes the delay possible. The public delay must be shorter than this window. |
| Master switch | When on, anyone with the public link can watch your delayed feeds. When off, the link stops working. |
| Access | Only an administrator can enable the page or change which aircraft are on it. A patrol officer cannot publish a feed. |
What stays off the public feed
Sensitivity is usually about the call, not the airframe. A chief does not worry about the drone. He worries about the night that drone gets sent to a suicidal subject, a juvenile victim, or a death investigation. There are three answers, and they cover different situations.
- Aircraft you never opt in. SWAT, covert assets, anything you do not want on a public page under any circumstances. They are simply not on the list, so there is nothing to remember in the moment and nothing to undo under pressure.
- A listed aircraft that catches a call you do not want public. Uncheck that aircraft and save. The public page picks that up on its next refresh, within roughly thirty seconds, and the stream drops. The operational feed your own people are watching does not change, and no other aircraft is affected.
- Everything at once. One switch. When on, anyone with the public link can watch your delayed feeds. When off, the link stops working.
The delay is doing quiet work here. Because the public feed runs behind live, the gap is also a decision window. A supervisor does not have to make the call the instant a drone launches. There is time to see what the flight is turning into and pull it off the public list before it would have reached anyone.
Why delayed instead of live
A live public feed of an in-progress call is a tactical problem, not a transparency win. It broadcasts officer positions, approach routes, and movement to anyone watching, including the person you are looking for.
The delay solves that without gutting the point. The community still sees what the aircraft saw. They just see it after it stops being operationally useful to someone who means harm. That is the trade that makes this defensible to a chief and to a city attorney at the same time.
What it is not
- It is not an archive. The buffer exists only to create the delay, and those segments expire. There is no library of clips to catalog, produce, or hand over.
- It is not a records system. Your existing evidence system stays the system of record. This changes nothing about how you handle video that matters to a case.
- It is not automatic. Nothing goes public because it happened. An aircraft appears on the public page because an administrator put it there.
- It is not a reporting channel. The page states plainly that it is not monitored and that emergencies go to 911.
Where it fits politically
Drone programs rarely die because the technology failed. They die at a council meeting, in front of residents who were never given a reason to trust the program before it launched.
A chief arguing for a drone program, or for expanding one into a Drone as First Responder program, is making a case about accountability as much as capability. Being able to say the flights are visible to the public, on the department's terms, with a switch the department controls, is a different conversation than promising a policy will be followed.
The bottom line
Transparency and operational security are usually treated as a trade. They are not, if you separate them in time. Publish what you choose, behind live, with a switch you hold. The community gets a real look at what the aircraft does. You keep control of the scene.
Not on this page, and that is deliberate. The public feed runs behind live by an amount the agency sets, so it cannot be used to track officer positions or follow an incident as it unfolds. The community sees what the aircraft saw, after it stops being tactically useful to someone who means harm.
No. A short rolling buffer exists only to create the time delay, and those segments expire automatically. There is no archive, no public video library, and nothing to catalog or produce later. Your existing evidence system remains the system of record for video that matters to a case.
An administrator, and only an administrator. Aircraft are opted in one at a time, so SWAT and other sensitive assets are simply never on the list. A patrol officer or a pilot cannot publish a feed to the public page.
Uncheck that aircraft and save. The public page picks it up on its next refresh, within roughly thirty seconds, and the stream drops. No other aircraft is affected, and nothing changes about the feed your own people are watching. Because the public feed also runs behind live by minutes, the delay works as a decision window: a supervisor has time to see what the call is turning into and pull the feed well before it would have reached anyone.
Yes. One switch controls it. When on, anyone with the public link can watch your delayed feeds. When off, the link stops working. Individual aircraft can also be removed from the public list at any time without affecting the operational feed the agency sees.
A flight log portal publishes records after the fact: where an aircraft flew, when, and why. This publishes a delayed view of the flight itself. The two answer different questions, and an agency can reasonably run both. Neither one is a substitute for a published policy and community engagement before launch.
Tell us what your council is asking for, and we will show you what a delayed public feed looks like on your own aircraft.
Sukh Bhela is a California police sergeant who has served as a UAS operator, UAS supervisor, and incident commander during critical incidents. His experience leading patrol operations and integrating drone technology into public safety responses led him to found BabbarOps, where he builds tools for live situational awareness and incident command. He writes about policing, drone operations, leadership, and the technology shaping the future of emergency response.
The views expressed here are the author's own, written in his personal capacity. They do not represent, and are not made on behalf of, any law enforcement agency or employer.
This page describes product capability, not legal advice. Public disclosure obligations, records retention, and privacy requirements vary by state and by agency policy. Confirm your approach with your agency counsel and your records custodian before publishing any feed.