---
title: "Axon Redaction Assistant (Axon Enterprise, Inc.)"
url: "https://ailawframework.com/software/axon-redaction-assistant"
type: "software_profile"
site: "AI Law Framework"
id: "axon-redaction-assistant"
vendor: "Axon Enterprise, Inc."
category: "Legal-specific"
segment: "eDiscovery and litigation"
confidence: "medium"
last_reviewed: "2026-09-27"
---

# Axon Redaction Assistant (Axon Enterprise, Inc.)

> Add-on inside Axon Redaction Studio that applies detection models to mask heads, licence plates and screens across video frames in bulk and redacts audio by transcript search, for disclosure and public records work.

Canonical page: https://ailawframework.com/software/axon-redaction-assistant  
Last reviewed: 2026-09-27

Site index for agents: https://ailawframework.com/llms.txt

Plan covered: The Redaction Assistant paid add-on inside Axon Redaction Studio in Axon Evidence, as published on Axon's Australian site. Axon Evidence, Redaction Studio and other Axon Cloud Services need separate review.

## Capabilities

- Redaction

## Key facts

| Fact | Value |
| --- | --- |
| Deployment | SaaS |
| Hosting regions | Unknown |
| Australian region | Unknown |
| Assurance | ACN, C5, CALEA, CCCS Protected B, CJIS, Cloud Security Guidance, CSA STAR, CSA Trusted Cloud Provider, Cyber Essentials, Cyber Essentials Plus, DISP, DoD IL4, ENS RD311/2022 HIGH, IRAP, EU-US DPF, FedRAMP High, FIPS 140-3, G-Cloud, GDPR, HIPAA, ISO 9001:2015, ISO/IEC 20000-1:2018, ISO 22301:2019, ISO/IEC 27001:2022, ISO/IEC 27017:2015, ISO/IEC 27018:2019, ISO/IEC 27701:2019, ISO/IEC 42001:2023, ISO 17025:2017, NIS2, SOC 2, Essential 8, TX-RAMP, VPAT |
| Training on customer content | Unknown |
| Retention | Axon Cloud Services Privacy Notice dated 24 August 2026: 'Customer defines Evidence retention periods pursuant to Customer's internal retention policies and procedures ... Therefore, Customer controls the retention and deletion of its Evidence within Axon Cloud Services.' Axon's own retention policies are stated to govern Non-Content Data, disposed of when no longer necessary to deliver and support the products. Two specific periods are published: files submitted via Third-Party Video 'may be retained up to one year to preserve video format compatibility', and Customer Content is retained for 90 days after termination before deletion, with written proof of deletion available on request. No retention period is published for redaction job artefacts such as detection metadata, generated transcripts or intermediate renders. |
| Integrations | Axon Evidence (evidence.com), Axon Redaction Studio |
| Pricing | No price is published. The product page calls the Assistant a 'premium add-on' inside Redaction Studio, and the redaction overview page directs buyers to contact the vendor: 'Contact Axon for pricing programs and plans to fit your agency's needs.' No pricing page, plan comparison or rate card appears on the Australian redaction pages, and the Trust Center index carries no commercial terms. Whether the add-on is charged per agency, per seat, per video or per minute of footage is not published, and the Master Services Purchasing Agreement named in the Cloud Services Privacy Notice was not opened. |
| Australian presence | Unknown. NO AUSTRALIAN CONTRACTING ENTITY, ACN OR ABN WAS FOUND. Axon publishes a regionalised Australian site at www.axon.com/au carrying this product, Australian industry pages and an Australian contact page, and the Australian pages carry an 'Australia' footer block; the trademark line on those pages reads '© 2026 Axon Enterprise, Inc.' The Global Privacy Notice dated 1 February 2025 is given by 'Axon Enterprise, Inc. and its other legal entities' without naming them and states 'Axon has its headquarters in the United States. Information we collect from you will be processed in the United States.' A regionalised website is not a legal entity, so no Australian entity, ACN, ABN or governing law is recorded. AUSTRALIAN DATA RESIDENCY IS NOT ESTABLISHED. The Axon Cloud Services Privacy Notice dated 24 August 2026 states that a customer 'determines where Axon will store Customer Content by designating an economic area listed on the Subprocessor List' and that all Customer Content in Axon Evidence, including backups, replication and disaster recovery sites, 'remains within the selected economic area'. The economic areas are named only on that Subprocessor List document, which was not opened within this profile's evidence budget, so whether an Australian economic area is offered is unresolved and must not be read off the regional URL scheme or the Australian marketing site. The same notice states that tenant configuration data 'may be copied or transferred to the United States' and that service interaction and service operations and security data sit in the selected area and the United States. WHERE MODEL INFERENCE RUNS IS NOT PUBLISHED on any page read. Two Australian-relevant badges appear on the Trust Center Compliance index, IRAP and DISP, with no scope statement, certificate or date read for either. No Australian customer or agency is named on any page read; a third-party statement that Axon Evidence is in service with Australian police agencies was not treated as vendor material and is not recorded. |
| Website | https://www.axon.com/au/products/redaction/assistant |

