Begin with information classification
Most privacy failures start before a prompt is written. Someone has a document, a call note, a personnel question, or a draft report and wants help organizing it. The first question should not be “Which tool should I use?” It should be “What kind of information is this, and what rules apply?”
Departments may handle protected health information, personally identifiable information, personnel records, juvenile information, investigation material, security-sensitive details, public-records content, and confidential legal or procurement information. The exact categories and obligations depend on the department and jurisdiction. Your policy, counsel, records officer, information-security staff, and other responsible authorities should define the boundaries.
Five privacy controls leaders can put in place
1. Create a simple data decision tree
Give staff a short path: Is the information public? Is it department-internal but non-sensitive? Does it contain PHI, personnel data, an active investigation, credentials, protected addresses, or security-sensitive details? If the answer is unclear, the default should be to stop and ask the designated authority rather than guess.
2. Define approved tools and accounts
A personal account and a department-approved account may not have the same controls, retention terms, administrative visibility, or contractual protections. Identify which tools are approved for which classes of work. If no tool is approved for a category of information, the answer is not to work around the rule.
3. Minimize before you prompt
When an approved workflow allows AI assistance, remove unnecessary names, identifiers, exact addresses, phone numbers, medical details, credentials, and other sensitive fields. Use a representative or synthetic example for training whenever possible. Minimization reduces exposure, but it does not automatically make a workflow compliant or appropriate.
4. Keep a human reviewer accountable
Privacy protection does not end when the prompt is submitted. Review the output for unsupported claims, copied sensitive information, incorrect inferences, accidental disclosure, and inappropriate recommendations. The person responsible for the department product remains accountable for the final decision and communication.
5. Ask vendors precise questions
Before a department adopts an AI product, ask where data is processed and stored, how long it is retained, who can access it, whether it is used to train a model, how deletion works, what audit logs exist, what subcontractors are involved, and how the vendor handles an incident. Ask for the actual terms and documentation, not only a verbal assurance in a demonstration.
Privacy and public records can overlap
A document can be sensitive for one reason and still become a public record for another. AI prompts, outputs, drafts, logs, and vendor records may raise retention, discovery, or disclosure questions depending on the task and jurisdiction. Do not promise staff that deleting a chat solves a records issue, and do not promise that a vendor’s retention setting answers every legal question. Coordinate the workflow with the people responsible for records and legal review.
Safe first exercises
Leaders can build familiarity without using sensitive operational data. Try a public-education draft, a generic training scenario, a fictional incident narrative, a meeting-summary example with synthetic notes, or a policy-outline exercise using publicly available material. The purpose is to learn the tool’s strengths and failure modes while keeping the exercise bounded.
Questions to answer before expansion
- Which information classes are allowed, restricted, or prohibited?
- Which tools and accounts are approved?
- Who can authorize a pilot?
- What review is required before an output is shared or published?
- How are prompts, outputs, and incidents handled under records rules?
- Who updates the policy when the tool or law changes?
Privacy-first AI adoption is not about making every task impossible. It is about putting the department’s judgment before the tool’s convenience.
Make the safe path the easy path
People are more likely to follow a privacy rule when the department gives them a practical alternative. Provide approved examples, a short request path for new tools, and a review checklist that can be completed without legal or technical jargon. If staff have to guess which system is approved or who can answer a question, the policy is creating pressure to work around it.
Privacy review should include the people who understand the actual workflow. A chief may set the expectation, while an EMS leader, records officer, information-security specialist, training officer, or counsel may identify a specific risk. The point is not to slow every experiment. It is to make sure a useful experiment does not quietly become an uncontrolled department practice.
Related resources: Readiness Call · AI Readiness Checklist · REACT Guide · Consulting · Training.