Trust + Security
Officers trust us with their words. We take that seriously.
Officers told us in our very first interviews that privacy and access control mattered as much as speed. Here's how we protect data, and an honest view of where our compliance stands.
Your data, your rules.
Minimum data
We collect only what a workflow needs. In pilots, your organization decides which systems Zenext can reach.
Your records, your policy
Transcripts and reports are kept according to your organization's own information policy, so they can be reviewed later.
No sensitive data on this website
Our contact forms ask you not to share incident, medical or confidential details.
Where data lives
Hosting region and retention are agreed with each pilot partner and documented before any data is collected.
Security built into the design.
| Role-based access | Users reach only the data and actions their role allows, with hierarchical groups for officers, supervisors and dispatch. |
|---|---|
| Encryption | Data encryption keys are protected by AES key wrapping (envelope encryption), as described in our IEEE CCWC 2020 paper. |
| Human confirmation | Actions and reports are confirmed by a person before they're sent or saved. Our AI principles |
| Reviewable record | Conversations and confirmations are logged so supervisors can review them after the event. |
| Private deployment | Our architecture research includes private-cloud and on-premises options for agencies that need them. |
AI-assisted reports you can stand behind.
Incident reports can become evidence in Title IX, Clery, workplace and civil matters. Zenext treats AI as a drafting aid, never the author.
- Officer review + signature. Nothing is filed until the officer reviews and signs.
- Labelled “AI-assisted”. Every report shows that AI helped draft it.
- Source kept. The original audio and transcript stay attached to the report.
- Full edit history. Every change between draft and signed report is recorded.
Privacy for the officers who use it.
| Location | Designed to share location only while an officer is on shift or during an alert, never off duty. |
|---|---|
| Recording | Voice is captured only while push-to-talk is active. Your organization sets notice and consent policies for its jurisdiction. |
| Who sees what | Supervisors see their own teams; access follows your roles and chain of command. |
| Retention | Your organization decides how long transcripts, locations and reports are kept. |
Compliance, stated plainly.
What each kind of buyer asks for, and where we are. We'd rather tell you than overstate it.
| CJIS Security Policy | Required only for sworn campus police connecting CJIS checks. Our prototypes are designed around CJIS requirements. We share our approach with sworn campus police partners on request. |
|---|---|
| SOC 2 | Not yet audited. We share our security approach with partners on request. |
| Universities: HECVAT + FERPA | We complete security questionnaires such as HECVAT on request, and handle student records under FERPA agreements with each university. |
| Hospitals: HIPAA BAA | Agreed during pilot scoping with each healthcare partner. |
| K-12: student data privacy | Agreed with each district during pilot scoping. |
| Privacy law | Our data handling is designed around Canada's PIPEDA, Québec's Law 25 and applicable US state laws. See our privacy policy (in legal review). |
| Accessibility | This website follows WCAG 2.2 AA practices: readable type, 44 px targets, dark mode and reduced motion. |
Report a security issue
Found a vulnerability in our website or software? Please tell us privately and we'll respond quickly.
Questions from research partners?
We'll share architecture details and complete security questionnaires for agencies and partners in our studies.