Starting today, Roger requires a verified credential. It is not open to the general public.
We want to explain why, plainly, and without pretending the decision was obvious.
The obligation comes first
Every transmission Roger processes was made by someone on shift. A dispatcher. A medic. A trooper alone on a road at two in the morning.
They are not sources. They did not opt in. They keyed a microphone because they were doing a job that most people are grateful never to have to do, and their voice ended up in our system as a consequence of that.
We think that creates an obligation, and we think the obligation runs to them before it runs to our growth.
A tool that can assemble an operational picture in real time is a tool that, left open, could be pointed at the people inside that picture. We are not going to describe how, and we are not going to pretend the possibility is not there.
What we will describe is where our line sits, because a line is more useful than a warning.
So we are closing a door that was open, before anyone asked us to.
What we have built, and why it changes the question
Public safety radio has been listenable for as long as there have been radios. Hobbyists, reporters, and neighbors have tuned in for decades. That is public, it is lawful, and we are not arguing otherwise.
What changed is not the radio. It is everything downstream of it.
Roger does not transcribe radio. Transcription is the first ten percent.
What we build is an ontology of the network itself. Who was where, at what time, on what channel, and who else was in it with them. Not a list of sentences. A structure.
The structure is what lets us cross the lines that everything else stops at.
Agency lines. Jurisdiction lines. Talkgroup lines. A radio system is designed to keep traffic separated, and every tool built on top of one inherits that separation. You listen to a channel. You listen to another channel. Nothing joins them.
Roger joins them. In real time, while the incident is still unfolding, not in an archive assembled afterward.
Here is what that means.
A trooper calls out a pursuit. The vehicle crosses a district line, then a county line, and what was one agency's problem becomes three. Different departments. Different talkgroups. Different radio systems entirely. Roger follows it across all of them, because Roger is not listening to a channel. It is listening to an incident.
The pursuit ends. A car is off the road and on fire. Roger already knows a fire apparatus was dispatched there, because it heard the dispatch on a channel no officer in that pursuit could hear, and it knows it is the same location, because it resolved two different descriptions to a single place. A suspect is apprehended. EMS is en route to the scene.
Four agencies. Multiple systems. A dozen voices, none of whom said the same thing the same way. One picture, assembled live.
Nobody hands us that structure. We build it. That is the product, and we are proud of it.
What we are not going to claim
We are not going to tell you the components are exotic. They are not. Speech models, entity resolution, retrieval, radio hardware. Any of it can be bought this afternoon.
Assembling them into something that actually works, across agencies, across systems, in real time, is the hard part, and it is the part we did.
But we are not going to pretend that a decision we make holds the line for an entire industry. It does not. Someone else will build toward this. Our restraint does not stop them.
That is not an argument against restraint. It is an argument for being explicit about what ours is.
We are not claiming to have solved this. We are telling you where our line is, we are drawing it before we were forced to, and we invite you to hold everyone in this category to the same one.
Why this is not the app on your phone
Someone will say this already exists. There are consumer safety apps that push incidents to your phone, and a few of them are well known.
They are broadcasts. An incident is selected, summarized, and sent to you. You receive it. That is the whole interaction. What reaches the feed is an editorial decision made upstream, the depth stops where the summary stops, and there is nothing underneath it to open.
Roger is not a broadcast. It is the record underneath, and it is interrogable.
You are not handed a card that says there was a pursuit. You have the pursuit. The traffic, the agencies, the sequence, the resolution, and an AI you can put questions to. Who else was on that channel. What was dispatched, and when. What happened before the call that made the call make sense. Ask, and keep asking, and the system keeps answering, because the structure underneath goes as deep as the questions do.
That is a categorically different object. A summary feed can be handed to everyone because it is shallow and edited on purpose. Ours is neither, by design.
We are not going to treat that difference as a marketing advantage and then act as though it carries no weight. It is the reason Roger sits behind a credential and an alert feed does not.
Who can get access
Verified public safety personnel. Credentialed newsrooms and working journalists. Institutional partners with a legitimate operational need.
Verification is a review, not a checkbox. We decline requests, and we will keep declining them.
If you already have an account, nothing breaks today. Existing users keep access through a transition window while credentialing opens, and we will contact you directly with the timeline.
This costs us reach. We are choosing it anyway.
What we will not tell you
We are being deliberately incomplete about how the safeguards work, and we would rather say so than let you notice.
We will not publish how identity is bound, how misuse is detected, or how access is scoped. Publishing a safeguard is an efficient way to publish its bypass.
What we will commit to in public:
Access is verified, not asserted. Access is scoped to what a credential has a reason to see. Access is revocable, and we revoke it.
And one commitment we hold in full public view.
A verified first responder can look at their own activity. Their own traffic, their own shift, their own night. That is a real capability and we think it is a good one.
No one gets that view of anyone else. Not a newsroom. Not an enterprise. Not another officer, in their own department or any other. Being a first responder gets you a window into your own work. It does not get you a window into anybody else's.
We will not build, sell, or provide a capability that surfaces the activity of an identifiable individual officer to anyone other than that officer and their own agency. Not at any price.
That is a permanent constraint on what this company is allowed to become, and we are writing it down so you can hold us to it.
Agencies who want the mechanism rather than the summary should ask us directly. That conversation belongs in a room.
What Roger is not
Roger is not a system of record and we are not asking anyone to treat it as one.
An officer curious about how a pursuit unfolded, or what a night looked like from outside their own channel, should be able to see that. That is what Roger is for. It is not dispatch, it is not a duty system, and it does not carry a guarantee of accuracy, completeness, or uptime.
Your CAD, your dispatcher, and your radio are your primary sources. They remain your primary sources. Roger sits alongside them for the people who are curious about their own work, and it should never sit in front of them.
We would rather say that now, clearly, than have anyone infer otherwise later.
As we grow
Roger is not standing still. Coverage is expanding and the system gets sharper as it gets wider.
A capability like this does not become more comfortable to leave open as it improves. It becomes less.
We would rather set the terms while the decision is still freely ours, and grow into a shape we chose, than be handed one later by an incident we could have prevented.
Being proud of a thing and being careful with it are not in tension. They are the same discipline.
Roger is powerful. That is the reason for the door, not an exception to it.
