1. FOIA your local department.

Send the request below to your local police department’s public-records officer. Replace bracketed placeholders.

Subject: Public Records Request — LexisNexis Accurint Virtual Crime Center Contract

Pursuant to [STATE FOIA LAW], I request the following records regarding your agency’s agreement with LexisNexis Risk Solutions:

1. The fully executed Accurint Virtual Crime Center (AVCC) agreement, including all exhibits, Schedule A, addendums, and amendments. Specifically include the AVCC XML Addendum or PSDEX Addendum that governs data contribution.

2. Any Interface Control Document (ICD) or technical specification that defines the data structure and elements for the automated export of Records Management System (RMS) or Computer-Aided Dispatch (CAD) data to LexisNexis Risk Solutions.

3. Any Data Translation guides, field-mapping tables, or schemas identifying which specific data fields (e.g., Victim Name, DOB, Witness Phone, Narrative) are included in the automated feed to LexisNexis.

We are not seeking URLs, credentials, network addresses, or encryption keys. We seek only the identity of data fields and legal terms governing their transfer.

2. Ask your council member or oversight body.

LexisNexis contracts are typically processed as routine procurement items. The key data-sharing terms — including an irrevocable license clause and an automated upload obligation — appear in a separate AVCC XML Addendum that often receives no independent review. Asking your elected representative to account for those terms is a basic exercise in local oversight. Forward any response you receive to tips@fineprint.report — it helps document what officials actually know.

Dear [Member / Supervisor],

I’m writing to ask about [Department]’s contract with LexisNexis Risk Solutions for the Accurint Virtual Crime Center (AVCC). Records obtained from other jurisdictions show that these contracts typically include an AVCC XML Addendum granting LexisNexis an irrevocable license to use, aggregate, and redistribute data uploaded by the department — including incident reports, dispatch records, and information about victims and witnesses who were never charged with any crime.

I’d like to understand what public oversight has been applied to this arrangement. Specifically:

1. Was the AVCC XML Addendum — the data-contribution and licensing annex — included in the materials presented to the council, or only the base Schedule A?

2. Does the contract include any restriction on which data fields (e.g., victim names, witness contact information, incident narratives) are included in the automated upload to LexisNexis?

3. Has [Department] received any documentation of which federal agencies — including ICE — have searched records contributed by [Department] through the LexisNexis platform?

I’m not asking you to take a position — I’m asking what your office knows and what the public record shows. A written response would be appreciated.

3. Use the (limited) opt-out anyway.

The LexisNexis consumer opt-out doesn’t reach police-report data. It does reach the consumer-side products — Accurint Person Search results, mailing-list products, and some marketing pools — that compound the exposure. Filing opt-outs reduces the surface area without solving the core problem.

The form is at lexisnexis.com/privacy. (We don’t link out to LexisNexis here; you can find their privacy page directly.)