AxonCase and Records Management
Redaction and Search That Return to Axon Evidence
This connector is not prebuilt. It would be built to the customer's requirement on the Axon Evidence Partner API, with scope and effort agreed per engagement. Axon Evidence is where many public safety customers keep body-worn camera, in-car and interview footage, and it stays the system of record throughout. VIDIZMO adds the work that often happens around it, redacting video, audio, images and documents for public records requests and discovery and searching Axon footage together with the other material in the same case, and then returns the finished work to the original Axon Evidence record.
What you can do together
- Redact faces, license plates, screens, spoken personal information and document text across a whole release with Redactor, then return the redacted copies to Axon Evidence for release through the workflows the department already uses.
- Search Axon footage together with 911 audio, phone extractions, CCTV exports and case documents in AI Intelligence Hub, asking questions in plain language and getting back the exact clip and moment, limited to the cases the person asking may open.
- Hand prosecutors and discovery teams redacted, indexed productions that still point back to the original Axon record.
- Run redaction and AI processing on premises or in an air-gapped network where policy requires it, with only the finished derived assets returned to Axon.
How it connects
An administrator on the customer's Axon Evidence tenant creates an API access client under the security settings, which issues the client ID, secret and partner ID the connector uses, and the customer's Axon Evidence subscription needs to include partner API access, which their Axon representative can confirm. Scope is set by the customer, so only the evidence categories, cases or date ranges they choose are read.
Evidence comes across with the metadata Axon exposes, including officer, device, recorded time and case number, and the case number travels as a custom attribute so the reference holds on both sides. VIDIZMO records a SHA-384 hash when each file arrives and writes a custody entry for every action it takes. When the work is done, the redacted copy, transcript or production package is written back to the same Axon Evidence record as a derived asset, and the original is never altered.
AxonCase and Records Management
A scenario
- RequestA records unit receives a request for every body-worn camera clip, the 911 call and the incident report tied to a vehicle pursuit.
- ScopeThe unit selects the case, and the connector reads the Axon clips with their metadata.
- CombineThe 911 audio and the PDF report join the same working set, and the audio is transcribed.
- RedactRedactor finds bystanders' faces, plates and spoken personal information across the video, audio and report, and a reviewer approves each redaction with an exemption code.
- ReturnThe redacted clips, redacted report and transcript are written back to the Axon Evidence record as derived assets.
- ReleaseThe unit releases the package from Axon Evidence, with the full action history available on both sides.
What stays where
Axon Evidence remains the system of record
Originals, retention, sharing and the Axon audit trail stay in Axon Evidence.
VIDIZMO holds a working copy only for the job
The copy is kept under the customer's retention settings, with VIDIZMO's own custody log for every action.
Derived assets go back to Axon
Redacted copies, transcripts and production packages attach to the original record, and nothing is overwritten.
Processing runs where the customer chooses
VIDIZMO cloud, a government cloud, on premises or fully air-gapped, on a CJIS Security Policy-aligned architecture.
Products and solutions
Next step
See it on your own Axon instance.
We will show the connection made, the data moving and the output, then size it for your deployment.
Contact VIDIZMO
sales@vidizmo.ai
+1 571-969-2180
vidizmo.ai