Live-only by design: why storing no video removes your biggest compliance burden
Live-only means Live Command shows live video from drones, aircraft, cameras and witness phones and does not record it. The heaviest compliance obligations, retention schedules, discovery and chain of custody, attach to a stored file. With no file, those obligations never start. Your evidence system stays the system of record, and what is left to govern is access.
When an agency evaluates any new video platform, the IT director and the records custodian ask the same question before anyone talks about features: “What happens to the data, and who is responsible for it?”
It’s the right question. Stored law-enforcement video is one of the most heavily regulated categories of data an agency holds. The moment a system retains incident footage, it inherits a long list of obligations, and a long list of risks.
The burden lives in the storage
Most of the compliance weight in public-safety video isn’t the live feed. It’s what happens after: the retained file, sitting on a server, for months or years.
Stored criminal-justice information brings requirements and exposure around:
- Retention and disposition schedules: how long footage must be kept, and how it must be destroyed.
- Records requests and discovery: every retained file is potentially discoverable and subject to public-records law.
- Chain of custody and audit: proving who accessed stored evidence, when, and why.
- System-of-record obligations: once you store it, you may be expected to manage it as evidence.
That’s the part agencies dread inheriting from a new vendor: another store of sensitive video to secure, audit, retain, and eventually answer for.
What “live-only” actually means
BabbarOps is the live operational layer during an incident: the shared picture every role works from in real time. It is deliberately not a system of record, a DVR, or an evidence-management platform.
Video from drones, aircraft, fixed cameras, and witness phones (EyesOn) goes to the dashboard and shows live. BabbarOps does not record or retain it. When the stream ends, there is no incident video file left behind in the platform.
That one architectural decision removes the heaviest obligations before they start:
- No retained incident video means no retention schedule to manage and no stored footage to secure.
- No stored footage means the platform isn’t holding a new pool of discoverable, records-requestable evidence.
- Your existing evidence system stays the system of record. BabbarOps doesn’t compete with it or duplicate it.
Not a system of record, on purpose
Calling a platform “not a system of record” can sound like a limitation. It’s the opposite. It’s a deliberate line between two jobs that get confused in public-safety video:
- The live picture: what’s happening right now, who needs to see it, and what decision it drives. This changes outcomes during the call.
- The record: the retained file, managed as evidence, subject to retention schedules, discovery, and chain of custody. This creates obligations after the call.
Your body-worn camera platform, evidence management, and RMS already own the record. BabbarOps owns the live picture, and stays out of the record entirely.
What still matters when nothing is stored
Most of what a records custodian has to defend attaches to a file that exists. Remove the file and most of the questions go with it.
What still matters for a live platform is narrower and centers on access, not the archive:
- Access control: only authorized, authenticated agency personnel can view feeds.
- Audit: a record of who was let in, who was removed, and who changed what.
Live Command is built for the access question: people sign in through the department’s own directory, three roles decide who can run a feed and who can only watch, and the audit log is kept where no one can edit it.
Why this is an advantage, not a limitation
Agencies already have systems of record: body-worn camera platforms, evidence management, RMS. What they don’t have is a clean, low-risk way to see the live picture during the incident without standing up one more regulated data store. Live-only means:
- Faster to adopt: far less to review when the data never persists in the platform.
- Lower ongoing risk: no growing archive of sensitive video to secure and answer for.
- Cleaner boundaries: your evidence system stays the system of record; BabbarOps stays the live picture.
For an agency weighing real-time situational awareness against the compliance cost of another video store, that distinction is the whole point. The live picture changes outcomes during a call. The stored file creates obligations afterward. BabbarOps gives you the first without the second.
No. BabbarOps is live-only by design. Video from drones, aircraft, fixed cameras, and witness phones is displayed live on the dashboard and is never written to storage. When the stream ends, there is no incident video file left behind in the platform.
No, deliberately. Your body-worn camera platform, evidence management system, and RMS already own the record. BabbarOps owns the live picture during the incident and stays out of the record entirely. It is not a DVR or an evidence-management platform.
Because BabbarOps retains no incident video, the platform isn't holding a new pool of discoverable, records-requestable footage. The obligations that attach to stored video (retention schedules, discovery, chain of custody) follow the retained file, and BabbarOps leaves no retained video behind. Confirm specific requirements with your agency's legal and IT authorities.
Most of what a records custodian has to defend attaches to a file that exists. With no stored video, the questions left are who can see a feed and who did what. Live Command answers both: people sign in through the department's own directory, three roles decide who can run a feed and who can only watch, and the audit log is kept where no one can edit it.
Amit Hadke is a distributed systems engineer with more than 20 years building real-time infrastructure at scale, at Twitter, Oracle, MapR, Nextdoor, Dremio and Pixeltable. He owns the platform side of BabbarOps: the streaming path that has to hold up on a bad uplink, and the GovCloud deployment Incident Command runs in. The architecture described on this page is his.
Sources
Key claims above concern how retention obligations attach to stored data. The primary references:
- FBI, Criminal Justice Information Services (CJIS) Division: the CJIS Security Policy and its audit and handling requirements, which attach to criminal justice information you store.
- California Government Code section 34090: the city-records destruction rule. It bars destroying a city record less than two years old, which is why retention decisions belong to the agency rather than to a vendor.
This article describes BabbarOps’ architecture at a general level and is not legal or compliance advice. CJIS and records-retention obligations vary by state and agency; confirm requirements with your agency’s legal and IT authorities. BabbarOps is an independent commercial product and is not affiliated with or endorsed by any law enforcement agency.
