Security
PatrolDocs doesn't store victim names, incident narratives, or defendant names. There's no field for any of it. That's not a policy we follow, it's a decision built into the database itself.
We're a small platform in active pilot, not a Fortune 500 vendor, and we'd rather tell you exactly where things stand than oversell it.
When an officer delivers a document to someone, we keep a record that the delivery happened: which documents, when, and which agency officer sent it. We do not keep the recipient's full phone number or email address. A phone number is stored as its last four digits. An email address is stored as the first character and the domain. The full contact information exists in our systems only for the moment it takes to send the message, then it's gone from our side. The message itself still has to reach the recipient through Twilio or Resend, our delivery partners, the same way any text or email gets sent.
If an officer logs a case or kit number, that's agency-configurable. It's a quick-reference identifier, similar in purpose to a case number printed on a business card, meant to give the recipient something concrete to reference with customer service or a records clerk if they follow up later — not an investigative field. Some agencies want it displayed on the recipient's page, some don't. You decide.
The documents that go through PatrolDocs are the same ones your agency already hands someone on paper: Marsy's Law cards, statutory victim notices, and community resource cards. We didn't invent new sensitive data by building this. We changed how it gets to the person who needs it: instant, trackable, and pulled from the agency's centrally managed library instead of whatever happens to be left in the posse box.
Every agency's data is walled off from every other agency's at the database level. Inside your agency, Officers use the mobile app to create deliveries but do not have a browse or search view of their own past deliveries in the app. A records supervisor or admin sees the whole agency's activity. PatrolDocs staff do not routinely review agency delivery content. Administrative access is limited to authorized platform functions, support, security, and troubleshooting, and is scoped to what's operationally necessary. Administrative mutations, including document changes, account changes, Agency lifecycle actions, and permission changes, are logged; simply viewing a record without changing it does not currently generate a separate log entry.
You set how long delivery records stick around, from one year to seven, with a three-year default. Audit logs run separately on a fixed seven-year floor regardless of what you pick for everything else, because that's the record that matters if anyone ever needs to reconstruct who did what.
We're a small platform in active pilot, not a Fortune 500 vendor, and we'd rather tell you exactly where things stand than oversell it.
Questions about how this fits your agency's IT policy? Reach out and we'll walk through it directly, not through a sales deck.
legal@patroldocs.com
775-600-0453
PATROL