Privacy Policy

Last updated: October 2026

WetBulbTracker LLC, a Missouri limited liability company ("WetBulbTracker", "we", "us"), is the controller of personal information collected through WetBulbTracker.com.

This Privacy Policy explains what information WetBulbTracker.com (the "Service") collects, how it is used, and the choices you have. By using the Service, you agree to the practices described here. We aim to collect as little as possible.

1. Information you provide

• Account information. If you create an account, we collect your email address. If you sign in with Google, we receive the basic profile information Google shares for sign-in (such as your email address and name). We do not receive or store your Google password. If you choose a password for your account, it goes from your device straight to our authentication provider (Supabase), which stores it only as a salted hash. We never see your password or store it in readable form. If you sign in with Apple, we receive the email address Apple shares, or a private relay address if you choose to hide yours. On our website, Apple can also share the name you give in its sign-in screen the first time you sign in there.
• Saved locations and preferences. If you save places or change settings (such as units or theme), we store those so they sync across your devices.
• Personalization profile (optional). If you use the "Your risk" feature, the heat-risk factors you choose are stored to tailor your personal-risk read. These may include a broad, optional self-report of health sensitivities (such as a heart or respiratory condition, pregnancy, or medication use). You choose whether to provide any of this; it is stored on your device and synced to your account only if you sign in; it is used solely to personalize your heat-risk read; it is never sold or used for advertising; and you can change or clear it at any time. We ask before collecting any of it. The first time you open the personalization controls you are told what the data is for and asked to agree; nothing is collected until you do, and the date of your agreement is recorded. You can withdraw at any time from the same place; withdrawing deletes the profile from this device and from your account, not just the agreement. Signing out is not withdrawing: it removes the profile and the date of your agreement from that device, and your account keeps both.
• Heat alerts (optional). If you turn on alerts for a saved place, your browser creates a push subscription for that device and we store it against your account so we can deliver the notification. In the WetBulbTracker app for iPhone, iPad or Android, the phone's notification token from Apple or Google takes the place of the browser's push subscription. It is stored the same way and for the same purpose, and it is removed when you sign out of the app. It is a delivery address for that browser, not a tracking identifier: we do not use it to build a profile, and it is deleted when you sign out of that device or delete your account. You can also remove a device from your account's device list; a device that is still signed in adds itself again the next time it opens WetBulbTracker. Alert rules also record the threshold you chose and when we last notified you, so we do not send the same warning twice. If you turn on For my personal risk, the alert also stores one number worked out from your personalization profile, never the answers behind it. It follows your profile when you change it. While your consent stands, it never goes below a small margin of 0.1 °C, even when your profile adds nothing, so that it keeps following your profile. It is cleared, back to zero, if you withdraw consent.
• Communications. If you email us, we keep your message and contact details to respond.
• Widget health details. In the Android app, Copy details on the Widget health screen copies the app's and Android's versions, the widget's last refresh attempts with their times, and its settings, never your location or places. Nothing is sent unless you paste them into a message to us. If you do, we keep them with your message to respond, and their times can be matched with our hosting provider's standard request logs (§2, Technical logs), which can include the coordinates the widget asked about.

2. Information collected automatically

