Trust & Compliance

Security at HailScore

How we host, encrypt, and access the data behind every HailScore. Where we are on the SOC 2 readiness path. Who our subprocessors are and what they're certified for. Companion document to the methodology white paper.

Last updated: November 12, 2026.

1. Data we collect & how we use it

HailScore collects these kinds of data:

  • Public records. NOAA, NWS and SPC records are US government works in the public domain. CoCoRaHS reports come from a volunteer network run by the Colorado Climate Center, which asks users to credit it. We also store public roofing-permit records (address, permit number, date and status) from the City and County of Denver, the City of Aurora and the City of Centennial. We ingest, index, and serve them. Detailed list in the methodology paper, §3.
  • Property lookup data. When someone looks up an address on the site, in the HailScore iPhone app, or in the HailScore widget on a contractor's website, we store the address and its coordinates, the score result, any roof inputs and the requester's IP address in the scores table. Site and app lookups also store the user-agent string and device type and, when sent, the page URL, referrer and campaign tags. When someone signed in on the website runs a lookup, we also record which account ran it, with the address and IP address. The scores table is the proprietary dataset that compounds with each lookup.
  • Lead capture data. When a homeowner unlocks the premium report, we store the name, email and optional phone number they enter. Unlocking on its own shares nothing with a contractor. An inspection request, made on that form or later, sends those details and the property address to one contractor, and the Privacy Policy lists what that contractor can record afterwards. The lead record (leads) also keeps the address, the score shown, the time and wording of any consent given, and the visitor's IP address, user agent, referrer and campaign tags. What the contractor records afterwards is stored in lead_outcomes.
  • Accounts and Pro tools. For accounts we store the email, the name if given, and a hashed password for accounts that set one; others sign in with emailed links or codes. Pro tools keep an activity log of lookups and other actions, usually with the address and, for lookups, the IP address, plus anything the user saves, such as watched addresses, notes and claim records (which can include an insured's name and claim number).
  • Home binder. A signed-in homeowner, on the website or in the iPhone app, can save homes (address, roof details, insurance carrier), log repairs (including cost and contractor name), and upload documents and photos. If a signed-in homeowner allows notifications in the iPhone app, we store the device's push token, device name, app identifier and app version so we can send storm alerts.
  • Storm alerts. When someone signs up for storm alerts by email, we store their email address and the address they want watched. Our sign-up form does not ask for a phone number, but older sign-ups may hold one, and the sign-up endpoint still stores one if a request includes it.
  • Orders. For a paid storm report we store the buyer's email and name, the address and date of loss, IP address, user agent and how they arrived. Card details are handled by Stripe.
  • Site analytics. Google Analytics and Microsoft Clarity (including session replays) record how the site is used unless the visitor declines in the cookie banner; see the Privacy Policy.
  • Records received from a contractor. A roofing contractor that works with HailScore supplied its own records of past roof inspections: customers' names, phone numbers, email addresses and property addresses and, where it recorded them, inspection results, insurance company and claim details, and roof install dates. They are stored in leads and lead_outcomes in that contractor's account, used to test and calibrate the score, and never sold.

We do not ask for Social Security numbers, bank or card numbers, government ID numbers, or biometric data. Card payments go through Stripe's hosted checkout or Apple in-app purchase, so card numbers do not reach our servers. Files a homeowner uploads to the home binder are stored as uploaded and may contain whatever the homeowner puts in them. We do not buy, sell, or rent personal data to third-party data brokers.

Uploaded files are not behind sign-in. Photos uploaded to the AI roof inspection feature are stored in Vercel Blob before the analysis runs. When the analysis succeeds, each photo is linked to the lead record; if it fails or its result cannot be saved, the photos stay stored at their public links with no database record linking them to the lead. They are stored at public links: anyone who has, or can work out, a photo's link can open it, and the links do not expire. The photos and the property address are sent to Anthropic for analysis. Home binder documents and photos are also stored at public Vercel Blob links that do not expire; each link is built from a random ID for the home, the upload time and the file's name, and anyone who has one can open the file. Binder files are not sent to contractors.

2. Hosting & infrastructure

The HailScore application is hosted on Vercel with deployment from a private GitHub repository. The application runs on Vercel's global edge network with primary compute in US regions. The database is Neon PostgreSQL 17 with the PostGIS 3.5 spatial extension, hosted in AWS us-east-1.

Production secrets (database connection strings, third-party API keys, cron-trigger tokens) are kept in Vercel's encrypted environment variables, in GitHub Actions secrets, and in environment files on the operator's own computers, which run backup jobs. They are not in the current source tree or in any client-side bundle. Keys that are public by design, such as the Mapbox map token and analytics IDs, ship in the browser code.

Scheduled jobs (NWS alert polling, NOAA MRMS radar pulls, storm-alert sends, contractor digest emails) run as Vercel Cron jobs and on GitHub-hosted Linux runners, with backup copies of some jobs on the operator's own computer.

3. Encryption

All traffic to myhailscore.com and all API endpoints is served over HTTPS (TLS 1.2 or later). Our responses carry a Strict-Transport-Security header with a two-year max-age, so a browser that has visited over HTTPS keeps using HTTPS. Plain-HTTP requests are redirected to HTTPS.

The Neon PostgreSQL database encrypts all data at rest using AES-256 (managed by AWS KMS as part of Neon's storage layer). Database connections are encrypted with TLS.

Credentials are stored as one-way hashes, never in readable form:

  • User passwords: bcrypt, cost factor 12
  • API keys: SHA-256 (the raw key is shown once, when it is issued)
  • Sign-in links (magic links): SHA-256, single use, expiring after 15 minutes to 7 days depending on purpose
  • App sign-in codes: 6-digit codes stored as an HMAC-SHA256 keyed with a server secret, valid for 10 minutes and single use; a code stops working after 5 wrong tries
  • iPhone app session tokens: SHA-256, expiring after 60 days
  • Password-reset links: single-use hashed tokens, valid for one hour
  • Share-page links: SHA-256

Paid report download links and saved-home alert unsubscribe links are signed with a server-side secret (HMAC-SHA256) instead of being stored. Storm-alert subscription tokens are random values, one per alert subscription, stored in plaintext. A token can only confirm or cancel its own alert subscription and cannot sign anyone in.

4. Authentication & access control

Website sign-in uses NextAuth v5 with two providers:

  • Credentials — email + bcrypt-hashed password.
  • Magic link — one-time sign-in links. Lead notifications emailed to contractors stay valid for 48 hours, team and contractor invitations for 7 days, and website sign-in links for 30 minutes. The sign-in box sends one only to an account without a password; saving a home from a report sends one to the email address entered, creating a homeowner account if none exists, and that link also works for an existing account that has a password. Right after checkout, the confirmation page can show a sign-in link that works for 15 minutes. Tokens are stored as SHA-256 hashes, work once, and sign in only the account they were issued for, into that whole account, not just the linked page. Site administrators cannot sign in by link. Links in the weekly contractor digest don't sign anyone in; they open the sign-in page.

The HailScore iPhone app signs in with an emailed 6-digit code and receives a random session token, which we store only as a SHA-256 hash; it expires after 60 days and can be signed out per device. The HailScore Pro app signs in with an emailed code or the account password and receives an API key for that device, kept in the device keychain. Signing out revokes that device's key.

Website session tokens are JWT with secure-only and HTTP-only cookie attributes. Some public endpoints can be called from any website: the address lookup (also used by our embeddable widget), the embed lookup, the API specification and our open Colorado data files. The browser-extension score endpoint takes anonymous requests from browser extensions but refuses ordinary web pages. These endpoints return score, weather and specification data. We never send the Access-Control-Allow-Credentials header, so another website cannot read a response made with a visitor's sign-in cookie. The v1 data endpoints require an API key.

Scheduled-job endpoints require a shared secret. Payment (Stripe), email-delivery (Resend) and App Store webhooks are accepted only with a valid signature from the sender.

Production database access is limited to:

  • The Vercel-deployed application, through a restricted application role
  • Scheduled jobs on GitHub Actions (data ingestion, maintenance and email jobs), using a database credential stored as a GitHub secret, with wider write permissions than the application's role, including deleting rows
  • Backup ingestion and daily reporting jobs on the founder's computers
  • The HailScore founder (Alex Chicilo), from the founder's own computers (including scripts and developer tools run there), for operational queries, audits and migrations. Migrations run with the database owner credential.

Access is reviewed when team composition changes.

4.1  API key rotation

During the pilot, HailScore issues partner API keys; they are not self-serve. Separately, anyone can create a HailScore Pro app account with an email address, and signing in to the app creates a key for that device that works on the same v1 data endpoints during the app's free trial or on a paid plan. To rotate a partner key without downtime:

  1. Ask us for a new key. A new key works alongside your existing key until you revoke the old one. We keep only a hash of each key, so we cannot show a key again after issuing it.
  2. Update your integration to use the new key. Both keys authenticate during the overlap window.
  3. Revoke the old key at /dashboard/api-keys, or ask us to. A revoked key stops working on its next request.

Keys don't expire on their own. We recommend rotating production keys at least every 12 months, and immediately if a key may have been exposed. Send your key in the Authorization: Bearer header. A ?api_key= query parameter also works, but URLs are often logged, so a key sent that way is easier to expose.

We keep an internal usage log for each API key (the api_usage table), recording the endpoint, status code, response time and source IP of each successful request to the v1 data endpoints. We can send you an export of a key's usage log on request.

4.2  Source IP restrictions

API keys are not restricted by source IP address. A key works from any network until it is revoked, so keep keys on your servers and rotate any key that may have been exposed.

5. Subprocessors

The following subprocessors handle data on behalf of HailScore. Certifications are listed as each vendor publishes them; follow the vendor link for its current list. HailScore relies on these vendors' own certifications and has no SOC 2 report of its own yet (see §9).

VendorRoleRegionCertifications
VercelApplication hosting, edge network, scheduled jobs (Vercel Cron) and file storage (Vercel Blob)USSOC 2 Type II · ISO 27001
NeonPostgreSQL 17 + PostGIS managed databaseAWS us-east-1SOC 2 Type II · ISO 27001
GitHubSource control, CI, and scheduled jobs (GitHub Actions) that read and write the production database, including jobs that email homeowners and contractorsUSSOC 2 Type II · ISO 27001 · FedRAMP
MapboxAddress suggestions, geocoding, map tiles and static map imagesUSSOC 2 Type II
AnthropicClaude vision API for AI roof inspection (beta): the photos a homeowner uploads and the property addressUSSOC 2 Type II
ResendTransactional email deliveryUSSOC 2 Type II
StripePayment processing: hosted checkout for report purchases, contractor lead charges and Team/Firm subscriptionsUSPCI-DSS Level 1 · SOC 2 Type II
Google Analytics 4Site analytics: pages viewed and events, cookie identifiers and IP address. Street addresses, coordinates and reset or checkout codes are redacted from most page addresses it records. Off if you decline in the cookie banner.GlobalSee vendor link
Microsoft ClarityHeatmaps and session replays, with all page text masked. It does not record on the dashboard, admin, home binder, sign-in and account pages, or checkout-success pages. Off if you decline in the cookie banner.GlobalSee vendor link
AppleHailScore iPhone apps: App Store in-app subscriptions, maps and address suggestions, turning a device location into an address, and push notification delivery (device token and alert text, which can include a home's nickname)GlobalSee vendor link

To build a report, our servers send the property's coordinates, never a name, email or phone number, to public data services: the U.S. Geological Survey, the FCC, Open-Meteo, NASA POWER and the USDA Forest Service. They also send its county to FEMA. Median home values come from Census Bureau figures we keep in our own database. For the Colorado roof estimate, they also read public lidar and building-footprint files covering the property's area from open-data storage on Amazon Web Services. These are public-data lookups, not subprocessors.

The HailScore scoring algorithm itself is implemented in our own application code; no third-party scoring or modeling service is in the data path between a lookup request and the score returned to the user.

6. Backups, disaster recovery & data retention

The Neon database supports point-in-time recovery: we can restore the production database to any moment within the history window set on our Neon plan, currently the most recent 6 hours. Backups are stored encrypted at rest within Neon's managed infrastructure (AWS).

Source code and CI workflows are versioned in GitHub with full revision history. Production deployments are immutable Vercel deployments. A previous deployment can be restored from the Vercel dashboard, or a change can be reverted in git, which builds and deploys a new version.

Our scheduled ingest jobs add weather records and do not delete them; hand-run maintenance scripts can remove duplicate or bad weather rows. No application code deletes rows from the scores, leads or lead_outcomes tables, though rows can be updated (for example a lead's status, or a contractor's outcome notes). Hard-delete operations on those tables require explicit operator confirmation per internal policy.

6.1  Data retention

Most HailScore data has no automatic expiry. The table lists the main data stores and what, if anything, removes them:

Data storeRetentionNotes
scoresNo automatic deletionThe property-risk dataset. Rows hold the address and coordinates, the score and any roof inputs, and the requester's IP address; site and app lookups also keep the user-agent string, device type, page URL, referrer and campaign tags. Scored lookups' address, coordinates and the roof inputs used (no IP address) are also kept in score_shadow_comparisons to test changes to scoring, including v1 API, bulk and browser-extension lookups that never reach the scores table. Account deletion does not remove either.
leadsNo automatic deletionContact details, the consent record and visit details for each lead. When we remove a person's contact details on request, we keep the address, the score shown and the record of any consent given. A lead already assigned to a contractor stays on file with us and with that contractor.
lead_outcomesNo automatic deletionWhat a contractor records about a lead, or imported from a contractor's own records of past inspections: contact attempts and notes, inspection result, insurer, claim number, amount and deductible, photos and job details. Used to test and calibrate the score against real outcomes.
api_usageNo automatic deletionA row for each successful call to the v1 data API: key, endpoint, status, response time and the caller's IP address. Used for usage and trial metering and the admin usage view.
roof_photosNo automatic deletionPhotos uploaded for the AI roof inspection, with the address and the AI result. Files are stored at public Vercel Blob links: anyone who has, or can work out, a link can open the photo, and links do not expire. Photos from an upload whose analysis failed stay in Vercel Blob with no row in this table.
home binderUntil the homeowner deletes itSaved homes, repair log, documents and photos (saved_homes, home_repairs, home_documents, home_photos). Deleting a single document or photo also tries to delete the stored file; if that fails, the file can stay at its public link with no record pointing to it. Removing a whole home deletes its records but not yet its stored files.
ios_sessions,
device_tokens
No automatic deletioniPhone app sign-in sessions and push notification tokens. A session stops working after 60 days or when that device signs out. Storm alerts stop for a phone once its sign-out reaches us, except on current app versions while the same account is still signed in on another iPhone (the app identifies every iPhone only as “iPhone”).
users, pro_activity,
pro_lookups, adjuster_claims,
watched_addresses
No automatic deletionAccount details (email, name, and a password hash if one is set); a log of lookups run while signed in on the website (account, address and IP address) and of other Pro actions; and what Pro users save, including watched addresses and claim records with an insured's name and claim number.
storm_alert_subscribersNo automatic deletionEmail storm-alert sign-ups. Unsubscribing stops alerts but keeps the record, switched off.
storm_report_ordersNo automatic deletionKept as a purchase record, including after account deletion. The report PDF is emailed to the buyer and also stored privately, available through download links that expire.
magic_tokensExpires after 10 minutes to 7 days, by purposeOnly a hash of each sign-in link or code is stored, and it stops working at expiry or after use. Expired rows are not deleted automatically; a password reset deletes that account's reset links.
geocode_cache90 daysCached address-to-coordinates results, each keeping the resolved address and keyed by a one-way hash of what was typed; a daily job deletes rows older than 90 days.
application logsSet by each vendorVercel, Neon and GitHub Actions keep platform logs for their own retention periods, which vary by vendor and plan.

Homeowners can ask us to delete their lead details by emailing alex@myhailscore.com. The matching scores row is kept as part of the methodology dataset. It is not anonymized: it keeps the address, coordinates, roof inputs and score, plus the IP address and any user-agent string, page URL, referrer and campaign tags recorded at lookup.

7. Vulnerability management

  • CI runs npm audit for high-severity advisories in production dependencies on every push to main and every pull request. It reports advisories but does not block a merge.
  • The site's TypeScript code is type-checked in strict mode on every push to main and every pull request.
  • Many public endpoints have rate limits keyed by IP address, email, signed-in user or API key, plus input validation and file-type checks on uploads. Most limits are kept in each server instance's memory, so they slow bursts rather than enforce a global cap, and some signed-in endpoints have no limit yet.
  • The AI roof inspection endpoint also stops accepting photos for a lead once five are on record, pauses when an estimated 24-hour spend cap is reached, and allows three requests an hour per IP address on each server instance.
  • Schema changes are gated by review and applied only with explicit operator sign-off. Migrations against the scores table — the proprietary dataset — require a documented plan and reviewed SQL.

8. Incident response

In the event of a confirmed security incident:

  1. Containment. Affected credentials are rotated immediately. Compromised endpoints are disabled at the Vercel layer. Database access is restricted as needed.
  2. Assessment. Logs in Vercel, Neon, GitHub, and Resend are reviewed to determine scope, affected records, and timeline.
  3. Notification. Affected users are notified by email within the deadlines set by applicable state breach-notification laws. Carrier and contractor partners are notified by individual email.
  4. Remediation. Root cause is identified, fixed, and documented. A post-incident review is published internally with action items tracked to completion.

The operator reviews a daily operations digest, and the application emails the operator about failed report deliveries and some other operational failures.

9. Compliance roadmap

HailScore is honest about where it stands. As of November 12, 2026:

FrameworkStatusNotes
SOC 2 Type IReadinessControls documented on this page; formal audit engagement is gated to our first carrier/enterprise requirement
SOC 2 Type IIPlannedNo audit is booked; we would begin one after a first carrier contract
TCPA compliancePartialThe report-unlock and inspection-request forms (web and iOS) store the exact consent wording shown, a timestamp, the IP address and the user agent with each consented request. The realtor roof-certification request form does not record consent yet.
CCPA / state privacyActiveSee the privacy policy. Requests to know, delete or opt out are handled by email at alex@myhailscore.com.
GDPRNot targetedHailScore is built for US properties, and address lookup accepts US addresses only. Visitors outside the US are not blocked.

HailScore will pursue SOC 2 Type I when a partner or customer engagement requires it, and would begin a Type II audit after a first carrier contract. Until certificates are issued, we can answer a security questionnaire on request under NDA.

10. Enterprise procurement

For carrier, adjuster, and partner engagements, HailScore can provide on request under NDA:

  • Security questionnaire. Answers to your security questionnaire (for example CAIQ-Lite or SIG-Lite) and an architecture diagram, provided in your procurement format on request.

Procurement contact: alex@myhailscore.com.

11. Vulnerability disclosure & reporting

HailScore operates under a coordinated-disclosure policy. We welcome reports from security researchers, customers, and the public, and we extend safe-harbor treatment to good-faith reporters.

11.1  Scope

In-scope assets:

  • myhailscore.com and all subdomains
  • The public REST API at /v1/*
  • The contractor and admin dashboards
  • The HailScore Pro iPhone app and any other HailScore iPhone app we publish

Out of scope:

  • Third-party services we depend on (report directly to them — Vercel, Neon, Mapbox, etc.)
  • Denial-of-service or volumetric attacks; please do not perform load testing against production without prior written consent
  • Social-engineering of HailScore staff, contractors, or vendors
  • Duplicate reports of an issue we already know about

11.2  Safe harbor

HailScore will not pursue civil action or law-enforcement referral against researchers who, in good faith:

  • Act in accordance with this policy
  • Limit testing to the in-scope assets above
  • Avoid privacy violations, destruction of data, and interruption or degradation of services beyond what is strictly necessary to demonstrate a vulnerability
  • Provide a reasonable opportunity (typically 90 days) for HailScore to remediate before public disclosure
  • Do not exfiltrate, retain, or share customer or end-user data beyond the minimum needed to demonstrate impact

11.3  How to report

Security contact
alex@myhailscore.com
Subject line: [SECURITY] <short description>

Please include in your report:

  • A clear description of the vulnerability and the affected component
  • Reproduction steps, ideally with a minimal proof-of-concept
  • The impact you observed or believe is possible
  • Any tools or accounts used (so we can attribute and credit you, if desired)

11.4  Our commitments

  • Acknowledge receipt within one business day
  • Confirm triage outcome within five business days
  • Provide a remediation timeline appropriate to severity (typically 7 days for critical, 30 days for high, 90 days for medium)
  • Notify the reporter when the fix is deployed
  • Publicly credit the reporter by name (if desired) in a future revision of this page

HailScore does not currently operate a paid bug bounty. We are happy to discuss compensation for material findings on a case-by-case basis, particularly for vulnerabilities that would impact carrier or partner integrations.


Security, privacy, operational and product questions not answered here: alex@myhailscore.com.