Contract amendment · Oklahoma City, Oklahoma · Signed by LexisNexis March 13, 2026; adopted April 21, 2026
Oklahoma City’s AVCC amendment
The only contract in this library that names federal agencies and shuts the door. It restricts where the data can go. It says nothing about how long it stays or whether it ever comes back.
3
Meets
4
Partial
0
Fails
17
Missing
of 24 practices this document could address
Oklahoma City has hosted a data-sharing warehouse for fourteen metro agencies since 2014, first on Bair Analytics software and, after LexisNexis bought Bair, on the Accurint Virtual Crime Center. In April 2026 the council renewed the subscription for $165,608.82 and, in the same item, approved an amendment the police department negotiated after two council members started asking about ICE. The vote was 7 to 2.
The amendment adds a section to the addendum: LexisNexis “will maintain data sharing restrictions that prevent nationwide sharing,” defined as “no access by any non-Consortium agency or user, including any state or federal entity,” without the city’s prior written authorization. Any legal process aimed at the city’s data triggers prompt notice, cooperation on a protective order, and minimum disclosure. The restriction overrides the addendum’s license grant “to the extent of any inconsistency.” A police captain told two council members in February that LexisNexis “agreed to all our requirements without changes.”
The three pages contain no retention period, no deletion duty, no requirement that consortium members destroy downloaded copies, no data return at termination, no audit right for the city, and no remedy for breach. The irrevocable license survives for everything the amendment does not contradict. FinePrint’s earlier reporting treated the amendment as a draft; the executed version, signed by LexisNexis’s CEO, is in the public council packet at pages 558 to 560.
Primary source
Amendment No. 1 to the AVCC/ACA/Community Crime Map Addendum, City Council packet, April 21, 2026, Item IX.D (pp. 554 to 582)Read 2026-09-28
Document
Practice by practice
What the document says, or does not say, on each practice in the Standard. Practices this kind of document has no business addressing are marked n/a. These marks are evidence for a jurisdiction’s grade; the document itself gets no score.
Stage 1
Decide
- Missing
The sole-source form says the consequence of not renewing is “People get hurt or killed.” That is a justification for the vendor, not a necessity finding for the system.
- Missing
- Meets
1.3Public notice and a recorded vote
Open session, memo and amendment in the public packet, recorded 7 to 2 vote. The renewal has been a council item every year since 2014; this is the year someone read it.
Stage 2
Acquire
- Partial
2.1Direct contract, no marketplace add-ons
A direct contract with LexisNexis for a platform. Schedule A lists the products bought; add-ons enabled inside AVCC would not appear here.
- Missing
2.2Published use policy before deployment
No use policy attached to the item.
- Partial
Twelve-month term, renewed by council vote. Renewal does not require re-justifying the program, and the sole-source form makes it a formality.
- Partial
2.4No irrevocable license to the vendor
The addendum’s “paid up, irrevocable, worldwide” license stands, overridden only “to the extent of any inconsistency” with the consortium-only rule. Still irrevocable inside the consortium and for LexisNexis’s own use.
Stage 3
Deploy
Stage 4
Use
- Missing
Stage 5
Share
- Meets
5.1No sharing without a published policy
“No access by any non-Consortium agency or user, including any state or federal entity,” without prior written authorization the city may withhold “in Customer’s sole discretion.” Notice before any outside disclosure. This is the clause every other PSDEX contributor is missing.
- Partial
The consortium is named: fourteen agencies listed in Schedule A. Nothing restricts LexisNexis’s own internal use, analytics, or sub-processors.
- Missing
The amendment restricts distribution, not retention. Nothing requires consortium members to delete downloaded copies.
- Meets
5.4Consortium and platform terms are public
The consortium agreement, Schedule A and every member agency are in the public packet.
Stage 6
Retain
- Missing
6.1Shortest retention that serves the stated purpose
No retention period anywhere in the amendment or Schedule A.
- Missing
Stage 7
Audit
- Missing
7.2Logs available to the oversight body
No audit or verification right for the city. It has to take LexisNexis’s word that the controls exist.
Stage 8
Retire
- Missing
No termination trigger or remedy if the restriction is breached.
- Missing
8.2Exit terms and certified destruction
No data return or destruction at the end of the subscription.
What to take from it
One practice, done properly, by a city that asked. The amendment proves the baseline contract lets the data go anywhere, and it proves LexisNexis will sign a restriction when a customer insists. Every other contributor could ask for the same paragraph. Then they should ask for the paragraphs Oklahoma City forgot: a clock, a deletion duty, an audit right, and an exit.