Effective November 15, 2026
PowCall ("we," "us") provides snow forecast data for ski resorts at powcall.com and in the Snow Stake app for iPhone and Android. This page explains what information we collect, why, and the choices you have. We collect the minimum needed to run the product and never sell your data. If you use the app, §5 is the part about it.
| Data | When | Why |
|---|---|---|
| Email address | You sign up for a powder alert | To send the alert you requested (forecast-triggered snowfall notifications for a resort you pick) |
| Email opens and link clicks | You open one of our emails, or click a link in it | To see whether alerts are delivered and read (recorded by our email provider, Resend; see §2) |
| Usage & device analytics | Automatically, while browsing the site | Understand which resorts/features get used, fix bugs, improve the product (via PostHog, see §3) |
| IP address | Automatically, on every request | Standard web server/hosting logs; basic abuse and rate-limit protection |
| Requests from ChatGPT or Claude | You use PowCall inside one of these AI assistants | To answer the request, limit request rates, and count usage in aggregate (see §4) |
| A push token, your alert choices, and a record of the alerts sent | You turn on the evening call in the Snow Stake app | To send the notifications you asked for and check that they arrive (see §5) |
| Crash and error reports | The Snow Stake app crashes or hits an error | To find and fix bugs (sent to Sentry; see §5) |
We do not require an account, password, or payment information to use PowCall. We do not store your location beyond the resort(s) you choose to follow (§4 covers the approximate location hint ChatGPT may send, which we don't store).
When you subscribe to a powder alert, we store your email address and the resort/threshold you selected. Every subscription requires email verification before alerts start. Every alert email includes a one-click unsubscribe link that immediately and permanently deletes your subscription — your address and every resort it follows — no login needed. To see or remove single resorts, ask for a manage link on the Powder Alerts page: we email it to you, so only someone who can read your inbox can see or change your alerts. We never use your alert email for marketing without separate, explicit opt-in.
Our emails (alerts, verification and manage links) are sent through Resend (§6), which tracks opens and clicks. Each email contains a tiny invisible image; when your mail app loads it, Resend records that the email was opened. Each link in an email, including the unsubscribe and manage links, first goes to Resend's servers, which record the click and then send you on to powcall.com. Like any web request, these carry your IP address and browser or device details. This shows us whether alerts arrive and get read; we don't use it for advertising. Turning off automatic image loading in your mail app stops open tracking; a click is recorded whenever you use a link in one of our emails.
On the forecast dashboard we use PostHog to understand product usage (page views, time on page, and specific feature interactions such as viewing a resort or comparing resorts). We configure PostHog to keep its identifier in your browser's local storage, not in cookies. PowCall itself sets no cookies. Like any web request, PostHog receives your IP address and browser details. This data is used in aggregate to improve the product and is not used to individually target you with ads — PowCall does not run advertising.
The dashboard also saves your favorites, compare list and filter in your browser's local storage, and whether you dismissed the storm banner in its session storage (cleared when you close the tab). These stay on your device and are not sent to us. Clearing your browser's site data for powcall.com removes all of them, including PostHog's identifier.
PowCall is available as a plugin in ChatGPT and as a connector in Claude. When you ask one of these assistants about ski-resort snow, it may call PowCall's tools. Those requests come from the assistant provider's servers (OpenAI's or Anthropic's), not from your device. Your conversation is handled by the assistant's provider under its own privacy policy. PowCall never receives your prompts or the rest of the conversation, and we send back only the forecast results you asked for.
What we receive with each request:
What we store:
| Data | How long | Why |
|---|---|---|
| Daily call counts, per UTC day, by assistant (ChatGPT, Claude or other), tool, resort and outcome (for example "answered" or "resort not covered"). The resort is recorded only if it is one PowCall covers; otherwise it is left empty. | Kept indefinitely; they contain no identifiers | Aggregate usage: how many people use PowCall in assistants and which resorts they ask about |
| A keyed hash (HMAC, made with a secret key) of ChatGPT's user ID and of its conversation ID, per UTC day and assistant. This hash is a pseudonymous identifier: we keep it instead of ChatGPT's ID. | 90 days; a daily job deletes older rows | Counting how many different users and conversations used PowCall each day |
| Daily counts of visits to powcall.com through PowCall's short links, per UTC day, by source (such as ChatGPT or Claude), campaign tag and resort | Kept indefinitely; they contain no identifiers | Aggregate usage |
| Daily capacity figures: the busiest minute's number of calls, and how many calls were turned away because the service was at its overall limit | Kept indefinitely; they contain no identifiers | Knowing when we need more capacity |
| Short-lived rate-limit counters: one keyed on a hash of ChatGPT's user ID, and one keyed on the IP address the request came from (for tool calls, the assistant provider's server) | About a minute, in memory; never written to our database | Rate limiting, so no single user or source can exhaust the service for everyone |
What we don't store: your prompts or conversation; tool inputs other than the name of a resort PowCall covers; your location or the location hint; your locale; the user agents (app or browser hints) ChatGPT sends about your device; IP addresses, beyond the minute-long rate-limit counter and our hosting provider's request logs; or the raw user and conversation IDs. Those request logs (§6) record each request's time, the tool called, and the name, version and IP address of the assistant software that made it, which is the assistant provider's server, not your device.
Purposes: answering the request; rate limiting, to protect the service from abuse; and aggregate usage counts (how many people use PowCall in assistants, which resorts they ask about, and whether we need more capacity). We don't use this data for advertising or profiling, and we don't combine it with other data about you.
Recipients: none. We don't share or sell this data. It is stored with our hosting provider (Render, §6), like the rest of PowCall's data.
Your controls: you can disconnect or uninstall PowCall in ChatGPT or Claude at any time; PowCall then receives nothing more from you. Hashed IDs are deleted automatically after 90 days. We have no way to tell which hash belongs to you (we can't look one up by your name, email or account), so we can't find or delete one individually on request. Questions: andrew@powcall.com.
If you follow a link from a PowCall card to powcall.com, that visit is an
ordinary website visit and the rest of this policy applies to it. The link
carries tags (such as utm_source=chatgpt) so our analytics can
count visits that came from an assistant.
Snow Stake is PowCall's app for iPhone and Android. It has no accounts and no sign-in, and it never asks for your name, email address or phone number. It does not ask for your location and we do not work one out from your IP address. It shows no ads and contains no advertising or analytics software. Your saved mountains, your settings and the last forecast the app loaded are kept on your phone.
What the app sends, and what we keep:
| When | What is sent | What we keep |
|---|---|---|
| You open or refresh the app, or one of its widgets updates | A request for the forecast and recent snowfall of the mountains you saved (up to 12), and for the list of mountains | Nothing. Our server answers the request and writes no record of which mountains a phone asked for. |
| You turn on the evening call (the app's optional notification) | The phone's push token (the address Apple or Google gives the app so notifications can reach it), whether it is an iPhone or an Android phone, the app version, and the language setting your phone sends with the request | One record for the phone: a random ID we assign, the push token, the app version, the language, a scrambled copy (a hash) of a secret key the app uses to show that later requests come from the same phone, and the dates the record was created, last used and confirmed |
| You choose mountains and an amount for the evening call | Up to 12 mountains, the amount (3, 6 or 12 inches) and how many days ahead to alert for | Those choices, with the phone's record |
| We send the phone an alert | Our server sends the alert's text and the push token to Apple or Google, which deliver it | A record of each alert: its text, the mountain and morning it was about, when it was sent, and whether Apple or Google accepted it |
| The phone receives an alert, or you tap one | A receipt: which alert, when it arrived, and whether you tapped it | The receipt, on that alert's record. We use receipts to check that alerts arrive, and we count how many are opened. |
| After you turn on the evening call, and again when the phone's push token changes or needs confirming | We send one silent test notification; the app answers with the one-time code it carried, which shows that this phone really holds the token | A hash of the token and a hash of the code, with no phone ID |
| The app crashes or hits an error | An error report, sent to Sentry (see below) | Nothing on our own servers |
IP addresses. Like any server, ours sees the IP address each request comes from. We use it to limit request rates, with short-lived counters: about a minute for ordinary requests, up to an hour for turning on the evening call, and a daily count of new sign-ups for the evening call per network, which expires within two days. Some log lines record an IP address: when a request is refused for going over a rate limit, and a few security lines about push tokens (for example, when two phones name the same token), which also record the phone's random ID and a shortened hash of the token. Our hosting provider keeps those logs for about 7 days. We do not use IP addresses to work out where you are.
Who delivers alerts. Alerts reach an iPhone through the Apple Push Notification service and an Android phone through Google's Firebase Cloud Messaging. To deliver one, our server sends them the alert's text and the phone's push token. They handle it under their own privacy policies.
Crash and error reports. The versions of the app we release send an error report to Sentry when the app crashes or hits an error. A report holds the error (what went wrong, and where in the app's code), the app version, and facts about the phone such as its model and operating system version. Before a report leaves the phone, the app removes the user, request and IP address fields, and removes push tokens, IDs, secret keys and the query part of web addresses. The app sends no screenshots, no screen recordings and no record of what you tapped. Like any server, Sentry's sees the IP address a report comes from. Reports are not tied to the phone's alert record.
How long we keep it:
| Data | How long |
|---|---|
| The phone's record and its evening-call choices | Until you delete it with Delete my data (below). Otherwise it is deleted automatically: 7 days after it was created, if the phone never confirmed its push token; 30 days after its token last changed, if the phone confirmed an earlier token but never the new one; and 90 days after the record stops being valid, which is usually because Apple or Google told us the token no longer works (for example, when we try to send to a phone the app was removed from). A phone that has confirmed its current token keeps its record, so alerts still work next season. |
| Alert records and receipts | 180 days, or until you delete your data if that is sooner |
| Test-notification records (hashes only, no phone ID) | Up to 8 days: the code works for 24 hours, and the record is deleted 7 days after that |
| A note that Apple or Google reported a token as no longer working (the token's hash and a time, no phone ID) | 180 days; longer only while a phone's record still depends on it |
| Alert totals: how many alerts were due, sent and confirmed in each region each evening and morning | Kept indefinitely; they contain no identifiers |
| Crash and error reports | Held by Sentry and deleted on its retention schedule |
Delete my data. In the app, open Settings and, under Your data, tap Delete my data. The app first asks our server to delete the phone's record: its push token, the hash of its secret key, the app version and language, your evening-call choices, and every alert record and receipt for the phone. Our server deletes them at once. Only when the server has confirmed, or has no record of the phone, does the app erase what it saved on the phone: your saved mountains, your settings and the saved forecast. If the server cannot be reached, nothing is deleted and the app says so, so you can try again. This works whether or not the evening call is on.
What is left afterwards: the test-notification and dead-token records in the table above (hashes only, no phone ID), the alert totals (no identifiers), and any log lines that mention the phone's random ID, until our hosting provider deletes them (about 7 days). Crash and error reports are not tied to the phone's record, so we cannot pick out the ones from your phone; Sentry deletes them on its schedule.
Turning the evening call off stops the alerts but keeps the phone's record. Uninstalling the app does not delete the record either: it stays until the rules in the table above remove it. To remove it straight away, use Delete my data before you uninstall. If you have already uninstalled, we cannot tell which record was your phone's, because it holds no name, email or account.
Purposes and sharing: we use this data to send the alerts you asked for, to check that they arrive and see how many are opened, to protect the service from abuse, and to fix bugs. We do not use it for advertising or tracking, we do not sell it, and we do not combine it with other data about you: email alerts you set up on powcall.com are stored separately, with nothing that connects them to a phone. The only recipients are the service providers named here and in §6. Help with the app: powcall.com/support.
Services we share data with to run PowCall and Snow Stake:
| Service | Purpose | Data involved |
|---|---|---|
| Resend | Delivers our emails and tracks opens and link clicks (§2) | Your email address, email content, when you open an email or click its links, and the IP address and browser details those requests carry |
| PostHog | Product analytics | Usage events, device/browser metadata, IP address |
| Render | Application hosting | Server request logs, IP addresses, the data described in §4 and §5 |
| Cloudflare | Network in front of powcall.com: every request from a browser, the Snow Stake app or an AI assistant passes through it on the way to our server | IP addresses and the requests themselves, in transit |
| Apple (Apple Push Notification service) | Delivers the Snow Stake app's alerts to iPhones (§5) | The alert's text and the phone's push token |
| Google (Firebase Cloud Messaging) | Delivers the Snow Stake app's alerts to Android phones (§5) | The alert's text and the phone's push token |
| Sentry | Receives the Snow Stake app's crash and error reports (§5) | The error, the app version, the phone's model and operating system version, and the IP address the report comes from |
Services your browser contacts directly when you use powcall.com. Each one receives your IP address and browser details, as any web request does:
| Service | When | Why |
|---|---|---|
| Google Fonts (fonts.googleapis.com, fonts.gstatic.com) | Most PowCall pages | Loads the site's fonts |
| unpkg (unpkg.com) | The forecast dashboard | Loads the Leaflet map library |
| Esri (server.arcgisonline.com) | When you open a map on the dashboard | Loads map tiles for the area you view |
| PostHog (us.i.posthog.com, us-assets.i.posthog.com) | The forecast dashboard | Product analytics (§3) |
We do not sell, rent, or trade your personal information to anyone, for any purpose. Weather/snowfall data itself (station observations, forecast models) comes from public sources (NOAA, USDA NRCS) and is not personal data.
Alert subscriptions are kept until you unsubscribe, remove them with a manage link, or ask us to delete them. Analytics events are retained per PostHog's standard retention window, and email open and click records per Resend's. Data from ChatGPT and Claude requests is kept as described in §4: hashed IDs for 90 days, aggregate counts with no identifiers indefinitely. Data from the Snow Stake app is kept as described in §5. You can request deletion of your data at any time — see §9.
Wherever you are located, you can:
If you're in the EU/UK (GDPR) or California (CCPA/CPRA), these rights apply to you explicitly by law; we honor the same requests for every visitor regardless of location.
Help with PowCall (the website, alerts, or PowCall in ChatGPT and Claude) or the Snow Stake app, questions, data requests, or deletion requests: andrew@powcall.com. We aim to respond within 30 days. Answers to common questions about the app are on the Support page.
PowCall and the Snow Stake app are not directed at children under 13, and we do not knowingly collect data from them.
If this policy changes materially, we'll update the effective date above and, for material changes affecting alert subscribers, note it in the next alert email.