forenzo.io is live: from the interview room to the prosecutor without a disc
The interview ends at 3:40 in the afternoon. Then somebody burns a disc. Somebody fills out a chain of custody form by hand. The detective needs a copy, the prosecutor needs one in September, and by then nobody is certain which copy is the original.
forenzo.io is live. It is a new Network Ninja product, and it connects to Collaborate, the case management system already running in hundreds of Children’s Advocacy Centers. $29 per interview, $19 with your Collaborate code, and the first three are free.
How it works
Upload the recording. A 90 minute interview is usually back in about fifteen.
- Upload. The whole file is fingerprinted on the way in.
- Transcribe. Speakers separated, up to five: an interviewer, a child, an interpreter, an advocate.
- Index. Key disclosures, topics and follow-up flags, each with a timestamp.
- Share. One PIN-protected link per recipient. Nothing to install.
It opens in about a second
Click the recording and it plays. No progress bar, no waiting for a multi-gigabyte file to come down. It streams, so the first frame is there in about a second whether the interview runs twenty minutes or two hours.
Seeking works the same way. Click any line of the transcript and the video is at that second. Not loading toward it. At it. A reviewer who needs the four minutes that matter watches four minutes, and court prep stops being an afternoon of scrubbing with a legal pad.
Your detective never creates a login
Neither does your prosecutor, and neither does a reviewer at another center. Every link carries a PIN and an expiry. Set the PIN or let forenzo.io generate one, and send it separately from the link so the two never travel together. Opens are recorded in the access log, which you can read and they cannot. Revoke it and it stops working. What they watch is their own copy, with their name and email, the case number and CONFIDENTIAL burned into the frame rather than drawn over the player. A copy that walks out says who it was made for.
That covers peer review and case review too. Instead of mailing a DVD to a reviewer at another center, you send a link that expires.
You start in the case, not in forenzo.io
If your center is on Collaborate, one action from the case hands you off, and the recording comes back attached to that case. You sign in through Collaborate. No second login, no retyped case number.
An API anyone can build against
That handoff is not the only way in. forenzo.io has a documented machine-ingest API, and any recorder or case management system can build against it. It is how a center running something other than Collaborate connects what it already has. Nobody carries a file anywhere.
- Your system authenticates with a key issued to your center and hands the recording over tagged with your own case number, so it lands in the right case with the child already attached
- Store your own identifier on it and the record is findable from either side
- It uploads in parallel parts, each hashed on the way, so a part that drops on a bad connection retries itself instead of restarting the file
- The server rehashes the whole stored file, not the parts, and a mismatch cancels processing rather than quietly moving a bad file downstream
- Machine uploads land in the same audit log your team’s clicks do
Ask us for the guide and we will turn the API on for your organization.
Catching what the machine mishears
Transcription runs on AWS Transcribe. On a child speaking at the edge of audible, any engine writes down a guess. What separates platforms is what happens next.
Click a segment and you get every reading the engine considered, with its confidence. Below, it offers four and every one is wrong. That is what Write-in is for, and why a person who knows the vocabulary does the review. Your correction is stored beside the original, never over it.
What it leaves behind
A SHA-256 hash at upload, and an access log that records views, tags, corrections and speaker renames, with the person and the timestamp to the second on every row. Nothing in it can be changed afterward, including by us: the database rejects any attempt to update or delete a row. Ask it to re-verify years later, before you rely on that file in a proceeding, and it re-reads the stored file and re-attests.
If you ever leave, you take all of it: every case, recording, transcript, correction and audit entry in one export, each file hashed, with a root hash over the bundle so whoever receives it can confirm nothing was altered without contacting us.
CJIS Security Policy v6.0, mapped control by control, and we send the whole matrix rather than a summary. The HIPAA Business Associate Agreement is signable in the product. Network Ninja is SOC 2 certified at the company level and Collaborate at the product level, both by third-party audit.
The first three interviews are free at forenzo.io. Contact us for a demo if your center pays by check, or your state chapter is buying for its members.
