8. T raining and Onboarding
Axon’s team will provide hands-on training for relevant personnel, user credentials and access to supporting applications, and operational guidance tailored to the current system configuration.
9. General Responsibilities
9.1. Axon will: (a) install, configure, and maintain all hardware at designated location site; (b) validate system power, connectivity, and functionality of Outpost; (c) integrate Outpost with Fusus, including NCIC and state hotlists; and (d) will provide training, documentation, and technical support to Customer personnel.
9.2. Customer will: (a) fund and maintain all legally required permits, authorizations, and/or licensing to place, maintain, and/or remove the Outpost at the installation sites; (b) ensure access to installation sites, support device placement communication, and coordinate internally (e.g., facilities, IT, legal, public safety) to facilitate deployment; (c) support scheduling for permitting and local compliance requirements; (d) designate a primary and backup point of contact; and (e) support site selection, utility clearance, and installation approvals.
Signature Date Signed
8/19/2026
Axon Enterprise, Inc. Doc ID: 36476a9332e2 T ax estimates are approximate and subject to change at time of invoicing.
Q-908995-001 • Page 6 of 6
That is the foundation Fleet 3, Outpost, and Lightpost are validated by independent third-party assessments, and proven across years of mobile ALPR deployments. The pages that follow show how it works in practice.
Built for Public Safety.
Governed for Accountability.
Privacy, security, and compliance across Axon Vehicle Intelligence.
Vehicle Intelligence
At a glance
Data ownership
Agencies own and control their ALPR data. Axon
does not pool, resell, or independently disclose it.
Sharing
Off by default. Invite-only, visible, time-bound,
and revocable.
Lawful requests
Routed to the agency as the data owner. Axon
does not independently disclose customer data.
Federal access
No back door, no centralized pool. No automatic or
standing federal access.
Retention
Agency-con/f_igured and automatically enforced.
Non-evidentiary ALPR data purge per policy.
Audit
Every access logged with user, action, time, and
stated reason, in immutable audit logs.
Agencies own and control their ALPR data. Sharing is explicit, permission- based, and revocable. Lawful requests go through the agency for read and hit data, not Axon. Retention is short, con/f_igurable, and automatically enforced. Every action is logged in immutable audit logs that hold up in a council chamber, a courtroom, or an oversight review.
ATTACHMENT C
axon.com
1. Your data, your control
Agencies own and control their ALPR data. Axon does not pool, resell, or independently disclose agency data.
The eight points below are how that principle is implemented in practice.
Data ownership
The agency owns and controls its ALPR data. Axon
does not have access to agency data and does not
use agency data for any other purpose, including
resale or independent analysis. Any external request
for data, including subpoenas, warrants, or FOIA
requests, would be directed to the agency itself, and
the agency would determine how to respond under
applicable law and its own policies.
Cross-agency sharing
Cross-agency sharing capabilities are planned for Q3
2026. Sharing relationships will be invite-only, visible, and revocable. Every relationship will be managed in the agency’s Axon environment and will require an explicit
invitation. Shared access will not create copies of
records, recipient agencies will not take ownership, and there will be no national lookup or unrestricted network.
Lawful requests
Legal process requests are directed to the agency, and
every step is logged. If a subpoena, warrant, or FOIA
request is directed to Axon, we object and route it to
the agency as the data owner. Axon Evidence audit
logs preserve each step so councils and oversight
bodies can con/f_irm lawful procedures were followed.
Retention
Agencies set retention, and data is purged automat-
ically. ALPR data is transferred into the agency’s
secure instance of Axon Evidence, where retention
periods are con/f_igured. Non-evidentiary ALPR data is
automatically deleted per agency policy. Axon pro-
vides recommended defaults, and agencies con/f_igure
and control the settings themselves.
Access tracking
Every access is recorded, including who accessed
the data, what actions were taken, and when access
occurred. Immutable audit logs in Axon Evidence
capture the user, action, time, and, when con/f_igured, the stated reason for access. Both Axon Evidence and
Fusus provide audit capabilities that allow agencies to review activity at any time.
Sharing controls
Sharing is o ff by default, con /f_igurable based on
agency policy, revocable, and can be time-bound.
Sharing does not involve copying or redistributing
ALPR data. Access is federated, allowing recipient
agencies to query authorized data without taking
ownership, and access can be revoked immediately
by the donor agency.
AI model training
Axon may use transformed ALPR data from customers
who have opted to participate in Axon’s Customer
Experience Improvement Program (ACEIP). Full plate
reads are not used. Customers may opt out at any time
by contacting [email protected].
Federal access
There is no back door or centralized pool for federal
access. Any federal access requires either valid legal
process directed to the agency or an agency-approved
sharing relationship. Even when a sharing relationship
exists, the agency must approve the request before
data is shared. All access is permissioned and logged.
Transparency
Agencies receive access to the ALPR Policy and Usage
Transparency Por tal in A xon Evidence, which can be
con/f_igured to publish retention policies, usage metrics, and program details on a public-facing website. Agen-
cies control what is published and may disable the
portal at any time.
axon.com
2. Built to be secure
Device security and hardware integrity
• Secure boot: Each stage of the boot process is cryp-
tographically validated; only Axon-signed firmware
runs on the device.
• Encrypted storage: AES-256 encrypted partition
with hardware-backed key protection covers ALPR
reads, context video, authentication tokens, configu-
ration files, and logs.
• Physical security: Physical interfaces (e.g., USB)
support only approved functions and are locked
against interactive access.
• Controlled firmware and updates: OTA firmware
packages are cryptographically signed and validated
before installation. Third-party penetration testing is performed under Axon’s Trust & Assurance program.
Secure access and role management
• Device access: Devices have no exposed local login
interface; configuration occurs through authenti-
cated Axon workflows. Pairing requires authenti-
cated provisioning via Axon’s installer with signed
tokens and encrypted channels.
• Agency access controls: Through Axon Evidence
and Fusus, agencies assign to the device role-based
permissions, enforce least-privilege access (including
export and retention restrictions), and use SSO and
MFA to align with their authentication standards.
• Audit and accountability: Every action, user activity, access attempts, configuration changes, sharing
decisions, data exports, is recorded in immutable
audit logs to maintain evidentiary integrity.
Data and network security
• Data in transit: TLS 1.2+ with cryptographic modules
protects uploads to Axon Evidence and Fusus.
Devices authenticate using hardware-protected cer-
tificates and signed tokens, preventing spoofing.
• Data at rest: AES-256 encryption protects all
stored data.
• Network defenses: Firewall enforcement permits
only essential outbound communication; inbound
interfaces are restricted by default. Store-and-for-
ward reliability buffers ALPR data on encrypted
storage if connectivity is lost.
ALPR audit capability:
Beginning April 2026, agencies have access to a one-
button ALPR audit report built directly into Axon Fusus.
The report is designed to make compliance reporting
easy, repeatable, and defensible. It captures officer-level access activity including user identity, the action taken, timestamp, and the stated reason for each ALPR
access. It’ll also show activity by external agencies with whom you decide to share your ALPR data, when ALPR
Sharing launches in Q3 2026.
The report is built for supervisory review, internal
affairs, and oversight bodies that require full account- ability detail. For external sharing such as FOIA
requests, agencies can choose to remove PII and inves-
tigative details like officer name, plate number, and case number etc. before sharing the report. This pulls the
data from the same immutable audit log infrastructure
that underlies all of Axon Evidence.
Axon ALPR cameras are engineered as /f_ield-deployable platforms with built-in protections aligned to Axon’s Secure by Design principles, validated by internal testing and independent third-party assessments. axon.com
3. Where Axon stands apart
Design area Agency-controlled model (Axon) Shared / network-based model Where data lives Within an agency-controlled environment. May be stored or accessed through shared or network-accessible environments.
Who can see data Visibility unchanged unless the agency takes explicit action.
Visibility may expand based on
participation, con/f_iguration,
or system features.
How data is shared Explicit, relationship-based sharing de/f_ined by the agency.
May be enabled through participation or
system features.
Federal access No back door or centralized pool for
federal access. Any federal access requires
a valid legal process directed to the
agency or an agency-approved sharing
relationship, and the agency must approve
each request before data is shared.
Network-based architectures may create
centralized data pools where legal process
can be directed to the vendor rather than
solely to the originating agency. Federal
access pathways have been a documented
focus of public scrutiny in this category.
Who can access Limited to direct, authorized relationships. May include indirect pathways such as partner agencies or shared query layers.
Retention System-enforced based on agency policy. Policy-de /f_ined with variable enforcement; exported data may persist outside controls.
Disclosure control Agency retains full control. May involve multiple entities.
Access tracking Agency can directly review and explain
all access.
Visibility into access may depend on
system structure.
If something goes wrong Issues typically contained to a single agency environment.
Impact scope may extend beyond
one agency.
Independent validation
SOC 2 T ype II, ISO 27001, ISO 27701,
FedRAMP High, CJIS, see trust.axon.com.
Varies by vendor.
The most important distinction is not the camera, it is how the system is structured after data is captured. Architecture determines exposure boundaries; con/f_iguration determines governance posture. axon.com
Agencies have used Fleet for years to deploy mobile ALPR responsibly, and that same foundation carries forward across fixed and mobile ALPR, sharing remains explicit, revocable, and fully auditable, whether the camera is in a patrol vehicle, on a roadside pole, or integrated into streetlight infrastructure. Adding fixed ALPR to an existing Fleet 3 deployment does not introduce a separate governance model: ALPR data flow into the same agency-con- trolled environment under the same retention, access, sharing, and audit controls.
Answers to the questions headlines are raising
Some of the most-asked questions in council chambers today come from headlines about other vendors in this category. Here is how Axon Vehicle Intelligence is structured to answer those questions directly.
Does Axon maintain a national pool of ALPR data?
No. ALPR data stays within the agency’s environment unless the agency chooses to share it. There is no auto- matic cross-agency access, and the system does not connect to a national database. When an agency does choose to share, that access is limited, visible, and can be changed or revoked at any time. Nothing is shared by default, and agencies can only share data they own.
Can federal agencies automatically access our ALPR data? No. The platform does not provide automatic or built-in access to any federal agency. There are no built-in path- ways that route data outside the agency’s controlled environment. Any request from a federal entity, like any other external request, would be directed to the agency itself, and the agency would determine how to respond based on its own policies and applicable law. Federal agencies do not receive automatic or standing access.
Can Axon disclose our agency’s data without our permission? No. The agency owns and controls its ALPR data. Axon does not have routine access to agency ALPR data and does not independently disclose it to any outside party. Subpoenas, warrants, and FOIA requests are routed to the agency as the data owner, and the agency determines how to respond based on its own policies and appli- cable law. All activity is logged so councils and oversight bodies can confirm lawful procedures were followed.
Is governance enforced by design or just by policy?
By design. Agency ownership, explicit sharing, enforceable retention, and immutable audit logs are built into the platform from the ground up, not added on top after the fact.
Can we use our own hotlists?
Axon supports both NCIC and agency-owned hotlists in a single platform. Axon pulls the NCIC hotlist on a daily cycle. Agencies can upload and manage their own hotlists directly in Evidence.com, with updates propagating to devices in minutes, giving agencies real-time control without depending on external update cycles. All hotlist data is encrypted in transit.
axon.com
What this means in a council conversation
When an agency walks into a hearing on ALPR, the questions that decide the room are predictable: Where does our data live? Who can see it? Can it be shared without our permission? How long is it kept? Can a federal entity access it? Who is accountable when something goes wrong? Axon Vehicle Intelligence is structured so each of those questions has a clear, speci/f_ic, system-enforced answer, not a policy promise layered over an architecture that allows otherwise.
Resources
Vehicle Intelligence overview: axon.com/products/vehicle-intelligence.
Trust, security certi/f_ications, and supporting documentation: trust.axon.com.
Axon Customer Experience Improvement Program: axon.com/aceip.
Axon cloud Services Policy: axon.com/legal/cloud-services-privacy-policy.
Responsible Innovation framework: axon.com/responsibility/responsible-innovation. , AXON, Axon, Axon Vehicle Intelligence, Fleet 3, Axon Outpost, Axon Lightpost, Axon Evidence and Axon Fusus are trademarks of Axon Enterprise, Inc., some of which are registered in the US and other countries. For more information visit www.axon.com/legal. All rights reserved. © 2026 Axon Enterprise, Inc.
1 axon.com
© 2026 Axon Enterprise, Inc. All rights reserved. No part of this document may be reproduced or redistributed without the prior written consent of Axon.
Council and
Community Q&A
This Q&A answers common questions about automated license plate recognition (ALPR) programs and the Axon Vehicle Intelligence capabilities that support them. It explains system capabilities, governance controls and accountability in clear, practical terms.
How is this different from another ALPR system?
The difference is in how the data is governed after capture. Axon Vehicle Intelligence is built around agency- controlled data: sharing is explicit and invite-only, no data is copied during sharing, recipient agencies cannot re-share data they receive, and all access and sharing activity is logged and reviewable by the owning agency.
Each agency’s data stays under its own control throughout the program’s operation.
What It Is & What It Captures
System Overview
What problem does this technology address?
Vehicle-related crime is a factor in many serious incidents, including stolen vehicles, hit-and-runs, missing persons cases and investigations that cross jurisdictions. In those situations, identifying a vehicle quickly can reduce the time it takes to locate a vehicle of interest and move an investigation forward. The system helps agencies confirm where a vehicle was seen and respond with better information, within defined limits on how data is collected, used and governed.
What data does the system collect?
The system captures a license plate image, a vehicle context image, basic vehicle attributes visible in the image such as color, make and vehicle type, and the time and location of the detection. The context image provides vehicle context for review. Because it is an image from the scene, it may incidentally include surroundings, signage or people in view. It is not analyzed for facial recognition or behavioral profiling. The system does not perform live registered-owner lookups or build a profile of a registered owner. 2 axon.com
© 2026 Axon Enterprise, Inc. All rights reserved. No part of this document may be reproduced or redistributed without the prior written consent of Axon.
Is this a form of surveillance?
ALPR cameras record vehicle detections at specific camera locations. The system does not use facial recognition, perform live registered-owner lookups or maintain continuous monitoring of individuals. The agency defines who can access the data, how long it is retained and what uses are authorized. Every search is tied to a named user and logged for review.
How does the agency decide where to deploy cameras?
Camera placement is an agency decision governed by the agency’s operational needs, its policies and applicable law. Agencies should be prepared to explain the reasoning behind their deployment plan if asked in a public setting.
Tracking & Movement
Does this system track people?
No. The system captures vehicle detection information, not driver identity. License plate images and vehicle context are recorded at specific camera locations. It does not use facial recognition, perform live registered- owner lookups or maintain a live location feed on any person.
WHAT IT IS & WHAT IT CAPTURES – CONTINUED
Could this be used to track where people go over time?
The system does not monitor people or maintain a live location feed on anyone. When investigating a specific vehicle, an authorized user can review where and when that plate was previously captured, within the agency’s retention period. That search is tied to a named user and logged with the action, time and, where configured, stated reason. It is an investigative search of a known vehicle, bounded by retention and oversight, not continuous monitoring of the public.
3 axon.com
© 2026 Axon Enterprise, Inc. All rights reserved. No part of this document may be reproduced or redistributed without the prior written consent of Axon.
Ownership, Sharing & Hotlists
Who owns and controls the data?
The agency owns and controls its ALPR data. Axon does not pool it, resell it, or disclose it except where legally required. Ownership does not change when data is preserved in Axon Evidence, and it does not change when an agency enables sharing. The agency decides retention, access and sharing. The system applies the configured controls. The agency remains responsible for policy, training and oversight.
Is this connected to a national database?
No. Data stays within the agency’s environment unless the agency chooses to share it. There is no automatic cross-agency access, and the system does not place agency ALPR data into a national or pooled database.
Visibility does not expand unless the agency takes deliberate action.
Can other agencies access the data?
Sharing is off by default and requires the owning agency’s deliberate approval. Another agency can access data only through a specific sharing relationship approved by the owning agency. That access is invite-only, visible and revocable. Sharing does not copy agency ALPR data into a shared repository, transfer ownership or connect agency ALPR data to a national pool.
Can an agency that receives shared data re-share it with other agencies? No. Re-sharing is architecturally impossible, not just prohibited by policy. Sharing is federated: no data is copied when a sharing relationship is established. Because no copy exists, a recipient agency never acquires ownership of shared data and cannot share it further. Agencies can only share ALPR data they own.
Can the agency audit how shared data is accessed?
Yes. When sharing is enabled, access to shared ALPR data is logged and reviewable by the owning agency. The audit record includes recipient activity against shared data and changes to sharing relationships over time, so the agency can review who had access during a specific period.
Can the agency control what ALPR searches are permitted? Yes. The agency configures which offense categories are authorized for ALPR searches. That configuration applies system-wide, covering the agency’s own users and any agencies the data is shared with, so a single standard governs how ALPR can be used across the program. When performing an ALPR search, users must enter an offense category. If that category is not on the agency’s authorized list, the search does not return ALPR data.
4 axon.com
© 2026 Axon Enterprise, Inc. All rights reserved. No part of this document may be reproduced or redistributed without the prior written consent of Axon.
Can an agency use hotlists?
Yes. The agency controls which hotlists the system uses, including agency-owned lists, the National Crime Information Center (NCIC) and other official vehicle-status lists the agency is authorized to use. Any vehicle- status or owner-related details associated with a match come from the agency-authorized hotlist entry, not from a live registered-owner lookup.
Can the system look up who owns a vehicle?
No, not through a live registered-owner lookup. When a plate is read, the system compares it against agency- approved hotlists, which may include official vehicle-status lists the agency is legally authorized to use where configured. Any vehicle-status or owner-related details associated with a match come from the agency- authorized hotlist entry, not from a live registered-owner lookup.
OWNERSHIP , SHARING & HOTLISTS – CONTINUED
Federal Access & Lawful Requests
Can federal agencies access the data?
There is no automatic, standing or built-in federal access to agency ALPR data through Axon. Because the agency owns and controls the data, a lawful request goes to the agency and its counsel to handle. If Axon receives such a request, Axon directs it to the agency as the data owner and discloses data only where legally required to do so.
What stops this from being used for immigration enforcement? This is a local policy decision that the agency governs through its own policy and applicable law. The system provides no automatic, standing or built-in access to any federal agency, including immigration enforcement. If Axon receives a request for agency ALPR data, Axon directs it to the agency as the data owner and provides data only where legally required to do so. If a request goes directly to the agency, the agency decides how to respond under its own policy and applicable law.
Are ALPR records subject to public records requests?
Public records obligations depend on state and local law. The agency is responsible for reviewing and responding to public records requests under its policies and applicable law. ALPR reads, hits, audit records or related materials may require legal review and redaction before any external disclosure. 5 axon.com
© 2026 Axon Enterprise, Inc. All rights reserved. No part of this document may be reproduced or redistributed without the prior written consent of Axon.
Retention, Oversight & Misuse
How long is data kept?
ALPR detection data is retained according to the agency’s configured retention policy and removed when the applicable retention period expires. Detections preserved as evidence follow the agency’s evidence retention rules. The agency sets retention periods according to its policy and applicable law, and the system enforces configured retention settings.
Is governance enforced by design or just by policy?
Policy sets the agency’s rules. System design and configuration controls help enforce those rules, and audit records help the agency review use against them. Agency ownership, explicit sharing, configured retention and logged activity are reflected in how the system works and in the records the agency can review.
What prevents misuse of the system?
Access is limited to authorized users, and every ALPR search and relevant system action is logged with user, action, time and, where configured, stated reason. The agency can assign an audit owner, review activity on a defined cadence and enforce policy through investigation, access restrictions and disciplinary action when needed.
What happens if a hotlist match turns out to be incorrect? A hotlist match generates an alert, not a stop. Officers review every alert and make all enforcement decisions based on their own assessment and applicable law. The system’s role ends at detection. What happens next is governed by the agency’s policies, officer training and applicable legal standards. The agency remains responsible for establishing how officers respond to alerts and how those decisions are reviewed over time.
Can an agency show the community how the system is governed? Yes. Axon offers a public transparency portal an agency can use to disclose its data retention policies and available aggregate ALPR program information. The agency decides whether to publish it and controls which available elements appear. It stays off until the agency turns it on, and the agency can deactivate it at any time. It publishes aggregate information only, no plate numbers, images, individual records or camera locations. When an agency has sharing enabled, the portal can also disclose the partner agencies with whom data is shared. 6 axon.com
© 2026 Axon Enterprise, Inc. All rights reserved. No part of this document may be reproduced or redistributed without the prior written consent of Axon.
How can the agency communicate program outcomes to the public over time? The agency decides what to report, how often and through what channels. That may include aggregate metrics or approved examples such as recovered vehicles, investigative leads, missing person responses or AMBER and Silver Alert support, where available and appropriate. The Axon transparency portal gives agencies a tool to publish aggregate program information publicly. Agencies can also include outcome summaries in council presentations, annual reports or community updates. Agencies should not publish raw ALPR reads, plate numbers, images, exact camera locations, active investigation details, user-level audit logs or personal information.
Does the system use AI to predict crime or flag people? No. AI reads plate characters and basic vehicle attributes from images. It is not used to predict behavior, assign risk scores or identify individuals.
Is agency data used to train AI?
Axon’s agreements with AI providers prohibit them from using agency data to train their models. Axon trains its own AI primarily on self-collected and synthetic data. An agency’s ALPR data can also contribute to improving Axon’s products, including AI, through the Axon Customer Experience Improvement Program (ACEIP).
Participation is optional, and the agency can decline or withdraw at any time. Every approved ACEIP use case is published on Axon’s ACEIP transparency portal, with the data used and the safeguards applied listed for each.
What stops this from expanding into something more invasive over time? New capabilities do not become part of the agency’s program unless the agency approves or configures them under its policy and contract.
AI & Scope
RETENTION, OVERSIGHT & MISUSE – CONTINUED
7 axon.com
© 2026 Axon Enterprise, Inc. All rights reserved. No part of this document may be reproduced or redistributed without the prior written consent of Axon.
Does Axon access agency data?
Axon has no standing access to agency ALPR data. Access occurs only when an agency initiates a specific support request. When that happens, access is temporary, limited to the stated purpose, logged and auditable by the agency.
Vendor Access,
Verification & Accuracy
Is the system independently verified?
Yes. Axon publishes current security and compliance documentation through trust.axon.com. Agencies should use that documentation to confirm which products, services and controls are in scope for each audit or certification. For governance detail, see the Axon Vehicle Intelligence Governance Guide.
What happens if the system gets it wrong?
Accuracy can vary with conditions such as lighting, camera angle and plate visibility. That is why a person reviews every alert before any action is taken. The agency has verification procedures to confirm information before an operational decision is made.
8 axon.com
© 2026 Axon Enterprise, Inc. All rights reserved. No part of this document may be reproduced or redistributed without the prior written consent of Axon.
Do these cameras livestream and record, and how is that governed? Livestreaming is permission-based and configurable. It is active only when an authorized user pulls up a feed for real-time viewing during an active situation. An agency controls whether it is enabled.
Video is handled under its own access, storage and retention controls, which are separate from how ALPR detection data is governed. Where an agency enables and configures recording, video is retained under the agency’s video retention settings, not its ALPR retention settings. Video access is logged and auditable by the agency.
Core boundaries are built into how the system works. The system does not place agency ALPR data into a national pool, does not share data automatically, does not use facial recognition, does not perform live registered-owner lookups and does not automate enforcement. Within those boundaries, each agency configures retention, access, sharing, transparency and livestreaming or recording settings under its policy and applicable law.
For governance detail, see the Axon Vehicle Intelligence Governance Guide. For current security and certification documentation, see trust.axon.com.
Cameras, Livestreaming
& Recording
AXON VEHICLE INTELLIGENCE
axon.com/products/vehicle-i ntelligence • trust.axon.com Safer Streets, Data You Control
How intelligent technology is helping communities without asking them to give up control of their own data A car is reported stolen at 7:40 on a Tuesday morning. By 8:15, it's found three miles away, parked outside an apartment complex, before the owner has even finished filling out the police report. A child goes missing from a park, and within the hour, a patrol officer gets an alert that the suspect vehicle just passed a nearby intersection. A hit-and- run leaves a family without answers, until a single camera on a streetlight two blocks away turns out to hold the one piece of information that closes the case.
This is what modern, AI-powered license plate recognition looks like in practice — not a surveillance dragnet, but a quiet, fast way of connecting a dot that used to take days, or never got connected at all. For the communities using it responsibly, it's become one of the more effective tools for solving the crimes that actually keep people up at night:
stolen vehicles, missing persons, hit-and-runs, and the kind of organized theft rings that move fast across city lines.
But a tool this capable also deserves real scrutiny — and it should have to earn a community's trust, not just ask for it. That's where the conversation usually turns, and where it should turn. Who owns this data? Who can see it? Can it end up somewhere the community never agreed to? How long does it stick around? And if something ever goes wrong, is there an honest paper trail, or just a promise? Your Community's Data Stays Your Community's Data
With Axon Vehicle Intelligence, the agency owns its license plate data. Axon doesn't pool it, doesn't resell it, and doesn't use it for anything beyond what the agency itself directs. There's no hidden national database quietly aggregating every community's plate reads into one place. If your community never chooses to share its data, it simply doesn't leave your community.
Sharing Only Happens When Your Community Says So
Nothing is shared by default. If an agency wants to collaborate with a neighboring department — which can genuinely help solve cross-jurisdiction crime — that relationship has to be explicitly invited, it's fully visible to the agency the whole time, and it can be revoked instantly if the community's priorities or leadership change. No open network. No standing access. No exceptions quietly baked into the fine print.
No Back Door for Federal Access
This is often the first question raised in a council chamber, and it deserves a direct answer: there is no automatic or standing federal access to a community's license plate data, and no centralized pool a federal agency can simply query. Any request — federal, state, or otherwise — has to go through the agency itself, following that agency's own policies and the law. Your community's elected leadership and police department stay the ones answering that question, not a vendor answering it for them behind closed doors.
Data Doesn't Sit Around Forever
Retention is set by the agency, not by Axon, and once that window closes, non-evidentiary data is deleted automatically — no one has to remember to do it, and no one can quietly decide to keep it longer. A community that wants a short retention window gets a short retention window, enforced by the system itself, not by a policy document that only works if everyone remembers to follow it.
Every Use Leaves a Record That Holds Up
Every time the system is accessed — who looked, what they did, when, and why — it's captured in an audit log that can't be edited after the fact. That's what makes it possible to answer tough questions honestly in a council meeting, in a courtroom, or in front of an oversight board: not a promise that things were done right, but a record that shows it.
AXON VEHICLE INTELLIGENCE
axon.com/products/vehicle-i ntelligence • trust.axon.com Independently Verified Security
None of this is just Axon's word to take. The security this is built on — encryption, access controls, breach protections — has been independently verified against some of the most rigorous standards that exist: SOC 2 Type II, ISO 27001, ISO 27701, FedRAMP High, and CJIS. Those aren't marketing terms; they're independent audits that have to be earned and re-earned, not claimed once and forgotten.
Safety and Accountability, Together
The honest version of this conversation isn't "trust us." It's this: a community can have a genuinely powerful tool for solving real crimes — recovering stolen cars, finding missing kids, closing hit-and-runs — without handing over control of its own data to do it. The technology is built so the hard questions have real, specific, verifiable answers, not vague reassurances layered on top of a system that could just as easily work the other way.
That's the balance this is designed around: safer streets, and a community that never has to wonder who's really in control of the tool making them safer.
▲ AXON axo n.com
1 © 2026 Axon Enterprise, Inc. All rights reserved. No part of this document may be reproduced or redistributed without the prior written consent of Axon. ▲ Real-Time Translation —
Axon Body 4
Frequently Asked Questions for City Council
This one-pager anticipates the questions Council members are most likely to raise about the Real-Time Translation feature available on Axon Body 4 cameras, covering how it works, its limitations, evidentiary use, data security, and oversight.
Feature Overview
What exactly does this feature do?
It lets an officer hold a two-way voice conversation with someone who speaks a different language, translated in real time through the body-worn camera. No app, no phone, no separate device — it's built into the Axon Body 4.
How is it activated — is it always listening?
No. It only activates when an officer manually double-presses a programmable button, and only captures audio while a second button is held down (push-to-talk). There is no passive or continuous listening.
How many languages, and how good is the translation?
50+ languages with strong reliability for understanding “main intent” (Spanish, Mandarin, Vietnamese, Tagalog, Arabic, Russian, and others are all covered). It is not positioned as certified-interpreter-quality — it is built for quick, everyday encounters, not high-stakes or evidentiary situations.
Appropriate Use & Human Interpreters
When is it appropriate to use, and when isn't it?
Designed for routine, lower-stakes interactions — traffic stops, minor incident reports, public event assistance.
For witness statements, high-stakes incidents, or anything requiring certified accuracy, officers are still directed to use human interpreters (certified bilingual officers, LanguageLine, etc.).
Does this replace bilingual officers or human interpreters? No. Certified human translators remain necessary for complex or high-stakes situations, and bilingual officers continue to be relied on for those cases.
Could this raise union or staffing concerns for bilingual officers? The tool is designed to support officers who don't speak a second language and reduce staffing strain — it is not meant to replace bilingual officers, who are still needed for complex, high-stakes, and evidentiary interactions.
Recording & Evidentiary Use
Is every interaction recorded?
ATTACHMENT D
▲ AXON axo n.com
2 © 2026 Axon Enterprise, Inc. All rights reserved. No part of this document may be reproduced or redistributed without the prior written consent of Axon. ▲ Yes. Activating translation also starts audio/video recording, uploaded to Evidence.com like all other body- camera footage — the same retention and chain-of-custody rules the department already uses.
Can this translated audio be used as evidence in court? Not reliably on its own — AI-generated translations may not meet formal evidentiary admissibility standards in most jurisdictions. The underlying recording, verified separately by a human translator, is what would support case documentation.
Oversight, Accuracy & Transparency
What oversight and accountability exists for how it's used? Every use is logged in the device's audit trail on Evidence.com, and supervisors can review who used translation, when, and for how long, per the agency's own access permissions.
What happens if the tool mis-identifies the language or mistranslates? The officer can reset and manually specify the correct language. If detection still fails or the tool clearly isn't working, the guidance is to fall back to a human translator.
Are community members told they're being translated or recorded? Officers are trained to state plainly that they are using the camera to translate the conversation — a suggested standard preamble is provided in training — though exact wording is left to officer judgment based on the situation.
Data, Cost & Certification
What data is retained, and is it secure?
No separate transcripts or audio are stored beyond what's already captured in normal body-camera evidence retention; usage metadata (device ID, timestamps) is retained for one year in Axon's secure logging systems.
No data is shared with third-party AI model providers — everything stays within Axon's secure cloud.
Is there a cost impact?
No separate data usage charge — it's included in the Camera Connectivity Pack, which is required to use the feature (i.e., the agency needs Axon Respond, Respond+, or the Device Connectivity Pack already in place).
Is it certified for government or public-sector use?
Yes — certified at the FedRAMP Moderate level.
What if a camera is lost or stolen?
It can be immediately marked lost in Evidence.com, which disables the device's access to the feature.
Source: Axon Real-Time Translation product documentation and Axon Assistant PRFAQ.