Last updated: 2026-09-30
Privacy Policy
Zeus AI is a working tool for roofing contractors. This page describes exactly what we collect, why we collect it, and who we share it with. Plain language — no dark patterns.
Who we are
Zeus AI is a product of Zeus Weather LLC, based in Tulsa, Oklahoma. We build storm-targeting and field-canvassing software for independent contractors. If you have questions about this policy or want to request a copy or deletion of your data, email joe@zeusweatherllc.com.
What we collect
Account information
When you sign up, we store your name, email address, a hashed password, and — if you provide them — your company name and an optional phone number. Manager accounts also store the U.S. counties you’ve licensed and a list of the sales reps you’ve added under your account.
Chat history
Conversations with the Zeus assistant — the prompts you send and the responses you receive — are stored against your account so you can return to them and so we can debug issues. We don’t use your conversations to train third-party models, and we don’t sell them.
Canvassing data
If you use the mobile app to canvass, we record:
- GPS coordinates of your phone while a canvassing session is active, sampled periodically to draw your path on the map.
- Barometric pressure from your phone’s sensor (used to detect roof climbs).
- Door-knock dispositions you file (address, outcome, photos, notes).
- Photos you upload of damage, signed contracts, or other job artifacts. These are stored on DigitalOcean Spaces and tied to the relevant property and your account.
Location and barometer access can be revoked at any time in your phone’s settings. Doing so disables the auto-detection features but does not delete data you’ve already filed.
Property and storm data
The properties, parcels, and storm history we show you are sourced from public and licensed datasets (NOAA, ATTOM, public county records). We attach your activity (knocks, notes, dispositions) to those records inside your account, but we don’t publish your data back into them.
Device and usage information
We log basic technical information — device identifier (used to enforce one mobile and one web session per user), browser type, IP address, timestamps, and which pages or endpoints you used. This is operational telemetry — we use it to troubleshoot and prevent account sharing. We don’t build advertising profiles from it; the one ad-related use is that, if you sign up after clicking one of our ads, your IP address and browser user-agent are sent to Meta to help match the conversion (see “Advertising & cookies”).
How we use it
- To deliver the product — answer your questions, show storm maps, route plans, log dispositions, send the morning digest you asked for.
- To support you — investigate bugs you report, recover lost data, and respond to your emails.
- To bill you — your subscription is tied to your account and the counties you’ve licensed.
- To improve the product — we look at aggregate usage (which features get used, where errors happen) to decide what to build next.
We do not sell your data. We never share your canvassing routes or chat history with advertisers, and we don’t use them for any purpose outside the four items above. The one exception is advertising measurement: when you sign up after clicking one of our ads, we send Meta a hashed (irreversible) copy of your email, name, and phone so Meta can tell us the ad worked. See “Advertising & cookies” below.
Who we share data with
Running a modern web app means routing data through a small number of third-party services. Each one only sees what it needs to do its job:
Anthropic
Powers the Zeus assistant. Your chat prompts and the responses are sent to Anthropic’s API. Per their data-use terms, Anthropic does not train on API inputs.
OpenAI
Used for ancillary tasks (voice transcription, certain summary rewrites). Subject to the same no-training-on-inputs commitment for API traffic.
Google Maps Platform
Renders maps, geocodes addresses, and provides autocomplete for address entry. Google receives address lookups and map viewport requests; it does not receive your chat history or canvassing data.
Mailgun
Sends emails on our behalf (login alerts, support replies, the morning storm digest). They process recipient address and message body for delivery.
Expo Push Service
Delivers mobile push notifications. Push payloads (e.g. “New plan ready”) and your device push token transit through Expo.
DigitalOcean Spaces
S3-compatible object storage for photos you upload. Files are stored in private buckets; URLs are short-lived signed links.
Railway / Vercel
Cloud hosts for the backend API and the web app. All traffic to and from these services is encrypted in transit.
Stripe
Processes subscription payments. Card details are entered directly into Stripe’s form; we never see or store your card number. Stripe receives your email, name, and billing details for the charge.
Cloudflare Turnstile
Checks that a sign-up comes from a person, not a script. Cloudflare receives technical signals from your browser (such as IP address and browser characteristics) during that check.
Sentry
Alerts us when something breaks in the app or on our servers. Error reports carry the technical details of the failure, the page or feature involved, your browser and device type, and your account ID — not your name, email, IP address, chat messages, or canvassing data.
Meta (Facebook)
Measures the performance of our Facebook and Instagram ads via the Meta Pixel and the Meta Conversions API. When you arrive from an ad and sign up, we send Meta a hashed (SHA-256, irreversible) copy of your email, name, and phone, your IP address and browser user-agent, plus the Meta cookies described below, so Meta can attribute the conversion. Meta does not receive your chat history, canvassing data, or a readable copy of your contact details.
We may add or change vendors as the product evolves. Material changes will be reflected here and dated above.
Advertising & cookies
We advertise Zeus AI on Facebook and Instagram. To know which ads actually bring in signups, we use the Meta (Facebook) Pixel together with the Meta Conversions API. This lets us measure ad performance with or without browser cookies.
- Hashed personal information (email, phone, name) may be shared with Meta in a privacy-preserving (SHA-256 hashed) format. Meta cannot reverse the hash to read your details; it’s used only to match the signup to an ad click.
- IP address and browser user-agent are sent to Meta (as Meta requires, unhashed) solely to match the conversion to an ad click — not to build a profile.
- _fbp — a first-party Meta cookie identifying your browser for ad attribution.
- _fbc — a first-party Meta cookie storing the ad click id (from the
fbclidin the ad link).
You can opt out of this kind of ad measurement in your Facebook ad settings, and you can clear or block the _fbp/_fbc cookies in your browser at any time.
Data retention
We keep your account data for as long as your account is active. When you cancel, we keep records for up to 90 days to handle billing reconciliation and reactivation, then we delete or anonymize them. You can request earlier deletion at any time by emailing joe@zeusweatherllc.com.
Operational logs (technical errors, request metadata) age out on a rolling 90-day window.
Your rights
You can:
- See a copy of what we have on you.
- Correct anything that’s wrong.
- Delete your account and the data tied to it.
- Revoke device permissions (location, notifications, etc.) from your phone or browser at any time.
Send a request to joe@zeusweatherllc.com and we’ll respond within a reasonable timeframe — typically a business day or two.
Security
Passwords are salted and hashed; we never store them in plain text. All traffic to our backend is over HTTPS. Sessions are limited to one active web browser and one active mobile device per user; a new login signs the previous one out. Photo storage buckets are private, accessed via short-lived signed URLs.
No system is bullet-proof. If we ever detect a breach that affects you, we will notify you directly by email.
Children
Zeus AI is a B2B tool for roofing contractors. It isn’t directed at or intended for children under 13, and we don’t knowingly collect their data.
Changes to this policy
We’ll update this page when the underlying practices change. The “Last updated” date at the top reflects the most recent revision. Material changes (new vendors handling your data, expanded collection) will also be flagged inside the app on your next sign-in.
Contact
Questions, requests, or concerns: joe@zeusweatherllc.com.
Zeus Weather LLC · Tulsa, Oklahoma · United States