Agency record
Apple Valley Police Department
MN · Municipal Police
The Apple Valley Police Department signed its agreement to feed the LexisNexis Public Safety Data Exchange on 15 November 2023. A lieutenant signed it. There is no sign it went to the city council.
The document is the standard AVCC XML Addendum — the same five-page form that turns a software subscription into a data contribution. Section I.2 commits the department to contribute its public safety information. Section II.1 grants LexisNexis a "paid up, irrevocable, worldwide, non-exclusive license" to use, adapt, aggregate, publish and distribute that data to the company's other law enforcement customers. Irrevocable means what it says: cancelling the subscription does not take the licence back. The department's FBI originating agency identifier, MN0191000, is written on the signature page.
The same records request produced something rarer than a contract: the department's own configuration tables, showing exactly which incidents flow to LexisNexis and who can see them. Every one of Apple Valley's 2,849 offence codes is assigned one of three settings. 1,785 are visible to the public and to law enforcement. 670 are marked "Law Enforcement Only". 394 are marked "Do Not Import" and never leave the building.
That middle setting is the one worth understanding. "Law Enforcement Only" does not mean the incident is held back from LexisNexis. It means it is held back from the public crime map and sent to LexisNexis anyway, into the law-enforcement-facing side of the platform — which, for a department that has signed the contribution addendum, is the national exchange. The 670 offences the department judged too sensitive to show its own residents are in that bucket.
A second table covers calls for service — the dispatch records generated when someone phones the police. Apple Valley has 61 call types, and all 61 are set to "Law Enforcement Only". Not one is excluded. Among them: child protection, criminal sexual conduct, crisis mental health, domestic disputes, missing persons and runaways, welfare checks, and violations of orders for protection. The person at the centre of those calls is usually not a suspect. Often no crime is ever charged.
The department does draw lines. Of 146 sexual assault codes, 89 are excluded from the feed entirely and none are public. Twenty-six offences — all sexual or stalking offences — have their map location randomly shifted by up to 500 feet so a victim's address cannot be read off the public map. That is a real protection, and it is worth saying that Apple Valley applied it. But it is a public-map protection. The offset does not touch the copy that goes to law enforcement subscribers.
One detail on the signed addendum shows how narrow these choices can be. Section II.1 lets a department initial a line declining to share a stripped-down, de-identified version of its data with third parties for public crime mapping. Apple Valley's lieutenant initialled it. But that option covers only the de-identified subset. The main grant — the full contribution, licensed to LexisNexis's law enforcement customers — has no opt-out line on the form at all. The signature page offers a choice about the smaller of the two flows.
The configuration tables also carry dates, and they are older than the contract. The earliest entry is 19 April 2013; 2,630 of the 2,849 offence codes were configured before the addendum was signed in 2023. The calls-for-service table was built over three days in August 2017. The pipe, in other words, appears to have been running for a decade before the department agreed to contribute. LexisNexis had acquired the company behind Apple Valley's public crime map in 2015. What the 2023 signature did was not build a connection. It attached an obligation to one that already existed.
Apple Valley sits in Dakota County, in a state the Department of Homeland Security designated a sanctuary jurisdiction in May 2025. Minnesota law limits what local police may hand federal immigration authorities directly. The addendum hands LexisNexis an irrevocable licence to distribute the same records to its customers, and ICE has been one of them.
Contract signals
- Database Interface (Schedule A)
- ○ not in record
- AVCC XML Addendum present
- ● confirmed
- Irrevocable license clause
- ● confirmed
- Jail Booking Search & Report
- ○ not in record
- Community Crime Map
- ● confirmed
- BuyCrash (crash data feed)
- ○ not in record
Technical
- RMS vendor
- —
- CAD vendor
- —
- Data fields shared (known)
- DOCUMENTED FROM THE AGENCY'S OWN CLASSIFICATION TABLES (Aug 5 2026 FOIA return), not inferred from contract language. RMS / crime data — 2,849 offence codes classified: - 1,785 "Public and Law Enforcement" (public crime map + LE product) - 670 "Law Enforcement Only" (LE product only; for a signed PSDEX contributor this is the contribution) - 394 "Do Not Import" (excluded from LexisNexis entirely) - 26 codes carry a "500 Foot Offset / Random Offset" — all sexual or stalking offences; a public-map control only, it does not apply to the law-enforcement copy CAD / calls-for-service data — 61 call types, ALL classified "Law Enforcement Only". None public, none excluded. Includes child protection, criminal sexual conduct, crisis mental health, domestic/disputes, missing person/runaway, welfare check, medical, juvenile complaint, threats/stalking, OFP/DANCO violation. Sensitive-category splits (RMS): Sexual Assault 146 codes — 89 excluded, 57 LE-only, 0 public. Sexual Offence 88 — 28 excluded, 45 LE-only, 15 public. Homicide/Manslaughter 14 — 11 public, 3 LE-only, 0 excluded. LIMIT OF THIS EVIDENCE: these tables classify offence and call TYPES, not data FIELDS. They do not show whether victim name, DOB, address, phone or incident narrative transmit. Do not cite them for the field-level victim/witness question. The Interface Control Document / data-translation guide remains outstanding. Not confirmed: Database Interface line item, Jail Booking Search & Report — the Schedule A was not produced.
Sanctuary status
- Sanctuary jurisdiction
- Yes
- Bypass confirmed
- —
Source
- Document type
- FOIA Return
- Discovery method
- —
- Source document
- View document →
Source documents (4)
Companion spreadsheet to the crime classification table, titled "Data Classification CFS Results", generated 8/5/2026. Four columns: CFS Type, CFS/CAD Classification, Viewable By, Created/Updated. 61 call-for-service types, every one of them classified "All Other" and set to "Law Enforcement Only". No CFS type is public and none is excluded. All 61 rows are dated 7–9 August 2017. The existence of this table is the point: it confirms that Apple Valley's LexisNexis feed carries computer-aided dispatch data — calls for service — and not only records-management crime data. The 61 call types include: child protection, criminal sexual conduct, crisis mental health, domestic/disputes in progress, domestic/disputes rpt, missing person/runaway, medical, medical/priority, welfare check, juvenile complaint, harassment, threats/stalking, and OFP/DANCO violation (Minnesota's orders for protection and domestic abuse no-contact orders).
Spreadsheet titled "Data Classification Crime Results", generated 8/5/2026, listing every one of the 2,849 offence codes in Apple Valley PD's records system and how each is handled in the LexisNexis feed. Eight columns: Crime, Event Classification, NIBRS Category, Viewable By, Random Offset, Created/Updated, Crimes Against, Group Offenses. "Viewable By" is the routing switch and carries three values. 1,785 offence codes are set to "Public and Law Enforcement", 670 to "Law Enforcement Only", and 394 to "Do Not Import". "Random Offset" is a location-fuzzing control, set to "No Offset" on 2,823 codes and "500 Foot Offset / Random Offset" on 26. Every one of the 26 is a sexual offence or a stalking offence. The Created/Updated column spans 19 April 2013 to 3 August 2026. 2,630 of the 2,849 rows carry a date earlier than the November 2023 addendum signing. This is the closest thing in the database to the field-mapping document the project has been requesting by FOIA — not a field-level schema, but the agency-side configuration that decides which categories of incident enter the LexisNexis platform and who sees them once there.
Email chain dated January 7, 2026, released by the Duluth Police Department. Alyssa Baumann, Duluth PD's senior crime and intelligence analyst, asked LexisNexis for a summary of services ahead of a city council presentation on the department's Accurint Virtual Crime Center and TraX subscriptions. Jeremy Bringle, a LexisNexis Risk Solutions strategic account manager, replied within minutes with marketing copy and four attachments, among them a Word document headed 'Minnesota Agencies Contributing Data to AVCC' listing 72 Minnesota law enforcement agencies by name. The bundle also contains the AVCC product brochure and the Accurint TraX brochure. Bringle's covering line describes the roster as the agencies whose data Duluth can see through AVCC, while the attachment itself is headed as a list of contributors. The 72 named agencies span the Twin Cities metro, central Minnesota, and two outliers in St. Louis County. Duluth PD, the recipient, is not on the list, and is separately documented as having signed the non-contributory variant of the AVCC XML Addendum.
Fully executed five-page "Accurint Virtual Crime Center/Accurint Crime Analysis/LexisNexis Community Crime Map/AVCC XML Addendum" for the Apple Valley Police Department, obtained in a records request return. Form code ADDM_ AVCC/ACA/CCM (Q3.21.v1) — the standard contributory variant, not the "NO DATA CONTRIBUTIONS TO PSDEX" read-only variant. Execution details, all from the document's own form fields and signature page: Customer "Apple Valley MN Police Department"; ORI number MN0191000; signed by Lieutenant Alan Spillers on 11/15/2023. Spillers is also named as the agency's PSDEX submissions contact under Sec I.4.f, at 7100 147th St W, Apple Valley MN 55124, 952-953-2700, Alan.Spillers@applevalleymn.gov. All three core contract signals tested. Sec I.2 contribution obligation: present. Sec II.1 irrevocable worldwide license: present. Database Interface: not testable from this document — the Schedule A was not produced and remains outstanding. The optional de-identification line in Sec II.1 was initialed "A S" in handwriting, electing the opt-out. Exhibit A is the FBI CJIS Security Addendum (CJIS Security Policy Appendix H).
Have something we don’t?
If you have a contract, FOIA return, or council packet for this agency, send it via the tip line.
Last researched September 17, 2026