# Peregrine and Carahsoft Executed Contract `CON-002_Peregrine_Carahsoft_Executed_Contract_2026-03-17.pdf` is a 24-page executed package for the [[Sixth Judicial District Prosecuting Attorney's Office]] to obtain the [[Peregrine Technologies, Inc.]] platform through reseller [[Carahsoft Technology Corp.]] under NASPO master contract `AR2472`. It contains a $3 million quote, Peregrine subscription terms, service-level terms, and an Arkansas contract addendum. The execution page carries state approval dated 2026-03-16 and Carahsoft acceptance dated 2026-03-17 (p. 24). Execution establishes contractual assent; it does not establish that the funding condition occurred, that payment was made, or that the platform went live. ## Price, term, and scope The Carahsoft quote totals **$3,000,000** and lists three one-year Peregrine subscription periods, each including data integration and unlimited users (p. 2, "TOTAL PRICE: $3,000,000.00"). Support, training, and cloud hosting are included in the firm-fixed-price license (p. 3). The scope names: - **Phase 1:** 22 data-contributing agencies, with RMS products identified, plus Prairie Grove Police Department as access-only (pp. 2-3). - **Phase 2:** 22 additional police departments, many with RMS "to be determined" (p. 3). - **State sources:** Arkansas State Police ACISS and e-Cite traffic-crash data are expressly listed in Phase 1 (p. 3). The 45 named agency roles differ from the later 44-row July status table. Pine Bluff, Forrest City, and Helena occur in the contract but not that table; Benton County Sheriff's Office and the Arkansas Attorney General's Office occur in the table but not the contract. See [[ACIN Participant and Integration Status]] and [[T032 - ACIN Participation Rosters and Agreement Status]]. ## Funding condition The controlling quote language provides: > "Customer shall notify Carahsoft and Peregrine in writing when the funds allocated for this Agreement have become available for obligation and expenditure." After that notice, kickoff is to occur within 14 days and full payment becomes due within 30 days (p. 3). The package contains no such notice, kickoff record, purchase order, invoice, payment, acceptance, or go-live record. > [!contradiction] Executed contract versus unawarded federal request > The contract is signed, but performance and payment are expressly triggered by written notice that funds are available (p. 3). The final custodian email says DOJ had not issued an award package or approved a final budget as of 2026-07-23. See [[T029 - ACIN Funding Obtained Language vs No Federal Award]]. ## Platform capabilities Peregrine defines the service as a cloud platform for integrating, modeling, searching, analyzing, visualizing, sharing, and acting on multiple data sources. Named functions include comprehensive search, workflows, dashboards, real-time alerts, trend analysis, geospatial analysis, link analysis, temporal analysis, and permission-based collaboration (p. 5). The Arkansas addendum requires: - a separate environment for non-aggregated, source-restricted RMS data used by approved third-party vendors, with role-based access, audited logging, and least privilege (p. 20); - U.S.-only AWS GovCloud or Azure Government hosting (pp. 20-23); - AI/ML decision support whose outputs remain subject to human review (p. 22); - logs sufficient for post-hoc review and up to 4,000 authorized users (pp. 22-23). These are contractual capabilities and requirements. The package supplies no configuration or usage export proving implementation. ## Ownership, derived data, and vendor access - End User Data remains the exclusive property of the customer and participating agencies (p. 5). - Peregrine owns Usage Data and de-identified data, subject to negotiated limits barring reidentification, commercialization of ACIN-derived law-enforcement intelligence, and product marketing without consent (pp. 4-8). - Peregrine receives a limited license to host, store, process, and use End User Data to provide and improve the service and generate Usage Data and de-identified data (p. 8). - The terms authorize offsite access to End User Data and production platforms as needed to provide services, while restricting sale, disclosure, or monetization outside the agreement (pp. 6, 9). ## Termination and deletion After termination, the customer may request permanent deletion of End User Data; Peregrine must comply within 30 days. Without a deletion request, Peregrine retains the data for 60 days and may then permanently delete it unless law requires otherwise (pp. 11-12). That vendor-exit rule coexists with ACIN's five- and seven-year internal retention provisions. The documents do not fully explain which system remains the authoritative copy after withdrawal or termination. ## Draft artifacts inside the signed package Pages 20-23 remain headed `Draft 01-07-2026` and visibly contain redline, formatting, and replacement-text artifacts. Page 24 nonetheless presents the addendum as approved and accepted. The record therefore supports describing the package as executed while also preserving that four incorporated pages still visually read as draft working text. ## Significance The contract identifies the selected core integration platform, a concrete agency/data-source scope, substantial analytical capabilities, vendor access and derived-data rights, hosting requirements, and a funding-triggered performance sequence. It materially deepens [[T014 - ACIN Analytical Reach vs Non-Surveillance Classification]] while leaving actual funding and operation unresolved. ## Open questions / follow-ups - Produce the written funding-availability notice, purchase order, invoice, payment, kickoff, implementation schedule, and acceptance tests. - Identify the effective contract term after the NASPO quote's stated 2026 expiration and the three subscription years. - Produce the final clean addendum without draft/redline artifacts. - Produce the approved system architecture, data dictionary, access roster, audit export, and third-party-vendor environment configuration.