Residents call 311 with their addresses, phone numbers and sometimes more than they meant to share. A city that puts an AI agent on that line should be able to explain what happens to that information. This post is a plain guide to how SentraOperator handles caller privacy.
What callers hear and what they're asked
Privacy starts with telling people what is happening. Every call opens with three lines: the caller is talking to the city's AI assistant, the call may be recorded, and for emergencies they should hang up and dial 911.
Callers know from the first seconds that the call is with an AI and may be recorded. See telling callers it's an AI for why we treat that as non-negotiable.
What the agent asks for
The agent asks only for what a request needs. For most requests, that is:
- the problem, matched to one of the city's Sentra 311 request types
- the address or nearest intersection
- the few details that request type requires
It does not ask for a date of birth, a Social Security number or other identity details. It never asks for card or bank numbers, and it does not take payments by voice. A secure pay-by-text-link feature is on the roadmap but is not available yet.
What gets removed or shortened
Some information is kept only in part, or removed:
- Caller phone numbers. The call log keeps only the last four digits. The full number is held only while the call is active, for example to send a text the caller asked for.
- Sensitive numbers in transcripts. If a caller reads out a card or account number anyway, it is redacted from the transcript.
- Application logs. System logs never contain full phone numbers or transcripts.
Redaction is a safety net, not permission. The agent is designed so callers are not asked for sensitive numbers in the first place.
AI summaries and the model provider
After a call ends, an AI model writes a short summary and notes the caller's sentiment. It works from a copy of the transcript with phone numbers, card and account numbers and email addresses removed. The provider is listed on our sub-processors page and does not use the data to train its models.
The summary is a reading aid for supervisors. It is never used to decide anything about a caller. See AI call summaries and sentiment.
Texts only with a yes
The agent can text a request number, a status link or a form link, but only after the caller says yes. Every text starts with the city's name and ends with "Reply STOP to opt out." STOP is honored. See texting callers.
Who can see a call
Inside the city, access depends on role. Staff sign in to the supervisor console with role-based permissions: supervisor, department staff, records clerk, city attorney and IT admin. Each sees what that role needs.
Every play, download, export, legal hold and settings change is written to an access log that the city can review and export. Recordings play only through short-lived links, and every play is logged.
Calls and data are processed and stored in the United States and encrypted in transit. Access is least-privilege, and every access is logged. Our security page has the details your IT team will ask about.
How long it is kept
Recordings, transcripts and call-log entries are deleted automatically on the retention schedule your city sets. As an example, our demo city keeps audio for 100 days, transcripts for two years and call-log rows for five years. Calls on legal hold are never deleted automatically.
Each department can also choose whether the part of the call after a transfer is recorded. The AI part is always recorded.
Retention and public records rules vary by state. Have your records manager and city attorney set the schedule. This is not legal advice. See recordings and retention and our privacy policy.
Questions to settle before go-live
A short list for the city team:
- Who can play recordings, and who can export them?
- What retention periods match your records schedule?
- Which departments record after a transfer?
- Who reviews the access log, and how often?
- What will you tell a resident who asks what happened to their call?
Having written answers makes it easy to respond when a resident, reporter or council member asks.
The short version
Callers are told up front that they are talking to an AI and may be recorded. The agent asks only for what a request needs, never takes payment numbers, keeps only the last four digits of a caller's number in the log and redacts sensitive numbers from transcripts. Access is by role and every access is logged.