Legal
This Privacy Policy explains how CrimeScore (operated by OopsLab LLC, "we", "us") handles information collected from customers of the CrimeScore API and visitors to crimescore.io and any embed widget served from our domain.
Area Watch data. When you explicitly choose “Watch this area,” we store your email address, the selected county, ZIP Code Tabulation Area, Census block group, or address, the page or map surface where you submitted it, a representative latitude and longitude, and any optional reason you provide. County and ZIP page actions use that page's published geographic center, while a map-tooltip action uses the point selected on the map. These non-address representative coordinates are rounded to three decimal places, and merely moving or zooming the map is not stored. Exact-address watches are verified again through Amazon Location Service and may store the matched address and its coordinates and ZIP; the county FIPS and block-group GEOID come from CrimeScore's own Census boundary files. Watches saved before this change may instead hold an address verified through the US Census geocoder. A public Watch submission is not linked to an existing CrimeScore account merely because its email matches. We link it only after that email is confirmed for a new account or the signed-in account explicitly watches the area. Ordinary map and address searches are not persisted as Area Watches unless you submit the Watch form.
Account information. When you register, we collect your email address, hashed password (via AWS Cognito), the organization name you create, and any team-member email addresses you invite.
Billing information. Payments are processed by Stripe. We never see or store full card numbers. We store the Stripe customer ID, subscription status, plan tier, billing-cycle dates, and the email address associated with the Stripe customer record.
API usage data. When your API key is used to call the CrimeScore API, we record the request count, endpoint, response code, timestamp, and request/response metadata needed for quota enforcement, abuse prevention, debugging, and billing. For score requests this may include the returned geographic identifier (for example, a Census block group GEOID). For recent-incident requests this may include the requested coordinates, radius, hour window, and returned result count. We do not store the originating IP address of end users beyond what is required for short-term abuse detection and rate limiting.
Dashboard activity. For signed-in users, we record dashboard page visits and selected map areas, including the geographic identifier, score component, time, and interaction count, linked to the account and organization. These records help our administrators understand product use and troubleshoot problems. We schedule these activity records to expire after 90 days. Ordinary map selections do not consume paid API requests. This activity record does not include typed addresses, exact click coordinates, or movements such as panning, zooming, or hovering.
Embed widget telemetry. When the CrimeScore embed widget is loaded on a third-party site, we record the publishable key used, the origin domain, the timestamp, and an aggregate load count. We do not set tracking cookies on end users of the embedding site.
Email lifecycle data. We process your email address, marketing subscription status, optional first name, account activation stage, and email delivery or engagement events to send account onboarding, product lifecycle, and subscribed marketing messages. We never include API keys or other authentication secrets in lifecycle email data.
Website and product analytics. Google Analytics and PostHog process page URLs, referring domains, campaign parameters such as UTM source, medium, and campaign, and a limited set of product-funnel events. Authenticated product activity may be associated with an internal account identifier so we can understand registration, activation, and subscription outcomes. We do not place email addresses, organization names, API keys, requested locations, or other personal information in campaign URL parameters or Google Analytics events.
Advertising attribution. When a CrimeScore visit includes a Google Ads click identifier (GCLID, GBRAID, or WBRAID), we may retain the first valid identifier for up to 90 days in your browser together with associated UTM parameters, the landing-page path, and the capture time. If you create or access an account during that period, we associate that first-touch record with your account until account deletion. We also create limited conversion records for events such as account creation, API activation, demo requests, trial starts, and the first paid subscription invoice.
Recent incident data. CrimeScore may collect and store normalized recent public or third-party incident activity for the 24-hour incident API and public activity-pulse visuals. We store only product-safe normalized fields such as a stable incident ID, sanitized label/category, approximate coordinates, timestamps, severity/rank signals, and aggregate cluster counts.
Operational logs. Standard server logs (request paths, status codes, error traces) are retained for up to 30 days for security and reliability purposes.
Voluntary product feedback. Signed-in dashboard users can provide survey answers and optional written feedback linked to their account. We use these responses to understand use cases, identify obstacles, and improve CrimeScore. Categorical survey events may be recorded in our existing product analytics; optional written feedback is excluded from those events and session recordings. Product feedback is separate from Area Watch configuration and email preferences.
Through the CrimeScore API, we do not collect end-user demographic information, personally identifying information about end users of your platform, or their browsing history. The API processes the location information described above. This is separate from information collected by advertising services on our public website, described below.
For recent incident features, we do not expose or store raw upstream payloads for customer use, media URLs, livestream details, user/comment data, radio clips, or raw update text in public feeds or customer API responses.
The CrimeScore model uses aggregate public government demographic, economic, and geographic data together with public reported-crime records.
We use explicitly submitted Area Watch details to save the areas you choose, understand demand and optional feedback, and support future area updates. This feature does not currently send incident alerts.
To operate the CrimeScore API and dashboard, send transactional emails (invitations, billing notifications, security alerts), provide account onboarding and product lifecycle messages, send marketing messages when subscribed, enforce quotas and abuse policies, attribute advertising outcomes, measure acquisition and product activation, improve product performance, and respond to support inquiries. We do not sell personal information for money or use dashboard and embed activity to serve third-party advertising. Advertising on our public website may involve sharing that is considered a “sale,” “sharing,” or “targeted advertising” under applicable state privacy laws; see Advertising and privacy choices below.
We use the following third-party services to operate the product:
Each subprocessor receives only the data strictly necessary to perform its function.
When advertising is enabled on our public map, ZIP, and county pages, Google AdSense and other third-party advertising vendors may use cookies, local storage, IP addresses, browser and device information, and interactions with ads to deliver and measure advertising, limit repeated ads, and prevent fraud. These services are separate from our Google Ads conversion attribution.
Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites. Google's advertising cookies enable Google and its partners to serve personalized ads based on visits to our site and other sites on the Internet. Other advertising networks may also use cookies and similar technologies. Learn more about how Google uses information from partner sites and Google's advertising technology providers.
Manage personalized ads. You can opt out of Google's personalized advertising through Google Ads Settings. You can also visit the Digital Advertising Alliance's opt-out tool to manage participating advertising companies' interest-based ads. These choices do not remove all advertising and may apply only to the browser or account where you make them.
Site-specific choices. On our public map and location pages, the footer's “Privacy choices” link reopens Google's European consent message when it is available for your location. The “Do not sell or share my personal information” link opens Google's U.S. opt-out dialog when it is available. Confirm your choice in Google's message; following a link alone does not record an opt-out. Google manages the resulting advertising consent or opt-out signals.
If Google's controls are unavailable, those links lead to this section. You can use the advertising settings linked above or contact support@crimescore.io with a privacy request. Browser settings can also restrict or delete cookies; deleting them may clear saved choices. Advertising preferences do not delete your CrimeScore account, change email subscriptions, or control all website and product analytics.
The CrimeScore API is intended as one input among many in legitimate location-risk-intelligence workflows. As stated in our published model card, the following uses are explicitly out of scope and not licensed:
Account-linked survey responses are retained while the account exists and removed during account deletion. You can also ask support@crimescore.io to remove survey content separately; a minimal opt-out record may be retained to prevent further invitations. Analytics records follow our separate analytics retention and deletion process.
Area Watch records are retained while the watch is active or until you delete the linked account or ask support to remove an accountless watch. Short-lived feedback tokens expire after 15 minutes. Public submission rate-limit records contain only a SHA-256 digest of the source IP address and expire automatically after their short abuse-prevention window. During account deletion, similarly digested email and profile identifiers are held as purge-coordination fences without the underlying email or account identifier. They remain held if login deletion must be retried and are removed after that deletion succeeds.
To remove Area Watch data submitted without an account, contact support@crimescore.io.
Account-linked Google Ads attribution is retained while the account remains active and is removed when account deletion completes. Limited Google Ads conversion rows expire after 120 days and are also removed during account deletion when associated with that account. Billing records are retained for 7 years to satisfy tax-record obligations. Operational logs are retained for up to 30 days. Aggregated, non-identifying analytics may be retained indefinitely for model and product improvement.
Google Ads conversion exports contain click identifiers, event names and times, deterministic order identifiers, and subscription revenue and currency when applicable. They do not contain email addresses, internal user IDs, UTM parameters, or landing paths. CrimeScore does not use hashed-email matching for this process.
If you are a customer, you can access, correct, export, or delete your account data at any time via the dashboard. To request deletion of your Stripe customer record and associated billing history, contact support@crimescore.io.
If you are an EU/UK resident, you have additional rights under GDPR/UK-GDPR including the right to lodge a complaint with your supervisory authority. If you are a California resident, you have rights under the CCPA/CPRA. We honor verifiable requests under both regimes.
All traffic is served over HTTPS. Passwords are hashed by AWS Cognito. API keys use a SHA-256 hash for authentication lookup, and newly created key values are retained in encrypted private database records so an authenticated organization owner or administrator can reveal and copy them later. Database access is limited to least-privileged service roles. Ongoing security review is the responsibility of the engineering team.
CrimeScore is a B2B product not directed at children under 13. We do not knowingly collect information from children.
We will post material changes to this policy on this page and update the "Last updated" date above. For significant changes affecting how we use information, we will notify account holders by email.
Questions about this policy? Email support@crimescore.io.