Privacy
This privacy policy explains how Crime Data API handles personal information associated with its service. Email is optional when creating a free API key and is used for key recovery and notices. Read the policy below for details about collected information, processing, retention and requests to the operator about your data.
Last updated: 2026-11-04
Controller: Shahar Frish, Israel. Contact shaharfrish6@gmail.com. We do not sell personal data or use it for advertising.
| Data | Purpose and lawful basis (where GDPR applies) | Retention and recipients |
|---|---|---|
| Key hash, usage counts; optional key email | Provide keys and quota accounting: contract (Art. 6(1)(b)). Recovery and service notices: legitimate interests (Art. 6(1)(f)). You may add an email; it is optional and used only for recovery and service notices. | While the key is active or needed for recovery; request deletion by email. Stored in our database; email is not returned by the API. |
| City requests: city, optional email and free text | Prioritize coverage and reply: legitimate interests in responding to requests. | Purged after 180 days by the nightly job. Avoid sending sensitive personal information. |
| Hashed IP and rate-limit counters | Prevent abuse and keep the service available: legitimate interests. | Expired buckets purged after two days by the nightly job. A hash is pseudonymous, not anonymous. |
| Page path, referrer hostname and daily counts | Understand site traffic: legitimate interests in improving documentation. | Aggregated daily in our database; no automatic retention limit is currently set. No analytics cookies. |
| Address queries, matched address and coordinates | Geocode requested locations: contract; caching for reliability: legitimate interests. | Sent to US Census Geocoder; successful matches cached for 90 days, failed matches for seven days. Expired entries are unused and purged nightly. Email the address for earlier deletion. |
Hosting: Vercel; database: Supabase (US). Billing is handled by Lemon Squeezy or RapidAPI; we receive billing identifiers and plan status, not card details. Infrastructure providers may process request paths and errors to operate and secure the service; their retention and international-transfer terms also apply. Address queries are disclosed to US Census in the US. Contact us for applicable transfer safeguards and provider details.
Public police data can still carry identification risk. Coarsening reduces identification risk; it does not guarantee anonymity.
Your rights: what should you know?
Where applicable, you may request access, correction, erasure, restriction or portability, object to processing based on legitimate interests, and withdraw any consent without affecting earlier lawful processing. Email shaharfrish6@gmail.com with the relevant key ID, address or request details; do not send your secret key. We may ask for proportionate identity verification. We respond within one month; if a lawful extension is necessary, we explain it within that month.
You can complain to your local data-protection supervisory authority, including in the EEA country where you live, work or believe an infringement occurred, or to Israel's Privacy Protection Authority. You do not have to contact us first. See the EEA authority directory and Israel Privacy Protection Authority.
Data comes from each city's open-data portal under the licence shown. It is police-reported incident data, not convictions, and can be revised by the source. Compared with the FBI API · Terms · Refunds · Privacy · DPA · Contact
Operated by Shahar Frish, Israel.
What should I know about this data?
Where does the incident data come from?
Incident data comes from city open-data portals under the licence shown for each city. It is police-reported data, not convictions, and sources can revise it.
Where can I check coverage and freshness?
The city coverage pages and GET /v1/cities identify covered cities, source licences and newest record dates.
Do scores predict personal risk?
No. Scores describe incident density within a city, are not comparable across cities and do not predict personal risk.
Where can I find related information?
Crime API reference · Incident density methodology · MCP setup for AI agents