Document Library
Primary sources. Signed contracts, FOIA returns, procurement records, and policy documents. Each entry links to the underlying source.
How to use this page
Documents are organized by category. Click a category tab to filter. Use “All” to browse everything. Click any document title to read it in full. Use the tip line to submit records we don’t have yet.
- Contributing Agency Agreements
- Signed contracts, Schedule A addenda, and AVCC XML Addendums in which a law enforcement agency formally agrees to contribute data to PSDEX. These contain the specific legal language — irrevocable licenses, data contribution obligations — that confirm an agency is feeding data to LexisNexis. Start here.
- Non-Contributing Agency Agreements
- Documents for agencies that have explicitly opted out or hold read-only access — including "NO DATA CONTRIBUTIONS" addenda and contracts limited to querying only. Important context for understanding who resisted the system and how.
- Public Safety Policies
- Department-level policies on data sharing, surveillance, and LexisNexis use. Useful for identifying agencies whose published policies may conflict with their documented data-sharing behavior — a key signal of sanctuary bypass.
- Audit Records
- Internal records of who accessed PSDEX data and how. Multiple public records requests indicate that agencies cannot audit this once data enters the system — which is why this tab may remain empty.
- City Council Meetings
- City and county council packets, votes, and resolutions approving or discussing LexisNexis contracts. Often the only public record of when and how a jurisdiction entered the PSDEX network.
- Law Enforcement Consortiums
- Documents from AVCC/PSDEX consortium bodies — governance minutes, member-agency joinder agreements, and inter-agency MOUs. Consortiums are regional networks where a lead agency holds the master contract and smaller agencies join through joinder agreements. These records often name member agencies not discoverable any other way.
- Inter-Agency MOUs
- Memoranda of Understanding, joinder agreements, and inter-agency contracts that define the legal structure of data sharing between agencies and consortiums. These establish what flows where and under what terms.
- Integrations with Vendors
- Technical and contractual documentation of how LexisNexis connects to other law enforcement systems — RMS, CAD, VINE, N-DEx. These integrations are the on-ramps: how data leaves local agency systems and enters the PSDEX pipeline.
- State Cooperative Documents
- Statewide cooperative purchasing contracts that let any state government entity procure LexisNexis products without a separate competitive bid. These dramatically expand the number of agencies in the system, often without a local council vote.
- Data Access
- Documents describing who has access to PSDEX data and under what terms — subscriber agreements, access logs, and records identifying which federal, military, or commercial entities are permitted to query the system.
Technical and contractual documentation of how LexisNexis connects to other law enforcement systems — RMS, CAD, VINE, N-DEx. These integrations are the on-ramps: how data leaves local agency systems and enters the PSDEX pipeline.
Arvada PD shares all mobile license plate reader data with LexisNexis Risk Solutions — meaning plate reads captured on Arvada streets may be accessible to thousands of LexisNexis law enforcement customers nationwide. §460.6(a)(2) of the department's official ALPR policy (effective June 2025) states that mobile ALPR data 'is also retained by LexisNexis Risk Solutions, per agreement with the Arvada Police Department.' The underlying agreement is not disclosed. It is unknown whether this data flows into PSDEX, the Accurint ALPR aggregation product, the Public Safety Marketplace, or another LexisNexis product line — each carries different downstream access implications.
LexisNexis Technical Setup Requirements — Accurint Crime Analysis / AVCC / Lumen (Client, 08-2022)
LexisNexis Risk Solutions Technical Setup Requirements for Accurint Crime Analysis, the Accurint Virtual Crime Center, and Lumen (Client version, dated 08-2022). The document is the engineering playbook behind PSDEX contribution. It instructs the agency to stand up a computing environment inside its own network where LexisNexis builds a custom interface named the PSDex Data Client. That client runs an automated ETL process that extracts read-only data from the agency Records Management System and Computer-Aided Dispatch, reformats it, and uploads it to LexisNexis servers over SFTP. The setup runs on a daily schedule, with a service account whose password is set never to expire so the job does not break, and LexisNexis is given VPN access into the agency network to build and maintain it. Two details stand out. First, the document states a data preference: limited copies and filtered views are not preferred, and raw access to the unfiltered RMS is preferred. The default configuration pulls the whole records system rather than a curated subset. Second, the document publishes the exact network destinations an agency firewall must allow, including PSTRANSFER, PSIMPORTER, and API.PSDEX at lexisnexisrisk.com, plus communitycrimemap.com and the Lumen environment in AWS GovCloud. Those endpoints are a fingerprint: a network that talks to them is running the contribution pipeline. This is a generic vendor document rather than an agency-specific contract, so it does not by itself establish that any particular department contributes. What it establishes is the mechanism. It is the technical counterpart to the AVCC XML Addendum: the addendum is the legal permission to contribute, and this is the plumbing that carries the data out. It also confirms that Community Crime Map is fed by the same Data Client, which supports treating CCM presence as a contribution indicator.
LexisNexis vendor manual confirms the Community Crime Map, Accurint Virtual Crime Center, and Accurint Crime Analysis run on a single shared data layer classified through one agency-administered console at accurint.com. Every imported crime type defaults to Law Enforcement Only visibility, meaning the full RMS feed reaches LexisNexis before any public-facing privacy filtering is applied. The 500-foot random offset agencies apply to sensitive incidents (sexual assault, homicide, death investigations) affects only the public map; exact locations remain visible to law enforcement users in AVCC and ACA. Administrator guide, doc code RE_GD_019.126P2 / CE20.282JN, © 2023 LexisNexis Risk Solutions.