Nationwide neighborhood safety. Search any U.S. city, neighborhood, or zip · (805) 900-0032
→ FOR HOAs · REALTORS · BROKERS — live neighborhood preview + full-report unlock ($149-$499/mo)

Our data sources

Every published statistic links back to the public dataset it came from, with the date it was last refreshed. Nothing prints without provenance.

Find a Safe Place runs on named, public datasets — all national-scale. Crime data comes from FBI UCR + NIBRS (nationally-comparable classifications covering every US law-enforcement agency that reports) plus the city police open-data portals we ingest for daily-fresh incident records. School data from every state Department of Education and the federal Civil Rights Data Collection. Demographics from the U.S. Census ACS. Pedestrian crashes from state DOT crash APIs. The pedestrian network from OpenStreetMap. Offender locations from the national registry. Every stat carries its refresh date and its source city/state.

Where does your crime data come from?

Two sources, combined: federal (FBI UCR and the NIBRS API) for nationally-comparable classifications covering every U.S. law-enforcement agency that reports, and city police open-data portals (ArcGIS / Socrata) for daily-fresh incident records at the block level. Where the two disagree on counts, we cite both and show the source by stat. New cities are added weekly — call in a request for yours at (805) 900-0032.

All datasets we ingest

Each row: the dataset, who publishes it, what we use it for, how often it refreshes, and when we last refreshed our copy.

Dataset Used for Cadence Last refresh
FBI UCR + NIBRS APIFederal Bureau of Investigation Nationally-comparable crime classifications + counts Federal monthly 2026-06-29
City police open dataCity police open-data portals via ArcGIS / Socrata · new cities added weekly Block-level incident records; repeat-address concentration Daily 2026-06-29
U.S. Census ACSU.S. Census Bureau · American Community Survey Population denominator, housing tenure, demographics Annual 2026-06-29
State Depts of Education school report cardsEach state Department of Education School quality grades, enrollment, performance Annual (school-year release) 2026-06-29
Federal CRDCU.S. Dept of Education · Civil Rights Data Collection School-based arrests + restraint, chronic absenteeism Federal biennial 2026-06-29
State DOT pedestrian-crash datasetsEach state Department of Transportation Pedestrian crash incidents along walk-to-school routes Annual 2026-06-29
OpenStreetMapOpenStreetMap contributors Pedestrian network, sidewalk coverage, signalized vs unsignalized crossings Daily tile pull 2026-06-29
National sex-offender registryU.S. Dept of Justice · NSOPW Offender distance to address, geocoded Federal rolling 2026-06-29

How fresh is the data?

Crime data refreshes daily where the city police open-data portal permits — our ingest pipeline pulls every morning from every ArcGIS / Socrata portal we cover. New cities are added weekly as their portals come online. Census ACS and state Department of Education report cards refresh annually on their official release schedules. The federal CRDC refreshes on a biennial federal cadence. OpenStreetMap tiles pull daily. Every neighborhood page shows the last-refreshed date per stat, not a blanket “as of” stamp.

How we treat the data

Public data arrives messy. The work is making it comparable.

Geocoding

Every incident, school, and crash record is geocoded to lat/lon and reverse-resolved to a neighborhood polygon so the map shows the right block, not a centroid.

Normalization

50+ feed schemas across every state and city we cover. Local police codes don't match FBI NIBRS codes don't match state DOT crash codes. Every new city we onboard requires normalizing their code system into our single internal taxonomy before we publish.

Deduplication

The same incident can appear in two feeds (PD + FBI). We dedupe by date + lat/lon + classification so a single event isn't counted twice.

What data do you NOT use?

We refuse a few categories on purpose. They aren't oversights — they're choices.

What we don't ingest

  • No social media. Nextdoor posts and Twitter chatter aren't public-safety signals.
  • No anonymous reviews. Rumor without provenance doesn't go on the page.
  • No paid data. If we have to pay a broker for it, we don't want it — the whole point is sourced, public data.
  • No predictive scores. We publish what already happened. We don't model who might offend.
  • No "safety score" from a third-party black box. If we can't show the formula, we don't publish the number.

Frequently asked

Can I get the raw data?
Yes — every dataset above is public. The table links to the publisher. We don't republish the raw feeds because the publishers already do.
What about HOA or partner data?
If we ever ingest a private dataset, we'll list it on this page with the same provenance fields and the access terms. As of 2026-06-29 we ingest zero private data.
What if a stat looks wrong?
Call (805) 900-0032 or email hello@findasafeplace.com. We'd rather correct a number than defend it.
Last updated: 2026-06-29 · Phone (805) 900-0032