Florida officer records are live — search the officer testifying against your client, free. Search free →
SKIP TO MAIN CONTENT
BENCHRECON
Trust and data handling

What you can verify before you trust a figure.

You are about to put a number in front of a judge. You should be able to trace it to the record it came from. This page states, plainly, where the data comes from, why every figure is checkable against a primary public source, how your own information is handled, and the honest limits of what we do. There are no security badges to collect here and none are claimed. What follows is the real posture.

Where the data comes from

Every product is built on public records from the bodies that keep them. Nothing is scraped from a paywall and nothing is invented.

  • Federal sentencing figures draw from the U.S. Sentencing Commission's public individual-case datafiles at ussc.gov.
  • Officer-record data draws from state peace-officer certification and discipline bodies (for example the Florida Department of Law Enforcement / CJSTC), NYC CCRB civilian-complaint history via NYC Open Data, and other state POST records obtained under each state's public-records act.
  • Court and docket sources, where used, are the free public corpora: CourtListener and RECAP (free.law) and the FJC Integrated Database.

The full source list, the citation convention, the refresh cadence, and the exclusions are documented on the methodology page.

Every figure is traceable to a primary source

This is the point of the product. In the federal briefs, every factual claim that derives from a specific record is labeled with the exact USSC datafile vintage it came from, and that datafile is publicly downloadable, so any figure can be reproduced by downloading the same file and running the same cell filter. In the state-court products, every rendered officer-record row cites the underlying public record, and every jury-instruction line links to the source authority behind it. Each brief's footer reports a source-citation count; the minimum standard is one citation per substantive factual claim.

We ship zero generated legal argument and use no large language model to synthesize analysis. The reason is on the record: documented AI-hallucination incidents in court filings have drawn real sanctions. A BenchRecon brief is an aggregation of cited public records, not a machine-written argument. If any citation in a brief is broken or does not resolve to its cited record, tell us within 7 days and we will correct the brief or refund the purchase (see the refund policy).

Freshness is live, not asserted

We do not ask you to take our word for how current the data is. The data-status page reports the real last-refresh date and per-source ingestion status, recomputed on each read from the underlying tables. If a source has gone stale past its refresh window, that page shows it, and new federal briefs built on data older than 30 days are routed to refund-pending rather than charged.

How your own information is handled

We collect the minimum needed to deliver what you buy. At checkout that is your email; for attorney-tier orders it also includes the firm name, bar number and state, and the use certifications you enter, recorded with a timestamp and IP as an auditable certification record.

  • Payments run through Stripe. We do not collect or store full payment-card numbers on our own systems.
  • Email delivery runs through Brevo; the database and file storage run on Supabase; hosting runs on Vercel. These providers process data on our behalf and are not authorized to use it for their own purposes.
  • The site is served over HTTPS with a strict Content-Security-Policy (nonce-based, no inline-script execution), enforced in middleware on every request.
  • We do not sell the buyer information you provide at checkout or on a waitlist. The one category of information we furnish to buyers is the officer public-record data that IS the product, and we disclose that posture plainly.

The complete collection, use, disclosure, and rights notice, including how to make a privacy request, lives on the privacy page.

Honest limits

A trust page that only lists strengths is a sales page. Here is what we do not claim:

  • We hold no third-party security certification. We do not claim SOC 2, ISO 27001, or a completed external penetration test, because none has been performed. When one is, it will be named here with its date, not before.
  • A BenchRecon brief is a research exhibit, not legal advice, not a finding about any person, and not a consumer report. Your judgment as licensed counsel governs whether and how it enters the record.
  • Officer-record sources are certification and public-complaint records, not internal-affairs files, and coverage varies by state. Where coverage is thin, we flag it rather than fill it in.
  • Public datasets carry their own denominator and vintage caveats. Those caveats are stated on each product and on the methodology page rather than smoothed over.

Questions or a report

If you find a citation that does not resolve, a figure you cannot reproduce, or a data-handling question, email [email protected]. We would rather hear it from you than have it surface in a courtroom.