• Location you look up. When you search for or tap a location, those coordinates are sent to our servers and to our weather data providers (see §4) to return conditions for that point.
• Device location (optional). Your device's location is used only with your permission. In a browser, your browser asks when you use the location button ("Locate me"), or when the site opens with no place to show, and if you allow it, shares your device's location with the Service. In the WetBulbTracker app for iPhone, iPad or Android, the app asks only after you tap the location button or the widget's own request to allow location, and your device's own prompt asks for your precise location; on iPhone, iPad and Android 12 or later, the same prompt lets you choose approximate location instead. (Versions of the Android app before 2.0 open the site in Chrome, which asks as a browser does.) Either way, the location is used to show conditions where you are and to center the map there, and it is handled like a location you look up (above). On an Apple Watch or a Wear OS watch, the WetBulbTracker watch app shows the reading where the watch is, so it asks for the watch's own location when you first open it, and when you tap its own request to allow location; §3 says how it uses that location. You can decline, and you can revoke this permission in your browser or your device's settings at any time.
• Approximate location from your connection. If the site or app opens with no place to show and no location from your device, it picks the place to open on from the approximate city, region, country and coordinates that our hosting provider (Vercel) works out from your connection's IP address, and the country also sets °F or °C until you choose a unit yourself. In the app, this happens even if you have allowed location, because the app asks your device where you are only when you tap the location button or the widget's own request. That place is then handled like a location you look up (above); our servers do not keep your IP address or that estimate for this, though the request, like any other, can appear in our hosting provider's standard request logs (see Technical logs, below).
• Usage and analytics. We use Vercel Web Analytics to understand aggregate usage (such as page views, general region, device and browser type, and which features are used). It is cookieless, does not track you across other websites, and runs for every visitor. Google Analytics runs only for visitors outside the EU, EEA, UK and Switzerland. Where it runs it sets its own cookies; where it does not, no Google Analytics script is loaded at all. That decision is made on our server from the country your request arrives from, and anything we cannot determine is treated as inside that region. In every region, the location parameters in the address bar and the token in a shared-document link are stripped before any analytics provider sees the page address. Your personalization profile is never sent to analytics: not the values, not which fields you filled in, and not whether you set, changed or cleared it. This is enforced by an automated check in our source code, not only by policy.
• Technical logs. Our hosting and infrastructure providers process standard request data (such as IP address, user agent, the address requested and, for a request made while you are signed in, the account it comes from) to operate the Service and guard against abuse, including rate limiting.

3. Cookies and local storage

