Common use of ACEIP Tier 1 Clause in Contracts

ACEIP Tier 1. 2.1. When Axon uses Agency Content for the ACEIP Purposes, Axon will extract from Agency Content and may store separately copies of certain segments or elements of the Agency Content (collectively, “ACEIP Content”). When extracting ACEIP Content, Axon will use commercially reasonable efforts to aggregate, transform or de-identify Agency Content so that the extracted ACEIP Content is no longer reasonably capable of being associated with, or could reasonably be linked directly or indirectly to a particular individual (“Privacy Preserving Technique(s)”). For illustrative purposes, some examples are described in footnote 11. For clarity, ACEIP Content will still be linked indirectly, with an attribution, to the Agency from which it was extracted. This attribution will be stored separately from the data itself, but is necessary for and will be solely used to enable Axon to identify and delete all ACEIP Content upon Agency request. Once de-identified, ACEIP Content may then be further modified, analyzed, and used to create derivative works. At any time, Agency may revoke the consent granted herein to Axon to access and use Agency Content for ACEIP Purposes. Within 30 days of receiving the Agency’s request, Axon will no longer access or use Agency Content for ACEIP Purposes and will delete any and all ACEIP Content. Axon will also delete any derivative works which may reasonably be capable of being associated with, or could reasonably be linked directly or indirectly to Agency. In addition, if Axon uses Agency Content for the ACEIP Purposes, upon request, Axon will make available to Agency a list of the specific type of Agency Content being used to generate ACEIP Content, the purpose of such use, and the retention, privacy preserving extraction technique, and relevant data protection practices applicable to the Agency Content or ACEIP Content (“Use Case”). From time to time, Axon may develop and deploy new Use Cases. At least 30 days prior to authorizing the deployment of any new Use Case, Axon will provide Agency notice (by updating the list of Use Case at xxxxx://xxx.xxxx.xxx/aceip and providing Agency with a mechanism to obtain notice of that update or another commercially reasonable method to Agency designated contact) (“New Use Case”).

ACEIP Tier 1. 2.11.1.1. When Axon uses Agency Content for the ACEIP Purposes, Axon will extract from Agency Content and may store separately copies of certain segments or elements of the Agency Content (collectively, “ACEIP Content”). When extracting ACEIP Content, Axon will use commercially reasonable efforts to aggregate, transform or de-identify Agency Content so that the extracted ACEIP Content is no longer reasonably capable of being associated with, or could reasonably be linked directly or indirectly to a particular individual (“Privacy Preserving Technique(s)”). For illustrative purposes, some examples are described in footnote 11. For clarity, ACEIP Content will still be linked indirectly, with an attribution, to the Agency from which it was extracted. This attribution will be stored separately from the data itself, but is necessary for and will be solely used to enable Axon to identify and delete all ACEIP Content upon Agency request. Once de-identified, ACEIP Content may then be further modified, analyzed, and used to create derivative works. At any time, Agency may revoke the consent granted herein to Axon to access and use Agency Content for ACEIP Purposes. Within 30 days of receiving the Agency’s request, Axon will no longer access or use Agency Content for ACEIP Purposes and will delete any and all ACEIP Content. Axon will also delete any derivative works which may reasonably be capable of being associated with, or could reasonably be linked directly or indirectly to Agency. In addition, if Axon uses Agency Content for the ACEIP Purposes, upon request, Axon will make available to Agency a list of the specific type of Agency Content being used to generate ACEIP Content, the purpose of such use, and the retention, privacy preserving extraction technique, and relevant data protection practices 1 For example; (a) when extracting specific text to improve automated transcription capabilities, text that could be used to directly identify a particular individual would not be extracted, and extracted text would be disassociated from identifying metadata of any speakers, and the extracted text would be split into individual words and aggregated with other data sources (including publicly available data) to remove any reasonable ability to link any specific text directly or indirectly back to a particular individual; (b) when extracting license plate data to improve Automated License Plate Recognition (ALPR) capabilities, individual license plate characters would be extracted and disassociated from each other so a complete plate could not be reconstituted, and all association to other elements of the source video, such as the vehicle, location, time, and the surrounding environment would also be removed; (c) when extracting audio of potential acoustic events (such as glass breaking or gun shots), very short segments (<1 second) of audio that only contains the likely acoustic events would be extracted and all human utterances would be removed. applicable to the Agency Content or ACEIP Content (“Use Case”). From time to time, Axon may develop and deploy new Use Cases. At least 30 days prior to authorizing the deployment of any new Use Case, Axon will provide Agency notice (by updating the list of Use Case at xxxxx://xxx.xxxx.xxx/aceip and providing Agency with a mechanism to obtain notice of that update or another commercially reasonable method to Agency designated contact) (“New Use Case”).

ACEIP Tier 1. 2.1. When Axon uses Agency Content for the ACEIP Purposes, Axon will extract from Agency Content and may store separately copies of certain segments or elements of the Agency Content (collectively, “"ACEIP Content”"). When extracting ACEIP Content, Axon will use commercially reasonable efforts to aggregate, transform or de-de- identify Agency Content so that the extracted ACEIP Content is no longer reasonably capable of being associated with, or could reasonably be linked directly or indirectly to a particular individual (“"Privacy Preserving Technique(s)”"). For illustrative purposes, some examples are described in footnote 11. For clarity, ACEIP Content will still be linked indirectly, with an attribution, to the Agency from which it was extracted. This attribution will be stored separately from the data itself, but is necessary for and will be solely used to enable Axon to identify and delete all ACEIP Content upon Agency request. Once de-identified, ACEIP Content may then be further modified, analyzed, and used to create derivative works. At any time, Agency may revoke the consent granted herein to Axon to access and use Agency Content for ACEIP Purposes. Within 30 days of receiving the Agency’s request, Axon will no longer access or use Agency Content for ACEIP Purposes and will delete any and all ACEIP Content. Axon will also delete any derivative works which may reasonably be capable of being associated with, or could reasonably be linked directly or indirectly to Agency. In addition, if Axon uses Agency Content for the ACEIP Purposes, upon request, Axon will make available to Agency a list of the specific type of Agency Content being used to generate ACEIP Content, the purpose of such use, and the retention, privacy preserving extraction technique, and relevant data protection practices applicable to the Agency Content or ACEIP Content (“"Use Case”"). From time to time, Axon may develop and deploy new Use Cases. At least 30 days prior to authorizing the deployment of any new Use Case, Axon will provide Agency notice (by updating the list of Use Case at xxxxx://xxx.xxxx.xxx/aceip and providing Agency with a mechanism to obtain notice of that update or another commercially reasonable method to Agency designated contact) (“"New Use Case”").

ACEIP Tier 1. 2.1. When Axon uses Agency Customer Content for the ACEIP Purposes, Axon will extract from Agency Customer Content and may store separately copies of certain segments or elements of the Agency Customer Content (collectively, “"ACEIP Content”"). When extracting ACEIP Content, Axon will use commercially reasonable efforts to aggregate, transform or de-identify Agency Customer Content so that the extracted ACEIP Content is no longer reasonably capable of being associated with, or could reasonably be linked directly or indirectly to a particular individual (“"Privacy Preserving Technique(s)”"). For illustrative purposes, some examples are described in footnote 11. For clarity, ACEIP Content will still be linked indirectly, with an attribution, to the Agency Customer from which it was extracted. This attribution will be stored separately from the data itself, but is necessary for and will be solely used to enable Axon to identify and delete all ACEIP Content upon Agency Customer request. Once de-identified, ACEIP Content may then be further modified, analyzed, and used to create derivative works. At any time, Agency Customer may revoke the consent granted herein to Axon to access and use Agency Customer Content for ACEIP Purposes. Within 30 days of receiving the AgencyCustomer’s request, Axon will no longer access or use Agency Customer Content for ACEIP Purposes and will delete any and all ACEIP Content. Axon will also delete any derivative works which may reasonably be capable of being associated with, or could reasonably be linked directly or indirectly to AgencyCustomer. In addition, if Axon uses Agency Customer Content for the ACEIP Purposes, upon request, Axon will make available to Agency Customer a list of the specific type of Agency Customer Content being used to generate ACEIP Content, the purpose of such use, and the retention, privacy preserving extraction technique, and relevant data protection practices applicable to the Agency Customer Content or ACEIP Content (“"Use Case”"). From time to time, Axon may develop and deploy new Use Cases. At least 30 days prior to authorizing the deployment of any new Use Case, Axon will provide Agency Customer notice (by updating the list of Use Case at xxxxx://xxx.xxxx.xxx/aceip and providing Agency Customer with a mechanism to obtain notice of that update or another commercially reasonable method to Agency Customer designated contact) (“"New Use Case”").

ACEIP Tier 1. 2.11.1.1. When Axon uses Agency Content for the ACEIP Purposes, Axon will extract from Agency Content and may store separately copies of certain segments or elements of the Agency Content (collectively, “ACEIP Content”). When extracting ACEIP Content, Axon will use commercially reasonable efforts to aggregate, transform or de-identify Agency Content so that the extracted ACEIP Content is no longer reasonably capable of being associated with, or could reasonably be linked directly or indirectly to a particular individual (“Privacy Preserving Technique(s)”). For illustrative purposes, some examples are described in footnote 11. For clarity, ACEIP Content will still be linked indirectly, with an attribution, to the Agency from which it was extracted. This attribution will be stored separately from the data itself, but is necessary for and will be solely used to enable Axon to identify and delete all ACEIP Content upon Agency request. Once de-identified, ACEIP Content may then be further modified, analyzed, and used to create derivative works. At any time, Agency may revoke the consent granted herein to Axon to access and use Agency Content for ACEIP Purposes. Within 30 days of receiving the Agency’s request, Axon will no longer access or use Agency Content for ACEIP Purposes and will delete any and all ACEIP Content. Axon will also delete any derivative works which may reasonably be capable of being associated with, or could reasonably be linked directly or indirectly to Agency. In addition, if Axon uses Agency Content for the ACEIP Purposes, upon request, Axon will make available to Agency a list of the specific type of Agency Content being used to generate ACEIP Content, the purpose of such use, and the retention, privacy preserving extraction technique, and relevant data protection practices applicable 1 For example; (a) when extracting specific text to improve automated transcription capabilities, text that could be used to directly identify a particular individual would not be extracted, and extracted text would be disassociated from identifying metadata of any speakers, and the Agency Content extracted text would be split into individual words and aggregated with other data sources (including publicly available data) to remove any reasonable ability to link any specific text directly or ACEIP Content indirectly back to a particular individual; (“Use Case”). From time b) when extracting license plate data to improve Automated License Plate Recognition (ALPR) capabilities, individual license plate characters would be extracted and disassociated from each other so a complete plate could not be reconstituted, and all association to other elements of the source video, such as the vehicle, location, time, Axon may develop and deploy new Use Cases. At least 30 days prior to authorizing the deployment surrounding environment would also be removed; (c) when extracting audio of any new Use Casepotential acoustic events (such as glass breaking or gun shots), Axon will provide Agency notice very short segments (by updating <1 second) of audio that only contains the list of Use Case at xxxxx://xxx.xxxx.xxx/aceip likely acoustic events would be extracted and providing Agency with a mechanism to obtain notice of that update or another commercially reasonable method to Agency designated contact) (“New Use Case”)all human utterances would be removed.

ACEIP Tier 1. 2.11.1.1. When Axon uses Agency Content for the ACEIP Purposes, Axon will extract from Agency Content and may store separately copies of certain segments or elements of the Agency Content (collectively, “ACEIP Content”). When extracting ACEIP Content, Axon will use commercially reasonable efforts to aggregate, transform or de-identify Agency Content so that the extracted ACEIP Content is no longer reasonably capable of being associated with, or could reasonably be linked directly or indirectly to a particular individual (“Privacy Preserving Technique(s)”). For illustrative purposes, some examples are described in footnote 11. For clarity, ACEIP Content will still be linked indirectly, with an attribution, to the Agency from which it was extracted. This attribution will be stored separately from the data itself, but is necessary for and will be solely used to enable Axon to identify and delete all ACEIP Content upon Agency request. Once de-identified, ACEIP Content may then be further modified, analyzed, and used to create derivative works. At any time, Agency may revoke the consent granted herein to Axon to access and use Agency Content for ACEIP Purposes. Within 30 days of receiving the Agency’s request, Axon will no longer access or use Agency Content for ACEIP Purposes and will delete any and all ACEIP Content. Axon will also delete any derivative works which may reasonably be capable of being associated with, or could reasonably be linked directly or indirectly to Agency. In addition, if Axon uses Agency Content for the ACEIP Purposes, upon request, Axon will make available to Agency a list of the specific type of Agency Content being used to generate ACEIP Content, the purpose of such use, and the retention, privacy preserving extraction technique, and relevant data protection practices applicable to the Agency Content or ACEIP Content (“Use Case”). From time 1 For example; (a) when extracting specific text to improve automated transcription capabilities, text that could be used to directly identify a particular individual would not be extracted, and extracted text would be disassociated from identifying metadata of any speakers, and the extracted text would be split into individual words and aggregated with other data sources (including publicly available data) to remove any reasonable ability to link any specific text directly or indirectly back to a particular individual; (b) when extracting license plate data to improve Automated License Plate Recognition (ALPR) capabilities, individual license plate characters would be extracted and disassociated from each other so a complete plate could not be reconstituted, and all association to other elements of the source video, such as the vehicle, location, time, and the surrounding environment would also be removed; (c) when extracting audio of potential acoustic events (such as glass breaking or gun shots), very short segments (<1 second) of audio that only contains the likely acoustic events would be extracted and all human utterances would be removed. to time, Axon may develop and deploy new Use Cases. At least 30 days prior to authorizing the deployment of any new Use Case, Axon will provide Agency notice (by updating the list of Use Case at xxxxx://xxx.xxxx.xxx/aceip and providing Agency with a mechanism to obtain notice of that update or another commercially reasonable method to Agency designated contact) (“New Use Case”).

ACEIP Tier 1. 2.1. When Axon uses Agency Content for the ACEIP Purposes, Axon will extract from Agency Content and may store separately copies of certain segments or elements of the Agency Content (collectively, “ACEIP Content”). When extracting ACEIP Content, Axon will use commercially reasonable efforts to aggregate, transform or de-identify Agency Content so that the extracted ACEIP Content is no longer reasonably capable of being associated with, or could reasonably be linked directly or indirectly to a particular individual (“Privacy Preserving Technique(s)”). For illustrative purposes, some examples are described in footnote 11. For clarity, ACEIP Content will still be linked indirectly, with an attribution, to the Agency from which it was extracted. This attribution will be stored separately from the data itself, but is necessary for and will be solely used to enable Axon to identify and delete all ACEIP Content upon Agency request. Once de-identified, ACEIP Content may then be further modified, analyzed, and used to create derivative works. At any time, Agency may revoke the consent granted herein to Axon to access and use Agency Content for ACEIP Purposes. Within 30 days of receiving the Agency’s request, Axon will no longer access or use Agency Content for ACEIP Purposes and will delete any and all ACEIP Content. Axon will also delete any derivative works which may reasonably be capable of being associated with, or could reasonably be linked directly or indirectly to Agency. In addition, if Axon uses Agency Content for the ACEIP Purposes, upon request, Axon will make available to Agency a list of the specific type of Agency Content being used to generate ACEIP Content, the purpose of such use, and the retention, privacy preserving extraction technique, and relevant data protection practices applicable to the Agency Content or ACEIP Content (“Use Case”). From time to time, Axon may develop and deploy new Use Cases. At least 30 days prior to authorizing the deployment of any new Use Case, Axon will provide Agency notice (by updating 1 For example; (a) when extracting specific text to improve automated transcription capabilities, text that could be used to directly identify a particular individual would not be extracted, and extracted text would be disassociated from identifying metadata of any speakers, and the extracted text would be split into individual words and aggregated with other data sources (including publicly available data) to remove any reasonable ability to link any specific text directly or indirectly back to a particular individual; (b) when extracting license plate data to improve Automated License Plate Recognition (ALPR) capabilities, individual license plate characters would be extracted and disassociated from each other so a complete plate could not be reconstituted, and all association to other elements of the source video, such as the vehicle, location, time, and the surrounding environment would also be removed; (c) when extracting audio of potential acoustic events (such as glass breaking or gun shots), very short segments (<1 second) of audio that only contains the likely acoustic events would be extracted and all human utterances would be removed. the list of Use Case at xxxxx://xxx.xxxx.xxx/aceip and providing Agency with a mechanism to obtain notice of that update or another commercially reasonable method to Agency designated contact) (“New Use Case”).

ACEIP Tier 1. 2.11.1.1. When Axon uses Agency Content for the ACEIP Purposes, Axon will extract from Agency Content and may store separately copies of certain segments or elements of the Agency Content (collectively, “ACEIP Content”). When extracting ACEIP Content, Axon will use commercially reasonable efforts to aggregate, transform or de-identify Agency Content so that the extracted ACEIP Content is no longer reasonably capable of being associated with, or could reasonably be linked directly or indirectly to a particular individual (“Privacy Preserving Technique(s)”). For illustrative purposes, some examples are described in footnote 11. For clarity, ACEIP Content will still be linked indirectly, with an attribution, to the Agency from which it was extracted. This attribution will be stored separately from the data itself, but is necessary for and will be solely used to enable Axon to identify and delete all ACEIP Content upon Agency request. Once de-identified, ACEIP Content may then be further modified, analyzed, and used to create derivative works. At any time, Agency may revoke the consent granted herein to Axon to access and use Agency Content for ACEIP Purposes. Within 30 days of receiving the Agency’s request, Axon will no longer access or use Agency Content for ACEIP Purposes and will delete any and all ACEIP Content. Axon will also delete any derivative works which may reasonably be capable of being associated with, or could reasonably be linked directly or indirectly to Agency. In addition, if Axon uses Agency Content for the ACEIP Purposes, upon request, Axon will make available to Agency a list of the specific type of Agency Content being used to generate ACEIP Content, the purpose of such use, and the retention, privacy preserving extraction technique, and relevant 1 For example; (a) when extracting specific text to improve automated transcription capabilities, text that could be used to directly identify a particular individual would not be extracted, and extracted text would be disassociated from identifying metadata of any speakers, and the extracted text would be split into individual words and aggregated with other data sources (including publicly available data) to remove any reasonable ability to link any specific text directly or indirectly back to a particular individual; (b) when extracting license plate data to improve Automated License Plate Recognition (ALPR) capabilities, individual license plate characters would be extracted and disassociated from each other so a complete plate could not be reconstituted, and all association to other elements of the source video, such as the vehicle, location, time, and the surrounding environment would also be removed; (c) when extracting audio of potential acoustic events (such as glass breaking or gun shots), very short segments (<1 second) of audio that only contains the likely acoustic events would be extracted and all human utterances would be removed. data protection practices applicable to the Agency Content or ACEIP Content (“Use Case”). From time to time, Axon may develop and deploy new Use Cases. At least 30 days prior to authorizing the deployment of any new Use Case, Axon will provide Agency notice (by updating the list of Use Case at xxxxx://xxx.xxxx.xxx/aceip and providing Agency with a mechanism to obtain notice of that update or another commercially reasonable method to Agency designated contact) (“New Use Case”).

ACEIP Tier 1. 2.11.1.1. When Axon uses Agency Content for the ACEIP Purposes, Axon will extract from Agency Content and may store separately copies of certain segments or elements of the Agency Content (collectively, “ACEIP Content”). When extracting ACEIP Content, Axon will use commercially reasonable efforts to aggregate, transform or de-identify Agency Content so that the extracted ACEIP Content is no longer reasonably capable of being associated with, or could reasonably be linked directly or indirectly to a particular individual (“Privacy Preserving Technique(s)”). For illustrative purposes, some examples are described in footnote 11. For clarity, ACEIP Content will still be linked indirectly, with an attribution, to the Agency from which it was extracted. This attribution will be stored separately from the data itself, but is necessary for and will be solely used to enable Axon to identify and delete all ACEIP Content upon Agency request. Once de-identified, ACEIP Content may then be further modified, analyzed, and used to create derivative works. At any time, Agency may revoke the consent granted herein to Axon to access and use Agency Content for ACEIP Purposes. Within 30 days of receiving the Agency’s request, Axon will no longer access or use Agency Content for ACEIP Purposes and will delete any and all ACEIP Content. Axon will also delete any derivative derivat ive works which may reasonably be capable of being associated with, or could reasonably be linked directly or indirectly to Agency. In addition, if Axon uses Agency Content for the ACEIP Purposes, upon request, Axon will make available to Agency a list of the specific type of Agency Content being used to generate ACEIP Content, the purpose of such use, and the retention, privacy privac y preserving extraction technique, and relevant data protection practices 1 For example; (a) when extracting specific text to improve automated transcription capabilities, text that could be used to directly identify a particular individual would not be extracted, and extracted text would be disassociated from identifying metadata of any speakers, and the extracted text would be split into individual words and aggregated with other data sources (including publicly available data) to remove any reasonable ability to link any specific text directly or indirectly back to a particular individual; (b) when extracting license plate data to improve Automated License Plate Recognition (ALPR) capabilities, individual license plate characters would be extracted and disassociated f rom each other so a complete plate could not be reconstituted, and all association to other elements of the source video, such as the vehicle, location, time, and the surrounding environment would also be removed; (c) when extracting audio of potential acoustic events (such as glass breaking or gun shots), very short segments (<1 second) of audio that only contains the likely acoustic events would be extracted and all human utterances would be removed. applicable to the Agency Content or ACEIP Content (“Use Case”). From time to time, Axon may develop and deploy new Use Cases. At least 30 days prior to authorizing the deployment of any new Use Case, Axon will provide Agency notice (by updating the list of Use Case at xxxxx://xxx.xxxx.xxx/aceip and providing Agency with a mechanism to obtain notice of that update or another commercially reasonable method to Agency designated contact) (“New Use Case”).

ACEIP Tier 1. 2.11.1.1. When Axon uses Agency Content for the ACEIP Purposes, Axon will extract from Agency Content and may store separately copies of certain segments or elements of the Agency Content (collectively, “ACEIP Content”). When extracting ACEIP Content, Axon will use commercially reasonable efforts to aggregate, transform or de-identify Agency Content so that the extracted ACEIP Content is no longer reasonably capable of being associated with, or could reasonably be linked directly or indirectly to a particular individual (“Privacy Preserving Technique(s)”). For illustrative purposes, some examples are described in footnote 11. For clarity, ACEIP Content will still be linked indirectly, with an attribution, to the Agency from which it was extracted. This attribution will be stored separately from the data itself, but is necessary for and will be solely used to enable Axon to identify and delete all ACEIP Content upon Agency request. Once de-identified, ACEIP Content may then be further modified, analyzed, and used to create derivative works. At any time, Agency may revoke the consent granted herein to Axon to access and use Agency Content for ACEIP Purposes. Within 30 days of receiving the Agency’s request, Axon will no longer access or use Agency Content for ACEIP Purposes and will delete any and all ACEIP Content. Axon will also delete any derivative works which may reasonably be capable of being associated with, or could reasonably be linked directly or indirectly to Agency. In addition, if Axon uses Agency Content for the ACEIP Purposes, upon request, Axon will make available to Agency a list of the specific type of Agency Content being used to generate ACEIP Content, the purpose of such use, and the retention, privacy preserving extraction technique, and relevant data protection practices applicable to the Agency Content or ACEIP Content 1 For example; (a) when extracting specific text to improve automated transcription capabilities, text that could be used to directly identify a particular individual would not be extracted, and extracted text would be disassociated from identifying metadata of any speakers, and the extracted text would be split into individual words and aggregated with other data sources (including publicly available data) to remove any reasonable ability to link any specific text directly or indirectly back to a particular individual; (b) when extracting license plate data to improve Automated License Plate Recognition (ALPR) capabilities, individual license plate characters would be extracted and disassociated from each other so a complete plate could not be reconstituted, and all association to other elements of the source video, such as the vehicle, location, time, and the surrounding environment would also be removed; (c) when extracting audio of potential acoustic events (such as glass breaking or gun shots), very short segments (<1 second) of audio that only contains the likely acoustic events would be extracted and all human utterances would be removed. (“Use Case”). From time to time, Axon may develop and deploy new Use Cases. At least 30 days prior to authorizing the deployment of any new Use Case, Axon will provide Agency notice (by updating the list of Use Case at xxxxx://xxx.xxxx.xxx/aceip and providing Agency with a mechanism to obtain notice of that update or another commercially reasonable method to Agency designated contact) (“New Use Case”).