# HIDTA MOU.pdf # source: alpharetta-pd/2026-08-17-data-sharing/HIDTA MOU.pdf # sha256: 455ad20494ec680f3f683385a0eae2e42d9a089f87c247e2ec1f2c563b24ad8a # pages: 11 # methods: embedded-ocr=11 # produced-by: creationDate=D:20251104164133Z; creator=[withheld]; modDate=D:20260721150815-04'00'; producer=UniDoc v3.12.3 (Commercial License - Business) - http://unidoc.io --- page 1 [embedded-ocr] --- HIGH INTENSITY DRUG TRAFFICKING AREA HIDTA LICENSE PLATE READER INTEGRATION PROJECT MEMORANDUM OF UNDERSTANDING This Memoran ym of Understanding (hereinafter “MOU” or “Agreement”) is made and entered into on this 47" day of Voweer er 2025 by and between the parties defined on the last page of the MOU, known collectively as “Member Agencies” or individually as a “Member Agency.” WHEREAS, the Member Agencies provide Public Safety services within their jurisdictions; and WHEREAS, the Member Agencies have found it to be of mutual benefit to provide for the most efficient utilization of their resources and services in the application to Public Safety efforts within their jurisdictions; and WHEREAS, the Member Agencies are committed to complete cooperation and coordination in providing the highest level of public safety services to the public, guided by the principle that performing cooperatively is in the best interest of the public; and WHEREAS, the Member Agencies desire to facilitate the sharing of information contained within their electronic data systems, including but not limited to: Automated License Plate Readers and Law Enforcement Data Sharing Systems - which may include aggregated information collected from multiple individual or regional sources - into commercially available and custom developed data integration systems; and WHEREAS, the Member Agencies desire to share data owned, aggregated, or collected by the Member Agencies under the conditions set forth in this MOU; The agencies are collectively known as the “Member Agencies”: SEE ATTACHMENT “A” Mission The High Intensity Drug Trafficking Area (HIDTA) is a multi-jurisdictional public safety program that was established to reduce drug trafficking and production in the United States. The HIDTA License Plate Reader Integration Platform (HLPRIP) was formed in support of this mission, under the leadership of the HIDTA Program, its Executive Board, and regional stakeholders, to develop, establish, and maintain an integrated system of information technology that maximizes the sharing of data and communication between Member Agencies in support of Page 1 of 11 HLPRIP MOU updated 09/10/25 ···· transcribed by claude-opus-5 vision pass (not OCR) ···· Cover page of an executed Memorandum of Understanding, clean laser print on a straight, well-exposed scan. Centered heading in small caps: HIGH INTENSITY DRUG TRAFFICKING AREA / HIDTA LICENSE PLATE READER INTEGRATION PROJECT, then MEMORANDUM OF UNDERSTANDING. The opening paragraph reads: 'This Memorandum of Understanding (hereinafter "MOU" or "Agreement") is made and entered into on this ___ day of ______ 2025 by and between the parties defined on the last page of the MOU, known collectively as "Member Agencies" or individually as a "Member Agency."' Two blanks are filled in by hand in blue ballpoint: the day blank carries '4th' (numeral 4 with a raised 'th'), the month blank carries 'November' in cursive. The year '2025' is not handwritten — it is pre-printed in the document's bold serif face. Five WHEREAS recitals follow, covering public safety services within jurisdictions, mutual benefit and efficient utilization of resources, cooperation and coordination, a desire to facilitate sharing of information within electronic data systems 'including but not limited to: Automated License Plate Readers and Law Enforcement Data Sharing Systems - which may include aggregated information collected from multiple individual or regional sources - into commercially available and custom developed data integration systems', and a desire to share data owned, aggregated, or collected by the Member Agencies. Then in bold: 'The agencies are collectively known as the "Member Agencies":' followed by 'SEE ATTACHMENT "A"'. Under an underlined 'Mission' heading, a paragraph describes HIDTA as a multi-jurisdictional public safety program established to reduce drug trafficking and production in the United States, and states that the HIDTA License Plate Reader Integration Platform (HLPRIP) was formed in support of that mission under the leadership of the HIDTA Program, its Executive Board, and regional stakeholders. The paragraph runs off the bottom of the page mid-sentence ('...in support of'). Footer: 'Page 1 of 11' centered and 'HLPRIP MOU updated 09/10/25' at right. No signature, no agency name, no ORI, no dollar figure, no stamp and no redaction appears anywhere on this page. heading_line_1: HIGH INTENSITY DRUG TRAFFICKING AREA heading_line_2: HIDTA LICENSE PLATE READER INTEGRATION PROJECT instrument_title: MEMORANDUM OF UNDERSTANDING execution_day: 4th execution_month: November execution_year: 2025 member_agency_roster: SEE ATTACHMENT "A" platform_acronym: HLPRIP page_number: Page 1 of 11 revision_footer: HLPRIP MOU updated 09/10/25 agency_name: None ori: None signature: None signature_date: None amount_usd: None purchase_order: None invoice_number: None --- page 2 [embedded-ocr] --- law enforcement and public safety, while maintaining the confidentiality of privileged or otherwise protected information shared through the system, and protecting privacy and civil liberties in accordance with applicable law. Member Agencies agree to work together in a variety of ways to facilitate sharing data in an effort to promote and improve the data sharing capabilities of the respective Member Agencies and the HLPRIP. Purpose This agreement outlines the duties and responsibilities of each Member Agency, defines the working relationships and lines of authority for Member Agencies within the HLPRIP, and provides for the addition of other eligible entities in the data-sharing program created by this MOU. Therefore, the Member Agencies hereby agree to the following: 1) Definitions 1.1 The HLPRIP Information Sharing System is a collective group of law and justice agencies sharing data into one or more data aggregation systems, of which are represented on this or other information sharing agreements. 1.2 Criminal Justice Practitioners: personnel from the Member Agencies who have the appropriate clearance and authority to use and access shared data as a function of their employment, also referred to as “Authorized Users.” 1.3 Data: electronic facts, records, analysis, images, or other information provided and shared by a Member Agency. 1.4 Data Set: a specific grouping, categorization, or subset of LPR data included in a Member Agency system. 1.5 Data Record: a unique individual record or document associated with an incident or person, which may include a variety of associated information. 1.6 Host: the entity providing the facilities, labor, and expertise used to maintain, operate, and manage a core component of the HLPRIP Database, such as software which aggregates data from multiple sources or provides unified access to disparate systems. 1.7 Member Agency: a law enforcement or public safety organization whose leadership has signed this agreement and the agency actively participates in information sharing with other Member Agencies. 1.8 Member Agency LPR Administrator: The Member Agency’s designee who is responsible for the management and oversight of the Member Agency’s Authorized Users and Member Agency Data submitted to the HLPRIP server. Page 2 of 11 HLPRIP MOU updated 01/16/25 ···· transcribed by claude-opus-5 vision pass (not OCR) ···· Continuation page, clean laser print, straight scan, no handwriting anywhere. It opens mid-sentence from page 1: 'law enforcement and public safety, while maintaining the confidentiality of privileged or otherwise protected information shared through the system, and protecting privacy and civil liberties in accordance with applicable law.' A paragraph follows on Member Agencies working together to facilitate sharing data and improve the data sharing capabilities of the respective Member Agencies and the HLPRIP. Under an underlined 'Purpose' heading: the agreement outlines the duties and responsibilities of each Member Agency, defines the working relationships and lines of authority within the HLPRIP, and provides for the addition of other eligible entities in the data-sharing program created by this MOU. Then, underlined and bold: 'Therefore, the Member Agencies hereby agree to the following:' and section '1) Definitions', comprising eight numbered definitions. 1.1 defines the HLPRIP Information Sharing System as a collective group of law and justice agencies sharing data into one or more data aggregation systems. 1.2 Criminal Justice Practitioners: personnel from the Member Agencies with appropriate clearance and authority to use and access shared data as a function of their employment, also referred to as 'Authorized Users.' 1.3 Data: electronic facts, records, analysis, images, or other information provided and shared by a Member Agency. 1.4 Data Set: a specific grouping, categorization, or subset of LPR data included in a Member Agency system. 1.5 Data Record: a unique individual record or document associated with an incident or person. 1.6 Host: the entity providing the facilities, labor, and expertise used to maintain, operate, and manage a core component of the HLPRIP Database, such as software which aggregates data from multiple sources or provides unified access to disparate systems. 1.7 Member Agency: a law enforcement or public safety organization whose leadership has signed this agreement and which actively participates in information sharing with other Member Agencies. 1.8 Member Agency LPR Administrator: the Member Agency's designee responsible for management and oversight of the Member Agency's Authorized Users and Member Agency Data submitted to the HLPRIP server. Footer: 'Page 2 of 11' and 'HLPRIP MOU updated 01/16/25'. No signature, no money, no stamp, no redaction. section_heading: 1) Definitions subsection_headings: Purpose; 1) Definitions (1.1 through 1.8) defined_terms: Criminal Justice Practitioners; Data; Data Set; Data Record; Host; Member Agency; Member Agency LPR Administrator authorized_users_term: Authorized Users page_number: Page 2 of 11 revision_footer: HLPRIP MOU updated 01/16/25 agency_name: None signature: None date: None amount_usd: None purchase_order: None invoice_number: None --- page 3 [embedded-ocr] --- 2) Member Agency Rights, Powers and Authority Each Member Agency expressly retains all rights and powers to finance, plan, develop, construct, maintain, repair, manage, operate, and control equipment, facilities, properties, projects, and information that it deems in its sole discretion to be necessary or desirable for its own information system needs, and that are authorized by the laws governing it. This agreement shall not be interpreted, and the HLPRIP Database shall not have any authority, to impair or control any of the Member Agency’s respective rights, powers, or title to such equipment, facilities, properties, information, and projects, nor shall any Member Agency be required to provide additional personnel, equipment, or services to the HLPRIP, which are not already a part of the Member Agency’s current operational costs, nor shall they be required to modify their non-HLPRIP Database systems or services, without their consent. Nothing in this Agreement shall be construed to require a Member Agency: 1) To disclose any information that the Member Agency determines, in its sole discretion, it does not have the ability or authority to disclose; OR 2) To perform any act that the Member Agency determines, in its sole discretion, is contrary to law or public/agency policy. Member Agencies are not required to seek approval from the HLPRIP to purchase, install, or modify their own LPR Database equipment, services, or work performed in conjunction with any legislative mandate/authority granted to or required of Member Agencies in order to carry out their respective responsibilities. Furthermore, the HLPRIP has no power or authority to control, interfere with, or inhibit Member Agencies from conducting their own internal business and/or providing their own resources or services to other entities, which may or may not be members of or served by the HLPRIP Database. Participation in the HLPRIP Database and any associated data interfaces or other customizations shall not prevent the Member Agency from operating systems independent of the HLPRIP Database. Notwithstanding anything to the contrary herein, a Member Agency shall have no obligation to seek approval from the HLPRIP for any modification to that Member Agency’s internal systems or processes that is mandated by the state in which the Member Agency is located, or by any law or regulation governing the affected member Agency. In gathering and sharing information, and in all other respects in performing acts related to this Agreement, the parties will comply with all applicable laws, rules, and regulations. 3) Effective Date and Term of MOU This Agreement's effective date is noted above and/or the date each subsequent Member Agency executes this agreement. This agreement shall remain in effect and shall be reviewed and updated every five years. The agreement can only be terminated as provided herein. Page 3 of 11 HLPRIP MOU updated 01/16/25 ···· transcribed by claude-opus-5 vision pass (not OCR) ···· Clean laser print, straight scan, no handwriting. Section '2) Member Agency Rights, Powers and Authority' (underlined) runs most of the page. Each Member Agency expressly retains all rights and powers to finance, plan, develop, construct, maintain, repair, manage, operate, and control equipment, facilities, properties, projects, and information it deems in its sole discretion necessary or desirable for its own information system needs; the agreement is not to be interpreted, and the HLPRIP Database is to have no authority, to impair or control any of those rights, powers or title; no Member Agency is required to provide additional personnel, equipment or services to the HLPRIP not already part of its current operational costs, nor to modify its non-HLPRIP Database systems or services without consent. A carve-out follows: 'Nothing in this Agreement shall be construed to require a Member Agency: 1) To disclose any information that the Member Agency determines, in its sole discretion, it does not have the ability or authority to disclose; OR 2) To perform any act that the Member Agency determines, in its sole discretion, is contrary to law or public/agency policy.' Member Agencies need no HLPRIP approval to purchase, install or modify their own LPR Database equipment or services. The HLPRIP has no power or authority to control, interfere with, or inhibit Member Agencies conducting their own internal business or providing resources or services to other entities, members or not. Participation does not prevent a Member Agency operating systems independent of the HLPRIP Database. Notwithstanding anything to the contrary, no HLPRIP approval is needed for any modification to a Member Agency's internal systems or processes mandated by its state or by any law or regulation governing it. The parties will comply with all applicable laws, rules and regulations. Section '3) Effective Date and Term of MOU' closes the page: "This Agreement's effective date is noted above and/or the date each subsequent Member Agency executes this agreement. This agreement shall remain in effect and shall be reviewed and updated every five years. The agreement can only be terminated as provided herein." Footer: 'Page 3 of 11' and 'HLPRIP MOU updated 01/16/25'. No signature, no money, no stamp, no redaction. section_headings: 2) Member Agency Rights, Powers and Authority; 3) Effective Date and Term of MOU effective_date_rule: noted above and/or the date each subsequent Member Agency executes this agreement review_cycle: every five years termination_rule: can only be terminated as provided herein page_number: Page 3 of 11 revision_footer: HLPRIP MOU updated 01/16/25 agency_name: None signature: None date: None amount_usd: None purchase_order: None invoice_number: None --- page 4 [embedded-ocr] --- 4) Data Sharing All Member Agencies agree to promote comprehensive, timely, and accurate data sharing with other Member Agencies via the HLPRIP system. HLPRIP data shall only be shared with Member Agencies, and only to Authorized Users of those agencies who possess an approved login and password and a "need to know" and "right to know" the shared data in fulfillment of assigned law enforcement or public safety duties. Any data shared by a Member Agency to the HLPRIP system that the Member Agency later declares should not be shared, shall be withdrawn by all Hosts from all data within 48 hours, including deletion of any replications of the data. Each Member Agency shall determine, within its sole discretion, which Data Records are to be shared with the HLPRIP system and shall maintain the databases or other sources that contain the applicable information. 5) Data Access Data exchange and user access shall be achieved using secure networks, including encrypted virtual private networks (VPN), or other reasonably secure configurations that follow current best practices for information technology and are acceptable to both the Member Agency sharing data and the Host receiving data or providing user access. The information residing in the Data Repositories shall generally be available at all times. Member Agencies agree to inform the HLPRIP in advance, whenever possible, of scheduled down times of specific data feeds. The HLPRIP will alert Member Agencies whenever possible that the HLPRIP system will be down due to upgrades, maintenance, or unforeseen events. 6) Information Ownership, Release and Accuracy 6.1 Ownership and Release Constraints Member Agencies shall retain control of, and remain the official custodian of, all information they contribute to the HLPRIP Database. All requests for information will be referred to the Member Agency that is the owner of the requested data, and that Member Agency will be responsible for responding to the request for information. 6.2 Information Accuracy Member Agencies and Authorized Users acknowledge that data maintained in the HLPRIP Database consists of information that may or may not be accurate. Neither party warrants nor may rely upon the accuracy of such information. Each party understands and agrees to convey that fact to anyone they authorize to access shared information. It shall be the responsibility of the person or entity requesting or using the data to confirm the Page 4 of 11 HLPRIP MOU updated 01/16/25 ···· transcribed by claude-opus-5 vision pass (not OCR) ···· Clean laser print, straight scan, no handwriting. Section '4) Data Sharing': all Member Agencies agree to promote comprehensive, timely and accurate data sharing via the HLPRIP system; HLPRIP data shall only be shared with Member Agencies, and only to Authorized Users of those agencies who possess an approved login and password and a 'need to know' and 'right to know' the shared data in fulfillment of assigned law enforcement or public safety duties. Next paragraph: 'Any data shared by a Member Agency to the HLPRIP system that the Member Agency later declares should not be shared, shall be withdrawn by all Hosts from all data within 48 hours, including deletion of any replications of the data.' Each Member Agency determines in its sole discretion which Data Records are shared and maintains the underlying databases or sources. Section '5) Data Access': exchange and user access shall use secure networks, including encrypted virtual private networks (VPN), or other reasonably secure configurations following current best practices, acceptable to both the sharing Member Agency and the Host; information in the Data Repositories shall generally be available at all times; Member Agencies agree to inform the HLPRIP in advance where possible of scheduled downtime of specific data feeds, and the HLPRIP will alert Member Agencies where possible of system downtime for upgrades, maintenance or unforeseen events. Section '6) Information Ownership, Release and Accuracy' with '6.1 Ownership and Release Constraints' — Member Agencies retain control of, and remain official custodian of, all information they contribute to the HLPRIP Database; all requests for information will be referred to the owning Member Agency, which is responsible for responding — and '6.2 Information Accuracy' — Member Agencies and Authorized Users acknowledge the HLPRIP Database consists of information that may or may not be accurate, neither party warrants nor may rely upon its accuracy, each party agrees to convey that to anyone it authorizes to access shared information, and it is the responsibility of the person or entity requesting or using the data to confirm (sentence runs onto the next page). Footer: 'Page 4 of 11' and 'HLPRIP MOU updated 01/16/25'. No signature, no money, no stamp, no redaction. section_headings: 4) Data Sharing; 5) Data Access; 6) Information Ownership, Release and Accuracy (6.1 Ownership and Release Constraints; 6.2 Information Accuracy) access_conditions: approved login and password; "need to know" and "right to know" data_withdrawal_deadline: 48 hours withdrawal_scope: withdrawn by all Hosts from all data, including deletion of any replications of the data network_requirement: secure networks, including encrypted virtual private networks (VPN) records_custodian_rule: Member Agencies retain control of and remain official custodian of information they contribute; all requests for information referred to the owning Member Agency accuracy_disclaimer: information that may or may not be accurate; neither party warrants nor may rely upon the accuracy page_number: Page 4 of 11 revision_footer: HLPRIP MOU updated 01/16/25 agency_name: None signature: None date: None amount_usd: None purchase_order: None invoice_number: None --- page 5 [embedded-ocr] --- accuracy of the information with the Member Agency that authored or originated the information before taking any enforcement-related action. 6.3 Audit Each transaction is to be logged, and an audit trail created. The Audit log will be maintained for a period of no less than twelve months to record user access to shared data, including the date and time when the data was accessed. Member Agencies shall conduct an internal audit on a periodic basis to ensure that queries are made for legitimate law enforcement purposes. Member Agencies will receive bi-annual audit logs containing all HLPRIP usage by the Agency’s Authorized Users. 6.4 Criminal Discovery Prior to releasing any data in furtherance of its statutory and constitutional obligations relating to the criminal discovery process, a member prosecuting agency shall seek express permission from the originating agency. In any instance where an originating agency declines to grant such disclosure permission, the originating agency and the prosecuting agency shall confer to reach agreement on possible limitations on disclosure (including the seeking of judicial protective orders) in an attempt to protect the originating agency’s specific concerns while allowing the prosecuting agency to meet its statutory and constitutional criminal discovery obligations. 7) User Access Each Member Agency is responsible for approving user accounts within that agency. Each agency agrees that all Authorized Users shall be current employees in good standing and be authorized to review criminal data for legitimate purposes. If for any reason an Authorized User is no longer eligible for such access, or ends his/her employment with the agency, the agency will make necessary contacts to ensure access is removed accordingly and in a timely manner. Each Authorized User agrees that the HLPRIP Database systems and the information contained therein are to be used solely for purposes consistent with the law. Authorized Users shall not use or share the information for any unethical, illegal, or criminal purpose. Authorized Users may not access any of the HLPRIP Database by using a name or password that was assigned to another user. Passwords may not be shared with other persons, including other Authorized Users, for access to the system. The various Member Agencies agree to use information shared in the HLPRIP Database information systems as a pointer system and not as the source of probable cause for law enforcement actions. Page 5 of 11 HLPRIP MOU updated 01/16/25 ···· transcribed by claude-opus-5 vision pass (not OCR) ···· A clean body page of a multi-agency license-plate-reader MOU, unsigned, no handwriting, no stamps, no exhibits. It opens mid-sentence carrying over from page 4: "accuracy of the information with the Member Agency that authored or originated the information before taking any enforcement-related action." Then a bold heading 6.3 Audit, whose paragraph is the substantive content of the page: each transaction is to be logged and an audit trail created; the audit log is kept "for a period of no less than twelve months" recording user access to shared data including date and time of access; Member Agencies shall audit themselves periodically to ensure queries are made for legitimate law enforcement purposes; and Member Agencies "will receive bi-annual audit logs containing all HLPRIP usage by the Agency's Authorized Users." Next, bold heading 6.4 Criminal Discovery, in two paragraphs: before releasing data in furtherance of statutory and constitutional discovery obligations a member prosecuting agency must seek express permission from the originating agency; and where the originating agency refuses, the two agencies confer on limitations including judicial protective orders, to protect the originating agency's concerns while letting the prosecutor meet its discovery obligations. Then a bold underlined heading 7) User Access with four paragraphs: each agency approves its own user accounts and warrants Authorized Users are current employees in good standing; access must be removed promptly when a user leaves or becomes ineligible; the database is to be used solely for lawful purposes and never for unethical, illegal or criminal purposes; no user may log in under another user's name or password and passwords may not be shared with anyone, including other Authorized Users; and finally the agencies agree to use the shared data "as a pointer system and not as the source of probable cause for law enforcement actions." Footer, centered: Page 5 of 11, with a smaller right-hand slug HLPRIP MOU updated 01/16/25. Margins are blank apart from light bitonal speckle; the right-margin sweep at 500 dpi found no notes, initials or handwriting. page_footer: Page 5 of 11 document_slug_footer: HLPRIP MOU updated 01/16/25 section_headings: 6.3 Audit; 6.4 Criminal Discovery; 7) User Access audit_log_retention_stated: no less than twelve months audit_log_delivery_interval_stated: bi-annual signature: None initials: None date_written: None amount: None account_code: None po_number: None invoice_number: None agency_name_on_page: None bates_or_production_stamp: None --- page 6 [embedded-ocr] --- In the event of any perceived non-compliance with this MOU and/or the HLPRIP Policies, Procedures and Privacy, the Member Agency LPR Administrator will serve as the POC to discuss any remedies required. In order to protect the integrity of the HLPRIP server system for all law enforcement agencies participating in the program, HLPRIP reserves the right to disconnect individual user accounts and/or agency access for violations of this MOU or the HLIPRIP Policies. 8) Security Requirements Member Agencies agree to maintain and enforce security requirements for the system. Each Member Agency is responsible for the internal security of their records and any technical support necessary to ensure proper security. All Member Agencies and the HLPRIP agree to enforce and maintain security, retention, and purge requirements for the information shared as specified in the Information Practices Act, the Public Records Act, 28 Code of Federal Regulations (CFR) Part 23, and any other laws or regulations governing applicable data types. 9) Connecting with other data sources and analysis platforms HLPRIP will continually work to expand the connectivity of the HLPRIP Database and will actively pursue opportunities to sign MOU agreements with new public agencies and other information sharing systems under the guidelines outlined in this Agreement. HLPRIP will also seek to acquire new analysis systems, and enhance the capabilities of existing platforms, as to provide optimal value for data shared by HLPRIP Database members. Member Agencies agree to grant authority to the HIDTA for the sole purpose of executing information sharing agreements to join new member agencies or information sharing systems into the HLPRIP Database, if approved by the legal counsel representing HIDTA. Such agreements will not require further review or approval by Member Agencies. Such agreements shall have no material changes or provisions that would adversely affect or contradict the policies of this MOU. 10) Admission and Withdrawal of Member Agencies Additional public agencies, or similar regional or statewide sharing systems, may become Member Agencies of the HLPRIP Database upon such terms and conditions as are determined by HIDTA, and by execution of a written amendment to this agreement by the proper authority of the new Member Agency. Existing and future Member Agencies have the right to withdraw from the HLPRIP Database MOU provided by written notice to HIDTA, or may be involuntarily removed upon any breach of this agreement. Page 6 of 11 HLPRIP MOU updated 01/16/25 ···· transcribed by claude-opus-5 vision pass (not OCR) ···· Another clean body page, no handwriting, no signature block. It opens mid-thought from page 5: on perceived non-compliance with the MOU or the HLPRIP Policies, Procedures and Privacy, the Member Agency LPR Administrator serves as the point of contact to discuss remedies. The sentence that follows is set in italics, visibly distinct from the roman text around it: "In order to protect the integrity of the HLPRIP server system for all law enforcement agencies participating in the program, HLPRIP reserves the right to disconnect individual user accounts and/or agency access for violations of this MOU or the HLPRIP Policies." Bold underlined heading 8) Security Requirements: agencies maintain and enforce security requirements; each is responsible for the internal security of its own records and any technical support needed; and all Member Agencies plus HLPRIP enforce security, retention and purge requirements "as specified in the Information Practices Act, the Public Records Act, 28 Code of Federal Regulations (CFR) Part 23, and any other laws or regulations governing applicable data types." Bold underlined heading 9) Connecting with other data sources and analysis platforms, two paragraphs: HLPRIP will keep expanding connectivity and pursuing MOUs with new public agencies and other information-sharing systems, and will acquire new analysis systems; and, materially, Member Agencies "agree to grant authority to the HIDTA for the sole purpose of executing information sharing agreements to join new member agencies or information sharing systems into the HLPRIP Database, if approved by the legal counsel representing HIDTA. Such agreements will not require further review or approval by Member Agencies" so long as they carry no material change contradicting the MOU. Bold underlined heading 10) Admission and Withdrawal of Member Agencies: new agencies or regional/statewide systems may join on terms determined by HIDTA and by written amendment executed by the new agency; existing and future members may withdraw on written notice to HIDTA, or be involuntarily removed for breach. Footer, centered: Page 6 of 11, right-hand slug HLPRIP MOU updated 01/16/25. Bottom third of the page below the last paragraph is blank. page_footer: Page 6 of 11 document_slug_footer: HLPRIP MOU updated 01/16/25 section_headings: 8) Security Requirements; 9) Connecting with other data sources and analysis platforms; 10) Admission and Withdrawal of Member Agencies authorities_cited_on_page: Information Practices Act; Public Records Act; 28 Code of Federal Regulations (CFR) Part 23 signature: None initials: None date_written: None amount: None account_code: None po_number: None invoice_number: None agency_name_on_page: None bates_or_production_stamp: None --- page 7 [embedded-ocr] --- 11) Liability and Indemnification Each Member Agency takes legal and financial responsibility for the actions of their employees, officers, agents, representatives and volunteers. Each agency shall bear the proportionate cost of any damage attributable to the fault of that particular agency, its governing body, officers, agents, employees and volunteers. It is the intention of the Member Agencies that, where fault is determined to have been contributory, principles of comparative fault will be followed. Any contract with a non-member agency receiving services pursuant to this agreement shall include a mutual indemnification provision. The contract shall also provide: 1) That the indemnity obligation shall exist with respect to any claim, loss, liability, damage, lawsuit, cost, or expense that arises out of, or is in any way related to, the performance of services pursuant to the contract; and 2) The obligation of the non-Member Agency and the HLPRIP database pursuant to the indemnification provision will extend, without limitation, to an injury, death, loss, or damage which occurs in the performance of the contract and that is sustained by any third party, any agent, or contractor of the non-Member Agency or the HLPRIP Database. 12) Signatories Not Agents Parties to this Agreement shall have no authority, either express or implied, to act on behalf of any signatory in any capacity whatsoever, as an agent. The Member Agency parties shall have no authority, express or implied, pursuant to this Agreement, to bind each other to any obligation whatsoever. 13) Assignment Prohibited Parties to this Agreement may not assign any rights or obligations pursuant to this Agreement. Any attempted or purported assignment of any rights or obligations pursuant to this Agreement shall be void and of no legal effect whatsoever. When a person with access is no longer employed or otherwise no longer eligible for access, the Member Agency Administrator is responsible for notifying the HLPRIP Regional Administrator who will remove all related passwords and security authorizations from the system. No person shall release any information contained in the HLPRIP Database either by Court Order or in response to a Public Records Act request, unless they are the originating agency or official custodian of such data. Page 7 of 11 HLPRIP MOU updated 01/16/25 ···· transcribed by claude-opus-5 vision pass (not OCR) ···· A clean body page, all roman type, no italics, no handwriting, no signature block. Bold underlined heading 11) Liability and Indemnification. First paragraph: each Member Agency takes legal and financial responsibility for the acts of its employees, officers, agents, representatives and volunteers; each bears the proportionate cost of damage attributable to its own fault; and where fault is contributory, comparative fault principles will be followed. Second: any contract with a non-member agency receiving services under the agreement must include a mutual indemnification provision. Then "The contract shall also provide:" and two indented numbered items. Item 1) the indemnity obligation exists as to any claim, loss, liability, damage, lawsuit, cost or expense arising out of or in any way related to the performance of services under the contract. Item 2) the obligation of the non-Member Agency and the HLPRIP database under the indemnification provision extends without limitation to injury, death, loss or damage occurring in performance of the contract and sustained by any third party, agent or contractor of the non-Member Agency or the HLPRIP Database. Bold underlined heading 12) Signatories Not Agents: no party has express or implied authority to act as agent for a signatory, and Member Agency parties cannot bind one another. Bold underlined heading 13) Assignment Prohibited: rights and obligations may not be assigned and any attempted assignment is void. Two further paragraphs sit under heading 13 that are not about assignment at all: when a person with access is no longer employed or eligible, the Member Agency Administrator must notify the HLPRIP Regional Administrator, who removes all related passwords and security authorizations; and, last, "No person shall release any information contained in the HLPRIP Database either by Court Order or in response to a Public Records Act request, unless they are the originating agency or official custodian of such data." Footer, centered: Page 7 of 11, right-hand slug HLPRIP MOU updated 01/16/25. page_footer: Page 7 of 11 document_slug_footer: HLPRIP MOU updated 01/16/25 section_headings: 11) Liability and Indemnification; 12) Signatories Not Agents; 13) Assignment Prohibited signature: None initials: None date_written: None amount: None account_code: None po_number: None invoice_number: None agency_name_on_page: None bates_or_production_stamp: None --- page 8 [embedded-ocr] --- 14) Costs Unless separate agreements are made, each party shall be responsible for their own costs associated with establishing, maintaining, or terminating their access to, or participation with, the HLPRIP Database. Nothing in this agreement shall be construed to mean that Member Agency parties are subject to incurring new costs. Any applicable user licenses, renewal fees, maintenance costs, or similar outlays must be determined in a separate contract or agreement to be added as an addendum to this Agreement. 15) Data Collection, Retention, and Dissemination 15.1 The LPR data collected by the various Member Agencies participating in the HLPRIP program will be transmitted to the HLPRIP Operations Center via a fiber optic line or through an encrypted Virtual Private Network (VPN). The data will be maintained on the Operation Center server independent of any other law enforcement databases housed at the HLPRIP Operations Center. 15.2 All LPR system data provided to HLPRIP Database will be stored on the Operations Center server for a period mandated by the Member Agency’s state law or policy. If the Member Agency’s state law or policy does not specify a retainment period, all LPR system data provided to HLPRIP will be stored on the Operations Center server for a period not to exceed two years. After the two-year period, the data will be purged unless it has become, or it is reasonable to believe that it will become, evidence, including evidence that tends to inculpate or exculpate a suspect, in a specific criminal or other law enforcement investigation or action. Should data be determined to have evidentiary value, the following paragraph applies: In those circumstances when data is identified as having evidentiary value, the LPR Program Administrator, or designee, will review the facts of the specific case and determine if the data should be saved. If the LPR Program Administrator determines it is reasonable to believe the data has evidentiary value, the Program Administrator will authorize the transfer of the applicable data from the LPR Program server to a form of digital storage media (CD, DVD, etc.) or other portable storage devices. 15.3 Agencies requiring data to be retained by HLPRIP beyond the established retention period may make a formal request to the HIDTA to extend retention. Each request must specify the need for extended retention, the circumstances surrounding the request, the requesting agency's case number, and a specific point of contact within the requesting agency. HIDTA reserves the right to grant or deny agency requests based on the information provided. 15.4 The following methods shall be used when disseminating LPR information: The "need to know" and “right to know," as defined in the HIDTA LPRIP Policies and Procedures, of a potential recipient must be verified and documented prior to dissemination of LPR information. Page 8 of 11 HLPRIP MOU updated 01/16/25 ···· transcribed by claude-opus-5 vision pass (not OCR) ···· A dense body page, no handwriting or signature. Bold underlined heading 14) Costs: absent separate agreement each party bears its own costs of establishing, maintaining or terminating access to or participation with the HLPRIP Database; nothing in the agreement means Member Agency parties are subject to incurring new costs; and any user licenses, renewal fees, maintenance costs or similar outlays must be set in a separate contract or agreement added as an addendum. Bold underlined heading 15) Data Collection, Retention, and Dissemination, in four numbered paragraphs. 15.1 LPR data collected by Member Agencies is transmitted to the HLPRIP Operations Center over a fiber optic line or an encrypted VPN, and maintained on the Operation Center server independent of other law enforcement databases housed there. 15.2 all LPR system data provided to the HLPRIP Database is stored on the Operations Center server for the period mandated by the Member Agency's state law or policy; where state law or policy specifies no retainment period, it is stored "for a period not to exceed two years. After the two-year period, the data will be purged" unless it has become, or is reasonably believed will become, evidence tending to inculpate or exculpate a suspect in a specific criminal or other law enforcement investigation. Then a paragraph set in italics: where data is identified as having evidentiary value, the LPR Program Administrator or designee reviews the facts of the case and decides whether it should be saved, and on so deciding authorizes transfer of the data from the LPR Program server to digital storage media (CD, DVD, etc.) or other portable storage devices. 15.3 agencies wanting data retained beyond the established period may formally request HIDTA to extend retention, stating the need, the circumstances, the requesting agency's case number and a specific point of contact; HIDTA may grant or deny. 15.4 dissemination requires the "need to know" and "right to know" of a potential recipient, as defined in the HIDTA LPRIP Policies and Procedures, to be verified and documented before LPR information goes out. Footer, centered: Page 8 of 11, right-hand slug HLPRIP MOU updated 01/16/25. page_footer: Page 8 of 11 document_slug_footer: HLPRIP MOU updated 01/16/25 section_headings: 14) Costs; 15) Data Collection, Retention, and Dissemination (15.1, 15.2, 15.3, 15.4) default_retention_period_stated: a period not to exceed two years purge_trigger_stated: After the two-year period, the data will be purged transport_stated: fiber optic line or encrypted Virtual Private Network (VPN) evidentiary_transfer_media_stated: digital storage media (CD, DVD, etc.) or other portable storage devices policy_document_named: HIDTA LPRIP Policies and Procedures signature: None initials: None date_written: None amount: None account_code: None po_number: None invoice_number: None agency_name_on_page: None bates_or_production_stamp: None --- page 9 [embedded-ocr] --- 15.5 Requests for Service (RFS) for License Plate Reader data will be processed in accordance with the HLPRIP Policies and Procedures. 15.6 A Law Enforcement Agency's request to query the LPR data shall be processed, provided the agency has a legitimate law enforcement purpose. Mandatory requirements are in place in order to satisfactorily justify the request. 15.7 The primary method of dissemination shall be via email, in an electronic format that employs a reasonable level of security to guard against alteration, or fax. 15.8 If access to secure email accounts is not practical, the information may be provided to the requestor via digital storage media or paper copy, as determined by HIDTA staff. 15.9 Reports and other investigative information received and disseminated by HLPRIP shall be retained within internal electronic HLPRIP files. After disseminating LPR information deemed to have evidentiary value, the completed report containing the data will be entered into a searchable database for future exploitation and auditing purposes in accordance with the HLPRIP Policies and Procedures. 16) Miscellaneous 16.1 Amendments This Agreement may be amended with the unanimous approval of all Member Agencies; provided, however, that no amendment may be made that would adversely affect the interests of the owners of bonds, letters of credit, or other financial obligations of the HLPRIP. 16.2 Conflicts of Interest No official, officer, or employee of the HIDTA or any Member Agency shall have any financial interest, direct or indirect, in the HLPRIP Database. Nor shall any such officer or employee participate in any decision that affects his or her financial interests or those of a corporation, partnership, or association in which he or she is directly or indirectly interested, in violation of any State law or regulation. 16.3 Mediation Any controversy or claim between any Member Agencies, or between any such Member Agency or Member Agencies and the HIDTA, with respect to the HLPRIP Database’s operations, or to any claims, disputes, demands, differences, controversies, or misunderstandings arising under, out of, or in relation to this Agreement, shall be submitted to and determined by mediation. The Member Agency desiring to initiate mediation shall give notice of its intention to every other Member Agency and HIDTA. Such notice shall designate Page 9 of 11 HLPRIP MOU updated 01/16/25 ···· transcribed by claude-opus-5 vision pass (not OCR) ···· A clean, high-contrast scan of a typed contract page set in a Times-like serif face, black on white, straight and unrotated, with no show-through from the reverse. It is the ninth page of an eleven-page memorandum of understanding governing a HIDTA license-plate-reader information-sharing program (HLPRIP). The page opens mid-section with numbered subsections 15.5 through 15.9. 15.5 provides that Requests for Service (RFS) for License Plate Reader data will be processed in accordance with the HLPRIP Policies and Procedures. 15.6 provides that a Law Enforcement Agency's request to query the LPR data shall be processed provided the agency has a legitimate law enforcement purpose, and that mandatory requirements are in place in order to satisfactorily justify the request. 15.7 makes email the primary method of dissemination, in an electronic format employing a reasonable level of security to guard against alteration, or fax. 15.8 permits digital storage media or paper copy where secure email is not practical, as determined by HIDTA staff. 15.9 provides that reports and other investigative information received and disseminated by HLPRIP shall be retained within internal electronic HLPRIP files, and that after disseminating LPR information deemed to have evidentiary value the completed report containing the data will be entered into a searchable database for future exploitation and auditing purposes. A bold outdented heading "16) Miscellaneous" follows, with three underlined bold subheadings: 16.1 Amendments (unanimous approval of all Member Agencies required; no amendment may adversely affect the interests of owners of bonds, letters of credit, or other financial obligations of the HLPRIP), 16.2 Conflicts of Interest (no official, officer or employee of the HIDTA or any Member Agency shall have any financial interest, direct or indirect, in the HLPRIP Database), and 16.3 Mediation (controversies to be submitted to and determined by mediation, the initiating Member Agency to give notice to every other Member Agency and HIDTA). The page breaks mid-sentence at "Such notice shall designate". The foot carries a centred "Page 9 of 11" and, at the right, a smaller "HLPRIP MOU updated 01/16/25". There is no signature, no date entered by hand, no initial, no stamp, no Bates number, no redaction and no dollar figure anywhere on the page. I scanned all four margins numerically for ink: the only sub-150-gray pixels outside the text block are at x 83-95 pt, y 351-361 pt, which a 500 dpi crop shows to be nothing more than the outdented "16)" of the Miscellaneous heading. page_footer: Page 9 of 11 revision_footer: HLPRIP MOU updated 01/16/25 program_name: HLPRIP parent_body: HIDTA sections_on_page: 15.5, 15.6, 15.7, 15.8, 15.9, 16), 16.1, 16.2, 16.3 signature: None date_signed: None initials: None amount: None account_code: None po_number: None bates_number: None --- page 10 [embedded-ocr] --- such other Member Agencies as the initiating Member Agency intends to have bound by any award made therein. Each Member Agency involved in the mediation shall bear its own legal costs, including attorney fees. 16.4 Partial Invalidity If any one or more of the terms, provisions, sections, promises, covenants, or conditions of this Agreement shall to any extent be adjudged invalid, unenforceable, or void for any reason whatsoever by a court of competent jurisdiction, each and all of the remaining terms, provisions, sections, promises, covenants and conditions of this agreement shall not be affected thereby and shall be valid and enforceable to the fullest extent permitted by law. 16.5 Successors This Agreement shall be binding upon and shall inure to the benefit of the successors of the Member Agencies hereto. 16.6 Execution The Governing Authorities of the Member Agencies enumerated herein have each authorized execution of this agreement, as evidenced by the authorized signatures below. 16.7 Entire Agreement This agreement supersedes any and all other agreements, whether oral or written, between the parties hereto with respect to the subject matter hereof and contains all of the covenants and agreements between the parties with respect to said matter, and each party to this Agreement acknowledges that no representations, inducements, promises, or agreements, orally or otherwise, have been made by any party, or anyone acting on behalf of any party, which are not embodied herein, and that any other agreement or modification of this agreement shall be effective only if executed in writing and signed by all current Member Agencies. Page 10 of 11 HLPRIP MOU updated 01/16/25 ···· transcribed by claude-opus-5 vision pass (not OCR) ···· A clean upright scan of the tenth page of the eleven-page HLPRIP memorandum of understanding, same serif typeface and same layout as the preceding page, black on white, no rotation, no show-through. The page opens with the tail of section 16.3 Mediation, completing the sentence carried over from page 9: such other Member Agencies as the initiating Member Agency intends to have bound by any award made therein, and providing that each Member Agency involved in the mediation shall bear its own legal costs including attorney fees. Four underlined bold subheadings follow. 16.4 Partial Invalidity is a severability clause: if any terms, provisions, sections, promises, covenants or conditions are adjudged invalid, unenforceable or void by a court of competent jurisdiction, the remainder shall not be affected and shall be valid and enforceable to the fullest extent permitted by law. 16.5 Successors binds the agreement upon and to the benefit of the successors of the Member Agencies. 16.6 Execution states that the Governing Authorities of the Member Agencies enumerated herein have each authorized execution of this agreement, as evidenced by the authorized signatures below. 16.7 Entire Agreement is an integration clause superseding all other oral or written agreements between the parties, disclaiming any representations, inducements, promises or agreements not embodied in the document, and requiring that any modification be executed in writing and signed by all current Member Agencies. Text ends roughly 55 percent of the way down the page; the lower two-fifths is empty white paper. Despite 16.6's reference to "the authorized signatures below", no signature, signature block, name line, date line, title line or initial appears anywhere on this page — the space below 16.7 is genuinely blank. No stamp, no Bates number, no redaction, no handwriting, no dollar figure. The foot carries a centred "Page 10 of 11" and, at the right, "HLPRIP MOU updated 01/16/25". A numeric ink scan of the margins found sub-150-gray pixels only in the top strip, and a 300 dpi crop shows those to be the first line of body text itself intruding into the strip, not a stamp or marking. page_footer: Page 10 of 11 revision_footer: HLPRIP MOU updated 01/16/25 program_name: HLPRIP parent_body: HIDTA sections_on_page: 16.3 (continuation), 16.4, 16.5, 16.6, 16.7 signature: None date_signed: None initials: None amount: None account_code: None po_number: None bates_number: None --- page 11 [embedded-ocr] --- The parties hereto execute this MOU as of the effective date: A ahave hn faLee , Gecrgry (Agency Name, State) *** (JURISDICTION) *** OCLOY COP Agency ORI # (Originating Agency Identifier) Deputy Chitt 204 /Jechler (Print Name & Title) «a Ob Lee i! Date (Signature must be by the chief executive of your agency or someone authorized to sign on his/her behalf) »,4 Andrew Dimond Date Acting Executive Director Atlanta-Carolinas HIDTA Page 11 of 11 HLPRIP MOU updated 01/16/25 ···· transcribed by claude-opus-5 vision pass (not OCR) ···· The parties hereto execute this MOU as of the effective date. Alpharetta Police, Georgia, ORI 0600400, executed by Deputy Chief Scott Mechler on 11/04/2025. The counterpart signature line for Andrew Dimond, Acting Executive Director, Atlanta-Carolinas HIDTA, is blank and undated on this copy. Agency Name, State: Alpharetta Police, Georgia Agency ORI #: 0600400 Print Name & Title: Deputy Chief Scott Mechler Signature: [present, cursive, not legible as text] Date: 11/04/2025 HIDTA signatory: Andrew Dimond, Acting Executive Director, Atlanta-Carolinas HIDTA HIDTA signature: [BLANK — line unsigned] HIDTA date: [BLANK]