• Local storage. Your preferences (units, theme, selected metric, and the audience you last picked for activity guidance on the location card) are stored in your browser's local storage so the app remembers them. If you use personalization, your profile and the date of your agreement are kept there too, with the identifier of the account they belong to while you are signed in. The app also keeps two small notes there, by account identifier: whether a withdrawal still has to reach our servers, and whether it last set your personalized alerts to the general reading. It keeps the place you are viewing as well: for as long as that tab (or the app) stays open, so that coming back within 30 minutes returns you to it, and as a copy rounded to about 1 km that goes with your searches to our servers, for up to 30 days after you last viewed a place, so that nearby places come first. That includes a place picked from your connection (§2). Clearing your browser data removes them.
• The app's widget and offline screen. In the WetBulbTracker app for iPhone, iPad or Android, the app keeps the last place you chose, your saved places, your unit and the latest readings in storage that only the app and its widget can read, on your device, whether or not you add a widget, so that the widget (and, on iPhone and iPad, the offline screen) can show them, and so that the app opens where you left off. On a device used on or before October 21, 2026, that place can be one picked from your connection (§2) until you choose one. Deleting your account in the app clears your places and readings from that device. Deleting it any other way (on our website, by email, or from another device) cannot reach that storage; removing the app clears it. The widget asks our servers for a reading by coordinates only, with no account information. The widget shows the reading where you are. It finds your location on your device, rounded to about 100 meters, asks our servers for a reading by those coordinates in the same way, and asks your device's own map service (Apple's or Google's) for the place's name. We do not store them. Like any request, they can appear in our hosting provider's standard request logs, which are kept for a limited period (see §2, Technical logs, and §6). A widget you add also keeps its own last readings and location (rounded, with the place's name); deleting your account does not clear them, but removing the widget does (on iPhone and iPad, when the app next opens).
• The Android widget's refresh record. From version 2.3.1 of the Android app, a widget you add also keeps a record of its last few refresh attempts on your device: when each was and how it went, as fixed words and numbers, with no location. The app's Widget health screen shows it, and none of it reaches us unless you copy the details and send them to us (§1). Deleting your account does not clear it, but removing the widget does.
• The watch app. If you use WetBulbTracker on an Apple Watch or a Wear OS watch, it shows the reading where the watch is, or, without a current location, the last place you chose. It finds the watch's location on the watch, rounded to about 100 meters, and asks the watch's own map service (Apple's or Google's) for the place's name. It asks our servers for a reading by coordinates only, the watch's or the last place's, with no account information. We do not store them. Like any request, they can appear in our hosting provider's standard request logs, which are kept for a limited period (see §2, Technical logs, and §6). The watch keeps its last location, rounded, with the place's name, what the phone passes it and its latest readings in storage on the watch that only WetBulbTracker can read, and it never sends its location to your phone. The phone app passes only the last place you chose and your unit to your watch, never your account or your personalization profile, through Apple's or Google's own phone-to-watch connection; for a Wear OS watch this can pass through Google's servers, encrypted so that only our app on your devices can read it.
• Authentication. If you sign in, our authentication provider (Supabase) stores a session token in your browser so you stay signed in.
• Analytics cookies, outside the EU/EEA/UK and Switzerland only. Our Vercel analytics is cookieless everywhere. Google Analytics, which does set its own cookies, is loaded only for visitors outside those regions, and never for anyone who has opted out of analytics. We run no advertising or tracking pixels anywhere. Apart from Google Analytics where it applies, the only cookie this site sets is the sign-in session above, and only if you choose to sign in. You can block or delete cookies in your browser settings; signing in will not work without the session cookie.

4. Third-party services

We rely on reputable third parties to operate the Service. Anthropic and Resend process data for us under data processing agreements and must protect it as this policy describes; the other services below receive only what each one's entry says.

• Weather and map data: Open-Meteo, ERA5 reanalysis, the U.S. National Weather Service, and RainViewer. We send Open-Meteo the coordinates you look up to retrieve conditions (ERA5 history reaches us through Open-Meteo), and ask RainViewer for the radar map tile that covers them, to check for rain there; we do not send these providers your identity. The National Weather Service never receives the places you look up: we request its published WBGT only for a fixed list of U.S. cities, to check our accuracy.
• Place names: Open-Meteo and BigDataCloud. The text you type in search goes to Open-Meteo's place search, to find matching places. BigDataCloud turns a point into a place name. It receives the point of any place you look up, whether you tapped the map, picked a search result or let the app find where you are, and the point behind the AI brief on a place's card, a paw check or a city page, or behind a report that includes Sports. We send each of them only that text or that coordinate: no identity, no account reference.
• Map tiles: CARTO, which serves the map background. Your browser requests tiles from them directly, so they see your IP address and which part of the map you are looking at, the way any image on any website is fetched. If CARTO stops serving our map, or we switch providers, your browser loads the map background (its tiles, fonts and icons) from OpenFreeMap instead, at tiles.openfreemap.org, delivered through Cloudflare. OpenFreeMap then sees the same things: your IP address and which part of the map you are looking at. Otherwise your browser contacts OpenFreeMap only to check that it is working before switching to it: when CARTO fails to load the map in your browser (and, while CARTO keeps failing, at most once a minute), or when we switch providers. Each check carries your IP address but no map area. With radar on, your browser also loads RainViewer's radar images directly, in the same way.
• Hosting and analytics: Vercel (hosting, and cookieless Web Analytics), and Google Analytics for visitors outside the EU, EEA, UK and Switzerland who have not switched analytics off (see §2 and §3). Both analytics services record the page you were on, with the location parameters removed first: a page you open at a specific coordinate is counted as the page, never as the place. Google Analytics also sets its own cookies and receives the standard request data any website sees, such as your IP address and browser type. Neither analytics service is sent your name, your email, an account identifier or your personalization profile. As our host, Vercel also runs our servers, so what your browser or app sends us passes through it, with the request data described in §2 under Technical logs. It keeps its logs of those requests for a limited period (see §6), and for a limited time it keeps copies of some of what our servers fetch and send back, such as a place's conditions or a brief, so that a repeated request can be answered from the copy.
• Sign-in with Google: Google, only if you choose that sign-in method.
• Sign in with Apple. Apple, only if you choose that sign-in method, in our iPhone or iPad app or on our website. Apple shares your email address, or a private relay address if you choose to hide yours. In the app, we do not receive your name from Apple; on our website, Apple can also share the name you give in Apple's sign-in screen, the first time you sign in there. If you delete your account, you can also remove WetBulbTracker yourself in your Apple Account settings, under Sign in with Apple.
• Authentication and database: Supabase, which handles account sign-in and is our database and file storage. Your account and what belongs to it are kept there, including your saved places and preferences, a synced "Your risk" profile, your heat alerts and the devices they reach, report schedules, Studio items and an uploaded logo. It also keeps records of our own, such as the record of mail we sent and the do-not-email list (see §6). Like our host, Supabase processes the request data described in §2 under Technical logs.
• Payments: Stripe, if you subscribe or start to. Starting to subscribe creates a Stripe customer record holding your email address and our reference for your account. When you pay, Stripe also collects your name and billing address and keeps them on that customer record, using the address to work out tax. Card details go directly to Stripe and never reach our servers; we store only your Stripe customer and subscription references, and what your subscription entitles you to, with its status and dates.
• Plain-language briefs: Anthropic (Claude). When the app writes a short brief about your conditions, we send that location's place name (such as a city, state and country), never its coordinates, with its local date and time, the season there, and its current and forecast conditions. Nothing from your personalization profile is sent for any brief: not your answers, and not the personal heat-risk level or the factors worked out from them. We never send your name, your email, or any account identifier.

A brief for a report sends something different: no raw conditions and no place at all, neither the name you gave it nor its coordinates. We send only the dates the report covers (for a report on the site, with the season they fall in there), the audiences and exposure you chose, and the report's computed figures, and the brief calls the place "this location". This applies to reports you build on the site, to Studio documents, and to reports emailed to you on a schedule.

Anthropic processes this data for us under a data processing agreement, may not use it to train its models, and deletes it within 30 days, longer only if it is flagged for misuse or the law requires it.

• Email delivery: Resend, for mail we send you: the sign-in, confirmation and account-security messages, billing messages (purchase confirmations, payment notices, renewal reminders and notice of any price change), and any scheduled report you asked for, including its AI-written summary. We send your email address, the message itself, and the place labels and figures inside it. It also carries the notices we send ourselves when a payment needs a person to look at it, which can name your Stripe customer and subscription references. Heat alerts do not go through this: they are browser push notifications and reach your device without an email provider.
• Notification delivery in the apps. Apple Push Notification service (iPhone and iPad) and Firebase Cloud Messaging from Google (Android) receive the device's notification token and each heat alert's title and text, to deliver it. Unlike alerts in a browser, which are encrypted so that only your browser can read them, Apple and Google can read these. So they name the place and the time, and the heat level only for alerts that do not use your personal profile. They never include anything from your profile, and never your coordinates.
• Your organization's logo (Pro): if you upload a logo for Studio documents, the image file is stored with our database provider, Supabase, in private storage readable only by your account, and appears on the documents you produce. On its way there it passes through our host, and it goes to no other third party. Removing it deletes the file.
• Address lookup (Studio): the U.S. Census Bureau geocoder, if you look up a street address for a Studio site. The address is sent from our servers, not your browser. We do not keep the address you type, though the request that carries it can appear, like any request, in our hosting provider's standard request logs, which are kept for a limited period (see §2, Technical logs, and §6). The matched address, or the one you pick when there are several, fills in the site's name, which you can change before saving. The name you save is kept with the site, like any Studio item, and is what the site is called in your Studio documents. A document you file keeps that name even if you later rename or remove the site, and a link you share to it shows the name to anyone who opens the link. If a document includes an AI brief, the brief is written without the name (see Plain-language briefs above).

We do not sell your personal information.

5. How we use information

We use the information above to:

• Provide and personalize the Service (return conditions for your locations, sync your saved places and settings, and, if you opt in, tailor your personal heat-risk read, "Your risk");
• Operate, secure, and improve the Service (analytics, debugging, abuse prevention); and
• Communicate with you when you contact us.

When we look up an account to answer a support request or to keep the Service secure, our support page shows the account's email address and how it signs in; when it was created, last signed in and confirmed its address; its plan and billing status; whether our email to it is being delivered; what kinds of devices receive its heat alerts and when they were last alerted; how many saved places and Studio items it has, and whether Studio branding is set; each heat alert's settings (whether it is on, the scale and level it warns at, its quiet hours and how far ahead it looks) and when it last sent an alert; and how many scheduled reports it has and how many are on, when the last one was sent and the next is due, and whether any is paused and why. That page does not show your personalization profile, where your saved places are, or your logo. Each time that page opens an account, we record that we looked it up and when.

6. Data retention

We keep account information and saved data for as long as your account is active. Deleting your account removes all of it at once (see §8 and Delete your account). What the app and your browser keep on your own device is in §3.

A few things outlive the account, and we would rather name them than let you discover them. Our payment processor retains invoice and payment records for as long as tax and accounting law requires a business to keep them. If you started to subscribe but never paid, there are no such records, and the customer record at our payment processor is deleted with your account. Analytics and technical logs are retained for a limited period under our providers' standard settings; neither is used to identify you. Copies our host keeps of some of our responses, such as a brief or a report (see §4), last up to a day or so, or up to about eight days for a report or reading that covers only hours already past. Anthropic deletes what we send it to write a brief (see §4) within 30 days, longer only if it is flagged for misuse or the law requires it. We also keep our own copy of each brief the AI writes, so that we can review what it says and answer a report about one. In that copy the place name we gave the AI, and any contact details our checks find, are replaced, and it holds no account, no coordinates and no network address. We keep it for 30 days, or 90 days if our automatic checks flagged it, and longer only while a report about it is open. Notices from our email provider about what happened to a message we sent, such as whether it was delivered, bounced or marked as spam, are kept for 30 days and then deleted. Email addresses are removed from them when they arrive. If we ever changed what your account can do, such as turning research access on or off, or looked your account up to answer a support request, the record of it is kept for 24 months, with the link to your account removed when the account is deleted.

Report links outlive the account as well. A link you make with Share, and the link in each scheduled report email, keeps the report's place, the name shown for it, its dates and its settings, and the plan of the account that made it, so that the link keeps working for anyone who has it until you ask us to remove it (see Delete your account). If you named a place after a person, that name is in the link. A link holds no email address and nothing that ties it to your account; one you shared also keeps a one-way hash of the network address it was most recently shared from, used only to limit abuse.

One more thing can outlive the account: your email address. If mail to you ever bounced, or you marked our mail as spam, that address stays on a do-not-email list. It is kept so that we cannot start mailing you again by mistake (it stops mail rather than enabling any), and it is the address on its own, not linked to an account that no longer exists. Ask us and we will remove it. Nothing else about you survives: the record of what we sent you outlives the account, but your address is removed from it when the account goes. The exception is older mail from before we began linking each message to its account, which may still show the address it went to; ask us and we will remove it.

7. Aggregated and de-identified data

We may compute and retain aggregated or de-identified information, for example comparisons between our heat-stress estimates and the National Weather Service's own published WBGT (itself a model), or statistics about how closely the two agree, to check, improve, and develop the Service and its underlying methods. This information does not identify you and is not personal information.

8. Your choices and rights

• Delete your account yourself. Sign in, open Account, choose Delete my account, type DELETE in the box, then press Yes, delete everything. It is immediate and irreversible, it cancels any Plus or Pro subscription, and it removes your profile, saved locations, alert rules and push subscriptions. Full detail, including what we are required to keep, is on Delete your account.
• Delete only part of it. You can remove a saved location, delete a heat alert, or clear your personal profile, including health sensitivities, without deleting your account.
• Download a copy. Export your data from Account at any time.
• If you cannot sign in. Email us from the account's own address and we will delete it for you.
• Location permission. You control device-location access through your browser's permission settings.
• Analytics. Our analytics is never linked to your account. Vercel Web Analytics is cookieless and aggregate everywhere; Google Analytics sets cookies and runs only outside the EU, EEA, UK and Switzerland (see §2). You can switch both off: open Settings and set Usage analytics to Off. That stops page counts and in-app events alike, from both. If your browser sends Global Privacy Control or Do Not Track, it is off already unless you turn it on.

Depending on where you live, you may have additional rights (such as under the GDPR or CCPA). We will honor applicable rights requests; contact us to exercise them.

9. Children's privacy

The Service is not directed to children under 13 (or the equivalent minimum age in your jurisdiction), and we do not knowingly collect their personal information. If you believe a child has provided us information, please contact us and we will delete it.

10. Security

We use industry-standard measures and reputable providers to protect your information. No method of transmission or storage is completely secure, however, and we cannot guarantee absolute security.

11. International users

The Service is operated from the United States and relies on providers that may process data in the United States and other countries. By using the Service, you understand your information may be processed in those locations.

12. Changes

We may update this Privacy Policy from time to time. Material changes will be reflected by updating the "Last updated" date above. Your continued use of the Service after changes take effect constitutes acceptance of the revised policy.

13. Contact

Questions or requests about this Privacy Policy? Contact us at info@wetbulbtracker.com.