## What the research found

| Topic | Status | Finding | Open question | Sources |
| --- | --- | --- | --- | --- |
| Product and plan covered | Public claim only | The Assistant is published as a paid add-on inside another product, not as a standalone purchase. The Australian product page, checked 2026-09-27, states 'This premium add-on accessed right within Redaction Studio uses AI models purpose-built for law enforcement to automate the masking of heads, license plates, and screens.' The overview page states that 'The redaction process begins in Axon's Redaction Studio. Part of Axon Evidence, users can open any piece of video evidence to which they have access and instantly leverage Axon's intuitive tools to manually redact both audio and video PII', so Redaction Studio is the manual layer and the Assistant is the paid automated layer above it. | Is the Redaction Assistant licensed per agency, per seat or per video, does it require a Redaction Studio entitlement for every user who will use it, and which Axon Evidence plan is a prerequisite? | [Axon Redaction Assistant product page (Australian site)](https://www.axon.com/au/products/redaction/assistant); [Redaction overview (Australian site) — Redaction Studio, the Assistant add-on and the exemption log](https://www.axon.com/au/products/redaction) |
| Deployment model | Public claim only | Cloud service. The Assistant runs inside Axon Evidence, which the Axon Cloud Services Privacy Notice dated 24 August 2026 defines as 'Axon's web services hosted on evidence.com including Axon Evidence, Axon Records, and Axon Dispatch, and other related offerings'. The Trust Center index lists a document titled 'Cloud vs On-Premises' under Additional Information, which was not opened, so whether any on-premises redaction path exists is not established from the pages read. | Is any on-premises or private-cloud redaction path available, and if so does the Redaction Assistant's model processing run in that environment or still call the cloud service? | [Axon Redaction Assistant product page (Australian site)](https://www.axon.com/au/products/redaction/assistant); [Axon Trust Center index — compliance badges, document categories and legal items](https://www.axon.com/trust); [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) |
| Published functions | Public claim only | Four functions are named on the Australian product page, checked 2026-09-27: screen, head and licence plate auto-masking, applying 'AI models purpose-built for law enforcement to efficiently mask screens, heads, and license plates throughout every frame they appear in the video'; multi-video initiation on 'up to 20 pieces of video evidence simultaneously ... so that videos up to 2 hours in duration are processed in 10 minutes or less'; head masking and tracking, where 'All unique heads are identified and followed throughout the video, even as they move in and out of frame; quickly select which to redact via a thumbnail panel'; and audio redaction acceleration via transcript, 'by simply searching for or clicking on any words found inside the transcript to auto-redact them throughout the entire video'. The overview page adds that once redaction is complete 'an agency configured exemption log is automatically generated along with an export of the redacted file'. | Does the Assistant detect anything other than heads, licence plates and screens, what happens to a head it fails to track across a cut, and does it produce the transcript that drives audio redaction or consume one produced elsewhere? | [Axon Redaction Assistant product page (Australian site)](https://www.axon.com/au/products/redaction/assistant); [Redaction overview (Australian site) — Redaction Studio, the Assistant add-on and the exemption log](https://www.axon.com/au/products/redaction) |
| Buyers and uses named by the vendor | Public claim only | The Australian site's 'Who We Serve' navigation lists five buyer groups, checked 2026-09-27: Law Enforcement, Fire & EMS, Corrections, Enterprise and Federal. The redaction overview page frames the purpose as statutory access and disclosure work: 'Respond more quickly to Freedom of Information Act (FOIA) and public records requests, minimize tedious manual work, and better serve your communities with Axon's redaction tools.' The named statute is a United States one; the pages read do not name the Australian freedom of information or right to information regimes. | Which Australian statutory access and disclosure regimes has the exemption log been configured against, and do you supply exemption templates for Australian jurisdictions? | [Axon Redaction Assistant product page (Australian site)](https://www.axon.com/au/products/redaction/assistant); [Redaction overview (Australian site) — Redaction Studio, the Assistant add-on and the exemption log](https://www.axon.com/au/products/redaction) |
| Contracting jurisdiction and Australian entity | Not confirmed | No Australian contracting entity, ACN or ABN was found. The Australian product pages carry the trademark line '© 2026 Axon Enterprise, Inc.' and link Australian industry, contact and legal pages; the Global Privacy Notice dated 1 February 2025 states 'Axon has its headquarters in the United States. Information we collect from you will be processed in the United States', and is given by 'Axon Enterprise, Inc. and its other legal entities' without naming them. The Cloud Services Privacy Notice dated 24 August 2026 states it 'is subject to the terms of the Master Services Purchasing Agreement, or other similar agreement, if any, between Axon and Customer'; that agreement was not opened. A regionalised Australian website does not establish an Australian legal entity or governing law. | Which Axon legal entity would contract with us, what is its ACN or ABN, which law governs the Master Services Purchasing Agreement for an Australian customer, and in which courts are disputes heard? | [Axon Redaction Assistant product page (Australian site)](https://www.axon.com/au/products/redaction/assistant); [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy); [Axon Global Privacy Notice, last updated 1 February 2025](https://www.axon.com/legal/privacy-policy) |
| Content ownership | Public claim only | The Axon Cloud Services Privacy Notice dated 24 August 2026 states 'Axon is a Data Processor of Customer Content and Axon obtains no rights to Customer Content. The Customer is a Data Controller and controls and owns all right, title, and interest in and to Customer Content.' It also states 'Axon will not use Customer Content for any advertising or other commercial purposes' and, of sub-processors, that 'Ownership of rights, titles, and interest in and to Customer Content remain with Customer.' Customer Content is defined to include 'all data, files, and content uploaded into, ingested by, created in, or generated through Customer's use of Axon Cloud Services within Customer's tenant', but expressly 'excludes Non-Content Data, Dedrone Data, Third Party Content, and Third Party Services'. | Is a redacted export, a generated transcript and the masking metadata produced by the Redaction Assistant treated as Customer Content, or does any of it fall into the excluded categories of Third Party Content or Non-Content Data? | [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) |
| Support and what support access exposes | Public claim only | The Axon Cloud Services Privacy Notice dated 24 August 2026 states support may be provided 'through phone, email, online chat or sessions' and that 'Phone conversations, online chat sessions, or online sessions with Axon support professionals may be recorded and/or monitored for efforts such as training, future support, and evidentiary purposes.' It also states that where 'access to or processing of Customer Content is necessary to provide support, the Customer Content will be processed as Support Data and will only be used for resolving support incidents', and that 'Files submitted via Third-Party Video may be retained up to one year to preserve video format compatibility.' Support Data is separately used 'to operate, improve, and personalize Axon Products'. No support hours, response times or Australian support location appear on the pages read. | If we raise a redaction support ticket, does the video become Support Data, who may view it, for how long is it kept, and are those personnel located in the economic area we selected? | [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) |
| Published evidence about output quality | Public claim only | Two published figures, both throughput claims with no method. The redaction overview page states 'By leveraging Axon's full solution, agencies can cut redaction time by up to 70% through improved AI model accuracy, faster processing, bulk initiation, the ability to view all unique heads and select which to redact, and more.' The product page states videos 'up to 2 hours in duration are processed in 10 minutes or less'. Neither figure is an accuracy measurement, and no detection rate, miss rate, false-positive rate, test set or evaluation method is published on the pages read. The Trust Center index lists AI items headed 'Building Secure AI Systems', 'AI Risk Management' and 'Responsible AI Statement', none of which was opened. | What is the measured miss rate for heads, licence plates and screens on body-worn and in-car footage, on what test set was it measured, and will you provide the evaluation method and the Responsible AI Statement? | [Axon Redaction Assistant product page (Australian site)](https://www.axon.com/au/products/redaction/assistant); [Redaction overview (Australian site) — Redaction Studio, the Assistant add-on and the exemption log](https://www.axon.com/au/products/redaction); [Axon Trust Center index — compliance badges, document categories and legal items](https://www.axon.com/trust) |
| What the published material supports | Public claim only | The published material supports automated masking of heads, licence plates and screens in video evidence, bulk initiation across up to 20 videos, transcript-driven audio redaction, and generation of an agency-configured exemption log with the redacted export. Nothing on the pages read addresses documents, images or paper records, and nothing addresses redaction of material held outside Axon Evidence. The transcript that drives audio redaction is consumed rather than produced by the Assistant on the page read, so no transcription function is recorded. | For material not already in Axon Evidence, and for document rather than video evidence, what is the redaction path, and does the Assistant work on video ingested from third-party sources? | [Axon Redaction Assistant product page (Australian site)](https://www.axon.com/au/products/redaction/assistant); [Redaction overview (Australian site) — Redaction Studio, the Assistant add-on and the exemption log](https://www.axon.com/au/products/redaction) |
| Check for vendor content directing how AI describes the product | Not confirmed | The check was made deliberately on 2026-09-27 and nothing of the kind was found on the pages read. A site map of www.axon.com run with a search string including 'llms ai info' returned 60 URLs, none of which is an /llms.txt, /ai-info, /ai or /for-ai path, and the two product pages, the Trust Center index and the two privacy notices carry no block addressed to AI models, assistants, crawlers or 'LLMs' and no 'Instructions for AI Assistants' heading. The site is large and a 60-URL map is not an exhaustive instrument, and a direct fetch of axon.com/llms.txt was not made, so an unlinked file at that path is not settled either way. | Do you publish any file or page addressed to AI models or crawlers, such as an llms.txt or an AI information page, and if so what does it say about the redaction products? | [Axon Redaction Assistant product page (Australian site)](https://www.axon.com/au/products/redaction/assistant); [Redaction overview (Australian site) — Redaction Studio, the Assistant add-on and the exemption log](https://www.axon.com/au/products/redaction); [Axon Trust Center index — compliance badges, document categories and legal items](https://www.axon.com/trust); [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy); [Axon Global Privacy Notice, last updated 1 February 2025](https://www.axon.com/legal/privacy-policy) |
| Authority to process the evidence | Public claim only | The Axon Cloud Services Privacy Notice dated 24 August 2026 allocates the roles: 'Axon is a Data Processor of Customer Content ... The Customer is a Data Controller', 'Axon only processes Customer Content on behalf of the Customer in accordance with the Agreement and the Data Processing Agreement entered into between the parties', and for tenant configuration data 'Axon is a Data Controller and Customer is an independent Data Controller, not a joint Data Controller.' The notice is accepted by conduct: 'By using Axon Cloud Services, Customer acknowledges that Customer has read and understands this Notice.' The Data Processing Agreement it refers to was not opened. | Does our Data Processing Agreement with Axon already authorise the Redaction Assistant's automated processing of evidence, or does enabling the add-on require a separate processing instruction? | [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) |
| Which models do the detection | Public claim only | No model or provider is named. The product page describes 'AI models purpose-built for law enforcement' and the overview page repeats that wording; neither names a model, a version, a provider or a training data source, and neither privacy notice names any model provider. The Cloud Services Privacy Notice defines 'Third Party Content' as including 'any output generated by AI powered tools, which are provided by a third party', which shows the platform contemplates third-party AI output without saying whether the Assistant's models are Axon's own or a third party's. | Which models perform head, licence plate and screen detection, are they built and run by Axon or by a named third party, and would their output be Customer Content or Third Party Content under your privacy notice? | [Axon Redaction Assistant product page (Australian site)](https://www.axon.com/au/products/redaction/assistant); [Redaction overview (Australian site) — Redaction Studio, the Assistant add-on and the exemption log](https://www.axon.com/au/products/redaction); [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) |
| Sub-processors | Public claim only | A list is published and its URL is named in the Cloud Services Privacy Notice dated 24 August 2026: 'Axon maintains an up-to-date list of the names and locations of the required Customer Content Subprocessor(s) used to for standard Axon Cloud Services on the Subprocessor List', published as a document file named august_2026_axon_sub-processor_list-2.docx. The notice states 'Axon only permits Subprocessors to use Customer Content to deliver to the Customer services that Axon offers. Axon prohibits Subprocessors from using Customer Content for any other purpose', that sub-processors are audited before onboarding, that 'Axon will give Customer notice of any new Sub-processor', and that customers with a data processing agreement in place may subscribe to advance notice. It also warns that 'additional Subprocessors may be included depending on additional functionality requested during contracting and implementation'. THE LIST ITSELF WAS NOT OPENED within this profile's evidence budget, so no sub-processor and no economic area is recorded here. | Which sub-processors on the August 2026 list are engaged for the Redaction Assistant specifically, in which countries do they operate, and is any of them an additional sub-processor triggered by enabling the add-on? | [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) |
| Use of customer content to train models | Not confirmed | No statement either way was found about training models on evidence content. The Cloud Services Privacy Notice dated 24 August 2026 states 'Axon processes Customer Content to provide Customer Axon Cloud Services' and 'Axon will not use Customer Content for any advertising or other commercial purposes', and does not mention training, tuning or model improvement in relation to Customer Content. It does state that other categories are used to improve products: Customer Entity and User Data is used to 'improve the quality of Axon Products or provide enhanced functionality and features'; Service Interaction Data is processed 'to improve the quality of Axon Products and provide enhanced functionality and features'; and Support Data is used 'to operate, improve, and personalize Axon Products'. For a product whose function is model detection, the absence of a no-training statement covering Customer Content is the finding. | Is our video, audio or transcript content used to train, fine-tune, evaluate or benchmark the Redaction Assistant's detection models, and will you warrant that in the Data Processing Agreement? | [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) |
| Use of user corrections and interactions | Public claim only | The Cloud Services Privacy Notice dated 24 August 2026 defines 'Customer Entity and User Service Interaction Data' as 'data regarding Customer's interactions with Axon Cloud Services and Axon Client Applications' and states 'Axon processes Customer Entity and User Service Interaction Data to improve the quality of Axon Products and provide enhanced functionality and features.' The Redaction Assistant workflow is built on user choices — selecting which detected heads to redact from a thumbnail panel, and clicking or searching transcript words to redact. The notice does not say whether those redaction choices and corrections are Interaction Data used for product improvement or Customer Content, and no opt-out is published. | When a user deselects a detected head or corrects a missed one, is that recorded as Service Interaction Data used to improve your products, and can that use be switched off for our tenant? | [Axon Redaction Assistant product page (Australian site)](https://www.axon.com/au/products/redaction/assistant); [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) |
| Retention | Public claim only | The Cloud Services Privacy Notice dated 24 August 2026 puts evidence retention in the customer's hands: 'Customer defines Evidence retention periods pursuant to Customer's internal retention policies and procedures. Customer can establish its retention policies within Axon Cloud Services. Therefore, Customer controls the retention and deletion of its Evidence within Axon Cloud Services.' Axon's own retention policies are stated to apply to Non-Content Data, which is disposed of 'when such data is no longer necessary for the delivery and support of Axon products and services'. Two specific periods are published: files submitted via Third-Party Video 'may be retained up to one year', and after termination Customer Content is kept for 90 days. No retention period is published for redaction job artefacts such as masking metadata, generated transcripts or intermediate renders. | Do the intermediate artefacts a redaction job creates — detection metadata, generated transcripts, unredacted working copies — follow the retention policy we set on the source evidence, or are they retained separately? | [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) |
| Deletion | Public claim only | The Cloud Services Privacy Notice dated 24 August 2026 states that on termination 'Axon will not delete any Customer Content during the 90 days following termination', that during that period the only functionality is retrieval and only if all amounts due are paid, that after 90 days Axon 'unless legally prohibited, will delete Customer Content upon termination as part of normal retention and data management instructions from customers', and that 'Upon written request, Axon will provide written proof that all Customer Content has been successfully deleted and removed from Axon Cloud Services.' In-service deletion is described as customer-controlled through the retention policy. No deletion timeframe is published for a single redaction job or its artefacts. | If we delete a piece of evidence that has been through the Redaction Assistant, within what period are the redacted export, the detection metadata and any generated transcript deleted, including from backups? | [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) |
| Vendor personnel access to evidence | Public claim only | The Cloud Services Privacy Notice dated 24 August 2026 states 'Within the Axon Cloud Services supporting infrastructure, access is granted based on the principle of least privilege. All access must be approved by system owners and undergo at least quarterly user access reviews', that 'Axon protects all Customer Content and Non-Content Data with strong logical access control mechanisms to ensure only users with appropriate business needs have access to data. Third-party specialized security firms periodically validate access control mechanisms', and that 'Axon personnel undergo an extensive background check process ... Axon personnel supporting Axon Cloud Services are subject to additional role-specific security clearances or adjudication processes, including Criminal Justice Information Services background screening and national security clearances and vetting.' It does not say whether the customer is notified of, or must approve, access to a specific piece of evidence, or whether such access appears in the customer's audit trail. | Are we notified when Axon personnel access a specific piece of our evidence, does that access appear in the evidence audit trail we can read, and in which countries are those personnel located? | [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) |
| Access control and audit inside the tenant | Public claim only | The Cloud Services Privacy Notice dated 24 August 2026 states 'Additional role-based access control is leveraged within Customer's Axon Cloud Service tenant to define what users can interact with or access Customer Content. Customer solely manages the role-based access control mechanisms within its Axon Cloud Services tenant', and 'Axon logically isolates Customer Content. Customer Content for an authenticated customer will not be displayed to another customer (unless Customers explicitly create a sharing relationship between their tenants or shared data between themselves).' On audit it states 'Tamper-proof audit trails are created automatically by Axon Cloud Services upon ingestion of any Evidence' and that a SHA checksum 'is made viewable by users with access to the Evidence audit trail for the specific piece of Evidence.' The Trust Center index lists 'Role-Based Access Control', 'SSO Support', 'Activity Logging' and 'Password Security' items, none of which was opened. | Does the audit trail record every Redaction Assistant run, including which detections were accepted or rejected and by whom, and can that portion of the trail be exported for a disclosure challenge? | [Axon Trust Center index — compliance badges, document categories and legal items](https://www.axon.com/trust); [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) |
| Encryption | Public claim only | The Cloud Services Privacy Notice dated 24 August 2026 states 'Customer Content and Non-Content Data is encrypted in transit over public networks. Customer Content is encrypted at rest in all Axon Cloud Service regions.' No cipher, protocol version, key management or customer-managed key statement appears in the notice. The Trust Center index lists 'Encryption-in-transit' and 'Encryption-at-rest' items, and a 'FIPS 140-3' compliance badge, none of which was opened, so no algorithm or key custody position is recorded. | Which ciphers and key lengths protect evidence at rest, who holds and rotates the keys, and is a customer-managed or customer-held key option available for an Australian agency? | [Axon Trust Center index — compliance badges, document categories and legal items](https://www.axon.com/trust); [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) |
| Independent assurance | Public claim only | A trust centre is published at trust.axon.com, reached from www.axon.com/trust and hosted on SafeBase, and its Compliance section listed the following badges when checked on 2026-09-27: ACN, C5, CALEA, CCCS Protected B, CJIS, Cloud Security Guidance, CSA STAR, CSA Trusted Cloud Provider, Cyber Essentials, Cyber Essentials Plus, DISP, DoD IL4, ENS RD311/2022 HIGH, IRAP, EU-US DPF, FedRAMP High, FIPS 140-3, G-Cloud, GDPR, HIPAA, ISO 9001:2015, ISO/IEC 20000-1:2018, ISO 22301:2019, ISO/IEC 27001:2022, ISO/IEC 27017:2015, ISO/IEC 27018:2019, ISO/IEC 27701:2019, ISO/IEC 42001:2023, ISO 17025:2017, NIS2, SOC 2, Essential 8, TX-RAMP and VPAT. IMPORTANT LIMITS ON THIS FINDING: the index also carries a 'View more' control, so the list is not complete; the underlying documents sit behind separate item links that were not opened and the document area is filtered 'All / Public / Private', so some are access-controlled; no scope statement, certificate, report date or auditor was read for any badge; and nothing on the index says which badges cover Axon Evidence or the Redaction Assistant's models as opposed to other Axon products. | Which of these certifications cover Axon Evidence in the economic area we would select, what is the scope statement for the IRAP assessment and the ISO/IEC 42001 certificate, and does that scope include the Redaction Assistant's detection models? | [Axon Trust Center index — compliance badges, document categories and legal items](https://www.axon.com/trust) |
| Contract terms | Not confirmed | The agreement itself was not read. The Cloud Services Privacy Notice dated 24 August 2026 names it and subordinates itself to it: 'this Notice is subject to the terms of the Master Services Purchasing Agreement, or other similar agreement, if any, between Axon and Customer', and refers throughout to 'the Data Processing Agreement entered into between the parties'. The Trust Center index lists a 'Master Services Agreement' item and a 'Privacy Policy' item under its Legal section; neither was opened, and the redaction pages publish no terms. No liability, indemnity, warranty or term-length provision is therefore recorded. | Please supply the Master Services Purchasing Agreement and the Data Processing Agreement that would apply to us, including the liability position where an automated redaction fails and unredacted material is released. | [Axon Trust Center index — compliance badges, document categories and legal items](https://www.axon.com/trust); [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) |
| Where evidence is stored and whether it leaves the region | Public claim only | Region selection is published and is the customer's choice, but the list of available regions was not read. The Cloud Services Privacy Notice dated 24 August 2026 states 'Axon offers Axon Cloud Services in numerous geographic regions. Before creating an account, Customer determines where Axon will store Customer Content by designating an economic area listed on the Subprocessor List. Axon ensures that all Customer Content in Axon Evidence remains within the selected economic area, including, without limitation, all backup data, replication sites, and disaster recovery sites', and that the selected area can be read from the tenant URL scheme. Three categories are stated to sit outside that boundary: 'Customer Entity and User Data may be copied or transferred to the United States', and Service Interaction Data and Service Operations and Security Data are 'located in Customer's selected economic area for Customer Content and the United States'. The Global Privacy Notice dated 1 February 2025 states 'Axon has its headquarters in the United States. Information we collect from you will be processed in the United States.' WHETHER AN AUSTRALIAN ECONOMIC AREA IS OFFERED IS NOT ESTABLISHED: the economic areas are listed only on the Subprocessor List document, which was not opened, and it must not be read off the existence of an Australian marketing site or the regional URL scheme. | Is an Australian economic area offered for Axon Evidence, and when the Redaction Assistant runs, does the model inference itself occur inside that economic area or is the video sent to another region? | [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy); [Axon Global Privacy Notice, last updated 1 February 2025](https://www.axon.com/legal/privacy-policy) |
| Breach notification | Public claim only | The Cloud Services Privacy Notice dated 24 August 2026 states, under the heading Data Breach: 'If Axon becomes aware of unlawful or unauthorized access to, disclosure, alteration, or destruction of Non-Content or Customer Data, we will notify affected Customers and relevant authorities as necessary.' No notification period, channel, content requirement or named contact is published, and 'as necessary' is not defined. The notice also states that Axon 'will not disclose Customer Content or Non-Content Data to Government Authorities except as required by any law or regulation' and that 'If permitted, Axon will notify Customer if any disclosure request is received for Customer Content so Customer may challenge or object.' The Trust Center index lists a 'Security Incident Handling and Response Statement', which was not opened. | Within how many hours of becoming aware will you notify our nominated contact of an incident affecting our evidence, what will the notice contain, and is that period in the agreement rather than the privacy notice? | [Axon Trust Center index — compliance badges, document categories and legal items](https://www.axon.com/trust); [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) |
| Notice of change to the service and the documents | Public claim only | Two mechanisms are published, one with notice and one without. For the service, the Cloud Services Privacy Notice dated 24 August 2026 states 'Axon periodically upgrades or changes Axon Cloud Services to provide customers with new features and enhancements in alignment with the Axon Evidence Maintenance Schedule. Axon communicates such upgrades or changes to customers one week prior to release', and customers 'cannot unsubscribe from non-promotional communications, such as maintenance schedules'. For the notice itself, change is unilateral: 'Axon may occasionally update this Notice. When Axon posts changes, Axon will revise the "last updated" date at the top of this page. Customer's continued use of Axon Cloud Services will signify Customer's acknowledgement, and to the extent allowed by law agreement to and acceptance of any such changes.' | Does the one-week maintenance notice cover a change to the detection models behind the Redaction Assistant, and will you notify us separately when a model version changes? | [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) |
| Exit and portability | Public claim only | The Cloud Services Privacy Notice dated 24 August 2026 publishes a 90-day post-termination window: 'Axon will not delete any Customer Content during the 90 days following termination. During this 90-day period, Customer may retrieve Customer Content only if Customer has paid all amounts due (there will be no application functionality of the Axon Cloud Services during this 90-day period other than the ability for Customer to retrieve Customer Content). Customer will not incur any additional fees if Customer downloads Customer Content from Axon Cloud Services during this 90-day period.' On format it states 'Evidence uploaded to Axon Cloud Services is retained in original format' and 'Evidence audit trails and system reports may also be downloaded in various industry-standard, non-proprietary formats.' It also states that requests for additional migration assistance 'will result in additional fees and Axon cannot warrant or guarantee data integrity or readability in the external systems.' | On exit, does the export include redacted versions and the redaction audit trail as well as the original evidence, and in which formats are the exemption logs produced? | [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) |
| Third-party components and where the add-on's output sits | Not confirmed | The Cloud Services Privacy Notice dated 24 August 2026 defines two excluded categories the firm must place the add-on against. 'Third Party Content' means 'applications, materials, data and information, such as location, transcriptions, translations and any output generated by AI powered tools, which are provided by a third party and are made available to Customer through Customer's use of the Solution', and Customer Content expressly 'excludes Non-Content Data, Dedrone Data, Third Party Content, and Third Party Services'. The notice also lists what Axon shares with third parties, being providers who facilitate 'user account management, authentication, analytics, and communication', 'product features, e.g. product development, and error analytics', 'customer service and support', and 'security monitoring and investigation'. Because the transcript that drives audio redaction and the masking output are both machine-generated, whether they are Customer Content or Third Party Content determines which protections apply, and the pages read do not say. | Are the Redaction Assistant's masking output and the transcript it searches Customer Content under your notice, or Third Party Content, and if the latter, which of your Customer Content protections do not apply to them? | [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) |
| Reaching out to the internet | Not confirmed | Nothing published states whether any part of the redaction workflow makes an outbound call to the public internet. The described scope is evidence already in the tenant: users 'open any piece of video evidence to which they have access' inside Redaction Studio, and the Assistant is initiated on 'up to 20 pieces of video evidence' in the tenant. No web search, external lookup or public data enrichment is named on the pages read. | Does the Redaction Assistant or the transcript service make any outbound call beyond Axon Cloud Services while processing evidence, and can such calls be blocked at tenant level? | [Axon Redaction Assistant product page (Australian site)](https://www.axon.com/au/products/redaction/assistant); [Redaction overview (Australian site) — Redaction Studio, the Assistant add-on and the exemption log](https://www.axon.com/au/products/redaction) |
| What the add-on does without a person approving it | Public claim only | The published workflow mixes automatic and selected steps. Automatic: detection and masking are applied 'throughout every frame they appear in the video', 'All unique heads are identified and followed throughout the video', a run can be initiated across 'up to 20 pieces of video evidence simultaneously', transcript words are redacted 'throughout the entire video', and on completion 'an agency configured exemption log is automatically generated along with an export of the redacted file'. Selected by a person: which detected heads to redact, 'via a thumbnail panel', and which transcript words to redact. Nothing published says whether a redacted export or an exemption log can be produced, released or shared without a person confirming the result, or whether the exemption log can be edited. | Can a redacted export and its exemption log be generated and released without a person confirming the masking, is the exemption log editable, and is there an approval step we can make mandatory? | [Axon Redaction Assistant product page (Australian site)](https://www.axon.com/au/products/redaction/assistant); [Redaction overview (Australian site) — Redaction Studio, the Assistant add-on and the exemption log](https://www.axon.com/au/products/redaction) |
| Human review before release | Not confirmed | The design places selection with the user but no published requirement forces review before export. The product page states unique heads are identified and the user 'quickly select[s] which to redact via a thumbnail panel', and the overview page states the manual baseline is Redaction Studio, where users 'manually redact both audio and video PII'. Neither page states that a human must review the automated result before the redacted file is exported or released, and neither publishes what happens to a head or plate the models do not detect. The Trust Center index lists a 'Responsible AI Statement', which was not opened. | Is there any enforced review or sign-off step between an automated redaction run and the export or release of the redacted file, and what is your published guidance on checking for missed detections? | [Axon Redaction Assistant product page (Australian site)](https://www.axon.com/au/products/redaction/assistant); [Redaction overview (Australian site) — Redaction Studio, the Assistant add-on and the exemption log](https://www.axon.com/au/products/redaction); [Axon Trust Center index — compliance badges, document categories and legal items](https://www.axon.com/trust) |

## Notes

WHAT COULD NOT BE VERIFIED. Five vendor pages were read on 2026-09-27 within the evidence budget: the Australian Redaction Assistant page, the Australian Redaction overview page, the Trust Center index reached from www.axon.com/trust, the Axon Cloud Services Privacy Notice dated 24 August 2026 and the Axon Global Privacy Notice dated 1 February 2025. NOT OPENED, and therefore not relied on: the Master Services Purchasing Agreement and the Data Processing Agreement both named in the Cloud Services Privacy Notice; the sub-processor list document whose URL that notice publishes, which is the document that names the available economic areas and would settle whether Australian residency is offered; the Redaction Studio product page; the Axon Evidence Maintenance Schedule; and every item behind the Trust Center index links, including the ISO/IEC 42001, IRAP, DISP, SOC 2 and CJIS entries, the Responsible AI Statement, the Security Incident Handling and Response Statement and the 'Cloud vs On-Premises' document. THE ASSURANCE ARRAY IS A LIST OF BADGE NAMES AS RENDERED ON THE TRUST CENTER INDEX, NOT VERIFIED CERTIFICATES: the index also carries a 'View more' control so the list is not complete, its document area is filtered 'All / Public / Private' so some documents are access-controlled, no scope statement or certificate date was read for any badge, and nothing on the index states which badges cover Axon Evidence or the Redaction Assistant's models rather than other Axon products. TRAINING ON CUSTOMER CONTENT IS RECORDED AS UNKNOWN: the Cloud Services Privacy Notice says nothing either way about training models on Customer Content while stating that three Non-Content Data categories are used to improve Axon products. OWNERSHIP IS RECORDED AS UNKNOWN: the pages read carry a footer link to an investor site that was not opened, and ownership must not be inferred from a footer link or a domain. A CORRECTION TO THE ROSTER ENTRY FOR THIS PRODUCT: the vendor's own words are heads, licence plates and screens, plus audio redaction driven by searching an existing transcript. 'Faces' is not the vendor's term, the head-tracking wording is broader than face detection, and the '70%' figure is a time-reduction claim, not a published accuracy metric. VOCABULARY GAPS, nothing invented: the CAPABILITY list has no value for redaction of video or audio media, so the document-flavoured 'redaction' was used; and the CATEGORY list offers only 'Legal-specific' and 'General-purpose', and this product is purpose-built for law-enforcement evidence disclosure rather than legal practice, so 'Legal-specific' was used as the closer of the two.

## Sources

- [Axon Redaction Assistant product page (Australian site)](https://www.axon.com/au/products/redaction/assistant) (checked 2026-09-27)
- [Redaction overview (Australian site) — Redaction Studio, the Assistant add-on and the exemption log](https://www.axon.com/au/products/redaction) (checked 2026-09-27)
- [Axon Trust Center index — compliance badges, document categories and legal items](https://www.axon.com/trust) (checked 2026-09-27)
- [Axon Cloud Services Privacy Notice, last updated 24 August 2026](https://www.axon.com/axon-cloud-services-privacy-policy) (checked 2026-09-27)
- [Axon Global Privacy Notice, last updated 1 February 2025](https://www.axon.com/legal/privacy-policy) (checked 2026-09-27)

A product profile is research to support questions. It does not approve a product for any firm. Public product information supports questions; it does not approve a product for your firm. Verify the exact plan, settings and signed terms.