PoliceCensus

Home / Held

What this site holds back

This site’s argument is about what police agencies do not report. This page applies the same test to the site itself: what it holds and does not publish, what it publishes only with a stated limit, and what it chose never to acquire — with the reason for each, in the source’s own words where the reason is the source’s own words.

Every count on this page is read from the database when the page is requested. Quoted wording, dated probe results and the one column count taken from a source file that is not loaded are marked as such where they appear. Disagree with an entry, or know something that settles one? See Corrections.

Published only with a stated limit

Mapping Police Violence

The data
15,550 records of deaths during police encounters, 2013–2026, compiled by Mapping Police Violence.
What this site does
Displays them as per-agency death counts, together with the Fatal Encounters records (see below), attributed to the compiler. They are excluded from every download on this site.
Why

mappingpoliceviolence.us states: “No part of this site, Mapping Police Violence, may be reproduced in whole or in part in any manner without the permission of the copyright owner.” This site’s records hold no permission document from the copyright owner. That is a gap in provenance, and it is stated here as one.

The site’s current wording is left in place while the written scope is confirmed; Source inventory says the same. Older wording describing this data as used “under written permission” remains in /downloads, /llms.txt, /llms-full.txt and the agency API, and in two internal files: a comment in the query layer and the extraction script for this data. Those were not revised when the other pages were, and they are listed here so the difference is visible.

Texas racial-profiling filings (TCOLE)

The data
5,490 filing records for 2,752 Texas departments, report years 2024–2025, from the Texas Commission on Law Enforcement: which department filed, in which year, under which of TCOLE’s two options (Full or Exempt, TCOLE’s own words), and when.
What this site does
Publishes it, credited to TCOLE, with a visible note that re-use terms are not verified. This was decided by the owner; it is not a clearance. “Exempt” is printed as TCOLE’s word and is never described as a failure to file.
Why

No licence, no public-domain dedication and no re-use statement was found on TCOLE’s racial-profiling page, its website policies, its privacy and security policy, its link policy or its public-information page, and the workbooks carry no rights metadata. The only rights statement on the site is a footer: “Copyright © 2023 Texas Commission on Law Enforcement”. A copyright notice asserts ownership; it grants nothing.

TCOLE publishes the workbooks for download, for the public, with no stated condition. That is publication, not a licence. As of 12 October 2026 TCOLE had not been asked what re-use it permits. The evidence is in data/licences/tcole-racial-profiling-2026-10-12.md.

FBI hate crime: a count only where the file has one

The data
277,135 incidents, 1991–2025, from the FBI Crime Data Explorer bulk file, naming 11,231 ORIs, loaded 12 October 2026.
What this site does
Shows a count for an agency-year only where the file lists incidents for it. Never a zero, and never a rate.
Why

Absence is not zero and cannot be made into zero. The FBI’s per-agency API answers HTTP 200 with every count 0 for an ORI that does not exist (probed with ZZ9999999), so an API zero is not evidence that an agency reported none. Nothing this site holds distinguishes “reported zero” from “did not report”.

The file is silent on most of the register. In 2025, 3,058 of the 19,645 agencies in the register have at least one incident in it and 16,587 have none. Across every agency in the register and every year in the file, 617,524 of 687,575 agency-years (89.8%) are silent. A silent agency-year may be zero incidents, non-reporting or non-participation; the data cannot say which, so no page says any of them.

The FBI contradicts itself on hate crime

The data
The same agency-years, read from the FBI’s bulk file and from its per-agency API, give different counts.
What this site does
Publishes the bulk-file figure, with the date of the file (loaded here 12 October 2026; the file’s own last-modified date is 14 August 2026).
Why

New York City Police Department, 2023: 612 in the bulk file, 624 in the API. 2024: 657 in the bulk file, 648 in the API. Two smaller agencies differ as well: Fort Lauderdale 2023 (14 in the bulk file, 6 in the API) and Manchester, New Hampshire 2025 (3 and 2). The bulk figures are read from this site’s stored rows; the API figures are from probes made on 12 October 2026, and the API is not stored.

