The Oklahoma City Example
For twelve years, Oklahoma City contributed its police data to a LexisNexis data-sharing system. No clause in its contract restricted where that data could travel. In April 2026, after public pressure, the city council added one. This is the story of how that clause came to exist, and why it matters for every city running the same software.
Since 2014, Oklahoma City has run a regional police data warehouse. It now runs on LexisNexis software called the Accurint Virtual Crime Center, and fourteen area agencies feed it. The pitch was sensible: break down jurisdictional walls so neighboring departments can see the same information.
The problem was the fine print. Nothing in the contract said where Oklahoma City's contributed data could go once it entered the LexisNexis system, a system the company sells access to far beyond Oklahoma. As ICE ran the largest immigration operation in the country's history, residents started asking the obvious question: who else can access our city's police records?
On April 21, 2026, the council renewed the software and added Amendment No. 1, which restricts sharing of Oklahoma City's contributed data to the city's own consortium and prohibits its distribution to any entity outside it. The city kept the tool, but fenced off the data so that only neighboring agencies could share records. Recognizing the problem, fixing it, and doing all of it through public records and open council debate is what makes Oklahoma City a useful example for other cities trying to take back control of where their residents' data goes: read what they have signed, push back in the open, and decide for themselves whether to fence the data or end the contract entirely.
A quiet decade, then a reckoning.
Every claim below comes from Oklahoma City's own procurement records, the signed LexisNexis contract, council meeting video, and local news coverage. The documents are linked at the bottom.
The Quiet Decade
A reasonable-sounding regional data warehouse, renewed every year as a routine sole-source item almost nobody read.
The data warehouse is born
After a competitive bid, the Oklahoma City Council approves a centralized data warehouse so contiguous agencies can pool and query each other's records. The stated goal is to break down traditional jurisdictional barriers. It runs on Bair Analytics software, hosted by the police department.
LexisNexis buys the vendor
LexisNexis Risk Solutions acquires Bair Analytics and agrees to keep hosting Oklahoma City's system. A local crime-mapping tool quietly becomes a node inside a national data broker's network. The product is rebranded over time as the Accurint Virtual Crime Center.
FY2025
Renewed on autopilot
Oklahoma City migrates to the LexisNexis cloud-hosted Accurint Virtual Crime Center and renews the arrangement year after year as a sole-source purchase. The justification is consistent: LexisNexis is the only company that links integrated public-records searches to local law enforcement data, so there is nobody else to buy it from.
LexisNexis has setup integrations with the area agencies to share data through their systems and link that with available public data. They are the only ones who have this setup.
Asked on the same form what the consequences would be of not approving the purchase, the department's answer was five words.
People get hurt or killed.
The Reckoning
Against a national backdrop of aggressive immigration enforcement, the routine renewal stops being routine.
Feb 2026
The national backdrop: Operation Metro Surge
Roughly 1,000 miles north, ICE and Border Patrol run Operation Metro Surge across Minnesota, which the Department of Homeland Security calls the largest immigration enforcement operation ever carried out. The operation is national news for months. ICE has publicly described LexisNexis data as mission-critical to its deportation work. The connection is not lost on people in other cities running LexisNexis software.
The FY26 paperwork is filed
OKCPD files the sole-source documentation to renew the Accurint Virtual Crime Center for 2026. The signed Schedule A puts the annual subscription fee at $173,889.26 and lists fourteen agencies on the account. The council's own resolution cites a figure of $165,608.82 for the purchase. The two numbers do not match (see Sourcing & Notes).
A council member asks the question
During a council session, council member James Cooper raises the city's association with LexisNexis directly. The police chief speaks about Accurint and its investigative value. He does not mention that the city contributes data into the LexisNexis system, or where that data can travel once it does. The discussion touches both the Accurint platform and a separate LexisNexis citizen-reporting contract.
The press picks it up
Local outlets report that Oklahoma City is weighing crime-fighting software amid privacy concerns, putting the LexisNexis relationship in front of a wider audience and framing the renewal as a live civic question rather than a rubber stamp.
A civil-rights attorney names the pipeline; the vote is deferred
At the next meeting, council members sit down with the chief and IT staff. Deputy Chief Jason Sandall fields questions. A civil-rights attorney, Anna Nathanson, who says she has tracked the company since 2019, testifies that LexisNexis data is mission-critical to ICE deportations and that the city should not deepen a partnership with a company so closely entwined with federal immigration enforcement.
The item on the floor that night is a separate $67,500 LexisNexis Coplogic contract for a citizen online-reporting portal. Asked whether that data is shared with the federal government, police say no: the portal is closed, shared with no other entities, and purged after 90 days. Nathanson counters that the reporting tool is a data-collection product whose participant data is shared with other users on the LexisNexis platform, including ICE. The two accounts do not agree. The council defers the vote.
The renewal returns, with a fence attached
The Accurint Virtual Crime Center renewal comes back to the council as Agenda Item IX.D, presented by the city manager and the chief. This time it carries Amendment No. 1. After more pushback from the dais and the public, the council approves it. The amendment is the part that changes the story.
The amendment restricts access to and sharing of data contributed by the Oklahoma City Police Department to only those entities specifically authorized as part of the Oklahoma City consortium, and prohibits disclosure or distribution of that data to any other entity outside the consortium.
Same software. Two completely different data deals.
The Accurint Virtual Crime Center can be run two ways. The default exposes your residents' data to a national system. The Oklahoma City model keeps it home. Nothing about the software forces one or the other. It comes down to what your contract says.
Contribute to the national pool
- Your department's records feed the shared LexisNexis system.
- No contract clause limits which entities can access what you contribute.
- Access is sold by LexisNexis to customers well beyond your region, including federal agencies.
- Victim, witness, and suspect information can travel with the rest of the record.
- Your council and your residents may never see where the data goes.
Contribute to a named consortium only
- Your records are shared only with agencies you specifically authorize.
- An amendment prohibits distribution to any entity outside that consortium.
- You keep the regional collaboration the tool was bought for.
- The restriction is written into the contract, not left to a vendor's policy.
- The limit is public, in a council resolution anyone can read.
The fence, drawn out
Oklahoma City's amendment restricts its data to the fourteen agencies on its own account. That roster is the consortium. Everyone inside the line can see the shared data. Nobody outside it can.
Source: signed LexisNexis Schedule A, Accurint Virtual Crime Center Online (Subscription), Customer: Oklahoma City Police Department, term Jan 1 – Dec 31, 2026.
You do not have to choose between a useful tool and your residents' privacy.
Oklahoma City is useful precisely because it is not a story about banning software. It is a story about reading a contract and changing one term. Here is the practical version for the two people most likely to be on this page.
Make the ask specific
- Get the contract itself, not the budget line. Ask for the signed Schedule A and any addendum by name. The order form alone doesn't contain the data sharing terms.
- Ask the questions that matter: "Do we share data with the national PSDEX exchange? Do we contribute data via our AVCC agreements, and if so, who has access to our city's police data?" If the answer is a description of the search tool, you have not been answered.
- Demand a ban, or a fence at least. Oklahoma City moved because council members and residents pushed back: against the claim that this was only a search tool, and against paying a company that supports ICE. The more they dug, the more they uncovered, until the police department put responsible restrictions in place itself in order to keep the product.
- Put it on the record. Public testimony and press coverage are what moved the OKC timeline from January question to April amendment.
Scrutinize all of it. A ban is on the table.
- Read the whole paper trail. Pull every contract, schedule, and amendment tied to LexisNexis, including the renewals before this one. Ask staff directly: do we contribute data to the national PSDEX exchange? Is there any integration between AVCC or PSDEX and our RMS, CAD, or other records systems?
- Consider ending the contract. If your city has been feeding resident data into a private platform that sells access to ICE and other agencies, pulling the tool is a legitimate option. So is asking who authorized that, and holding them accountable.
- If you keep it, fence it. Introduce an amendment that prohibits sharing city police data with outside agencies through private platforms. At most, share with named local consortium members.
- Demand audit trails. Require records of who queries your city's data and how. Does it include juvenile data? Does it include sexual-assault victim data? Ask whether that information is shared with other agencies with no accountability, and whether you would ever vote to allow that.
- Make the limit public. Put the restriction in the resolution itself, so the next council, the next reporter, and the public can find it.
- Commission a study. Ask whether there are better ways to share and integrate systems with your neighbors than routing resident data through a private national database.
Template language
Adapt the operative language Oklahoma City adopted. Run it past your municipal counsel. The point is to name a closed set of authorized entities and to forbid distribution outside it.
This Amendment restricts access to and sharing of data contributed by the [AGENCY NAME] to only those entities specifically authorized as part of the [NAMED CONSORTIUM], and prohibits disclosure or distribution of that contributed data to any other entity outside the consortium. This restriction survives termination of the underlying subscription, and the vendor shall delete contributed data upon written request.
The first two sentences track Oklahoma City's adopted Amendment No. 1. The survival-and-deletion sentence is a FinePrint recommendation drawn from how these subscriptions handle data after cancellation; it is not part of the OKC resolution. Confirm both with counsel.
How we know what we know.
We can confirm Oklahoma City contributed data to a LexisNexis-hosted system, and that its earlier contracts contained no language restricting that data to the consortium. Its Schedule A did not carry the typical national-exchange restriction, and it did not clearly exclude it either; the terms were ambiguous. In our research, agencies whose contracts lack restrictive language have generally been found to contribute to the national database. We do not yet have direct confirmation that Oklahoma City's data reached the national exchange before 2026. The clearest evidence that it was unrestricted is Amendment No. 1 itself: a city does not need to add a restriction to a system that was already restricted.
The signed Schedule A states an annual subscription fee of $173,889.26. The council's sole-source documentation and resolution cite $165,608.82 for the purchase. We use the higher figure where we describe the contract, and flag the discrepancy here. The gap likely reflects a credit, a cost-share among consortium members, or a prior-year adjustment, but the records we have do not reconcile it. We are confirming through follow-up records.
The police department and the testifying attorney gave directly conflicting accounts of the Coplogic citizen-reporting portal. We report both and take neither as settled. The document that would resolve it is the Coplogic contract and its data-handling terms, which we are seeking.
FinePrint standard: every claim links to a primary source. AI-assisted research is flagged until independently confirmed. Document links marked as public records will resolve to hosted copies when this page goes live.