Security
Security at SentraOperator.
How we protect a city's calls and records.
SentraOperator answers a public phone line and keeps a city's call records. Security and records handling are built into the service, not added on.
Hosting and encryption
- Calls and data are processed and stored in the United States.
- All traffic to the service, the supervisor console and the phone providers is encrypted in transit (TLS).
- City secrets, such as Sentra 311 integration keys, are encrypted at rest (AES-256-GCM), with the key kept separate from the data.
- Recordings play only through short-lived signed links, and every play is logged.
- Legal holds stop held calls from being deleted by the retention schedule.
Access
- Least-privilege access: each component gets only the permissions it needs.
- Staff sign in to the supervisor console with role-based permissions (supervisor, department staff, records clerk, city attorney, IT admin).
- Every play, download, export, legal hold and settings change is written to an append-only access log the city can review and export.
Every request is verified
- Webhooks from the phone carrier and the voice AI provider are signature-checked; unsigned requests are rejected.
- The agent's tool calls carry a shared secret and are validated against strict input rules.
- The agent can use only the tools a city turns on, and reads back what it's about to file.
Personal data handling
- The call log keeps only the last four digits of a caller's number; the full number is held only while the call is active.
- The agent never asks for card or account numbers, and sensitive numbers are redacted from transcripts.
- Application logs never contain full phone numbers or transcripts.
- After a call ends, an AI model writes the call summary and caller sentiment from a copy of the transcript with phone numbers, card and account numbers and email addresses removed. The provider is listed under Sub-processors and doesn't use the data to train its models.
Retention and deletion
Recordings, transcripts and call-log entries are deleted automatically on each city's schedule by a nightly job. Calls on legal hold are skipped.
Resilience
If the AI path is unavailable, calls fall back to the city's staff number.
Compliance
Our controls are being prepared for a SOC 2 Type II audit in 2027. We support security questionnaires and reviews from city IT: write to [email protected].
Reporting a vulnerability
See security.txt. Please report suspected vulnerabilities privately and give us time to fix them before disclosure.