The stored rows match the bulk file row for row, so this is not a parsing error here. The API reports a last refresh of 15 September 2026 and the bulk file was last modified 14 August 2026, which is consistent with the two routes carrying different revisions. That is a hypothesis; it is unproven. These four were found in a sample of agency-years, not a full comparison, so others may exist.

Deaths are not a like-for-like series

The data
Deaths during police encounters come from two sources whose years only partly overlap: Fatal Encounters alone in 2000–2012, both in 2013–2021, and Mapping Police Violence alone in 2022–2026.
What this site does
Counts each death once. 9,091 Fatal Encounters records are excluded as duplicates of Mapping Police Violence records; they are kept in the database, flagged. The matching rule is on Source inventory.
Why
The source doing the recording changes at those boundaries. Counts across them are not comparable, and a difference between a year on one side and a year on the other is not a measurement of change.

Held, and not published

California POST certification actions, per agency

The data
722 peace-officer certification actions in 338 buckets, from California POST, aggregated before storage.
What this site does
Publishes a statewide total only, on California certification. No count appears on any department’s page.
Why

POST’s own footnote says: “Last Employing Agency” is not necessarily the reporting agency or the agency where the serious misconduct occurred. A count on a department’s page would assert what the publisher disclaims.

POST also states that it “is aware that there are issues affecting the accuracy of a peace officer’s certification status as listed on this page”, and the endpoint is not deterministic: one officer alternated between MADERA CO SO and MADERA CO DA across 12 identical requests.

Names

The data
Two kinds. The name of each person who died is stored in one column, deaths.victim_name. California POST’s source is a list of named officers.
What this site does
The victim name exists solely as the key that matches the same death across sources. No page query selects it. The site stores none of the officers’ names.
Why
Printing a name is a product decision that has not been taken. The claim is checked rather than asserted: scripts/gate-no-name-leak.sh scans the served HTML of the agencies with the most deaths on record for a real victim name and tests its own detector, and the California POST load searches its buckets, stored rows and run note for officer names and rolls back on any hit.

227 columns of the TCOLE workbooks

The data
The TCOLE workbook has 243 columns (read 12 October 2026). Six are loaded: year, filing status, submission date, department name, department number and total stops. The 227 columns after total stops are per-stop breakdowns by sex and race or ethnicity, reasons for stops, searches, contraband, arrests, use of force and complaints.
What this site does
Does not load them. The other ten columns are also not loaded: the chief administrator’s name, county, region, zip code, a TCOLE analysis flag and five columns with no label.
Why
Demographic breakdowns beside enforcement counts imply comparisons this site will not make. The restraint is enforced: scripts/gate-tcole-filings.sh asserts against the live database that the table has exactly its permitted columns and that no label from those 227 columns exists anywhere in it. The value of what is loaded is whether a department filed what Texas law requires of it, not what the filing says.

Deliberately never acquired

Washington Post fatal-force data

The data
The Washington Post’s database of fatal police shootings.
What this site does
Not downloaded, not used.
Why
It is licensed CC BY-NC-SA. NonCommercial makes it unusable here, and ShareAlike would extend the same licence to the database derived from it.

FBI estimated crimes

The data
The FBI’s estimated_crimes_*.csv files.
What this site does
Not downloaded, not used.
Why
They are the FBI’s imputations, filling in for agencies that did not report. Publishing them would paper over the exact non-reporting this site exists to expose.

Census ACS demographics on agency pages

The data
American Community Survey population and demographic estimates for the places agencies serve.
What this site does
Not shown on agency pages.
Why
Per-capita figures use the population the agency itself reports for, not an ACS population. And demographic context beside death counts implies comparisons this site refuses to make.

Police Scorecard (Campaign Zero)

The data
Scores assigned to police departments.
What this site does
Not acquired, not reproduced.
Why
A score is an editorial characterisation of an agency. This site reproduces what a source records and does not characterise it.

The datasets this site does publish, with their live row counts, are on Source inventory; how they are collected is on Method & sources.