GRIDPULSE Live map

Privacy

Privacy Policy

Effective October 13, 2026

GridPulse shows live stress on the US power grid, on the web at gridpulsemap.com and in the GridPulse app for iPhone, with its widgets, alerts and Live Activities. It is built to work with as little information about you as possible. This page explains exactly what that is.

The short version

  • No accounts. There is nothing to sign up for or log in to.
  • No ads, no tracking, no analytics. GridPulse has no advertising or analytics SDKs and no tracking pixels, and it sets no cookies.
  • Nothing sold or shared for advertising. We don't sell your information, share it for advertising or build profiles.
  • Locations are rounded first. A location is rounded to about 1 km on your device before it is sent anywhere. The server never logs it or writes it to disk. If you use alerts or Live Activities in the app, it keeps only each place's grid region and zone (and, while "Grid emergencies" or "Weather that can cut power" is on, its county), with the place's name and this iPhone's push tokens. If you turn on browser alerts, it keeps that browser's push subscription, the one grid you picked and when the browser last checked in.
  • Alerts are optional. Turning alerts off in the app or on the website deletes what the server kept for them.

Using the map, the dashboard and the app

To send you pages and live grid data, our server receives what any web server receives: your IP address and standard request details, such as the address requested and your browser or app version.

GridPulse's server does not keep access logs. When a request fails, it logs the method and path only, never the query string (which can hold a search), the body of the request, your IP address or a device token. A location is never part of a web address: the website and the app send it in the body of the request. A search's text does travel in the web address, so Render and Cloudflare, which carry the connection (see Services involved), can see it, and their own logs may include it.

To stop any one client from overloading the free public data sources GridPulse relies on, the server counts requests per IP address (for IPv6, per network block). These counters live only in the server's memory. They are never written to disk or to logs, and they are dropped as newer visitors replace them or when the server restarts.

The grid data itself (demand, capacity, prices, fuel mix, weather and hazards) comes from public feeds that our server fetches on its own schedule. Nothing about you is sent to those sources.

Your location and "your area"

Alerts (iPhone app, optional)

Alerts are off until you turn them on. When you do, the app sends GridPulse:

Each time the app registers (when you turn alerts on or change them, and when you open the app), and while "Grid emergencies" or "Weather that can cut power" is on, the server uses each place's rounded point to find the county it is in (a 5-digit county code used to match National Weather Service warnings to your places), and then discards the coordinates. With both off it keeps no county code. It stores the token, your place names, regions and zones, county codes while either of those is on, your settings, when you registered and when the app last checked in, and a short record of which alerts it last sent so it doesn't repeat them. To confirm that a new token works, it may send one silent notification that you won't see.

Notifications are delivered by Apple Push Notification service (APNs), which receives the token and the notification's text. Please don't use personal details, such as someone's full name, as a place name.

The registration is deleted:

Older copies can remain for a while in our host's automatic disk backups (see How long information is kept).

Live Activities (iPhone app, optional)

If you start a Live Activity for a grid, the app sends GridPulse that activity's push token, the grid region it follows, the name shown with it, whether it was started automatically and, if you have used alerts on this iPhone, its notification token, so the activity can be matched to your alert settings. When you start one, the name is the city of a saved place on that grid, or else the name you gave the place, if you have one. When GridPulse starts one for you (below), it is the name you gave the place, and APNs receives that name as well. The server uses these only to keep the activity up to date through APNs. It deletes them when GridPulse sees that the activity has ended or been dismissed (right away if the app is running, otherwise the next time it runs), and in any case about 8 hours after the activity starts, when iOS ends it.

If you turn on "Live Activity when my grid is High" in the Alerts screen, the app also sends a Live Activity start token, so the server can start one when a saved place's grid reaches High. The server keeps that token with your alert registration and uses it only while the option is on. Turning the option off deletes it, as does deleting the registration.

Browser alerts (website, optional)

Browser alerts are off until you turn them on for one grid with "Alert me". Your browser then asks your permission and creates a push subscription: an address at your browser's push service (Google for Chrome and most Android browsers, Mozilla for Firefox, Apple for Safari, Microsoft for Edge) plus keys that encrypt messages to it. GridPulse stores that subscription, the one grid region you picked, when you turned alerts on, when your browser last checked in, and a short record of which alerts it last sent and whether the push service accepted them, so it doesn't repeat them. Nothing else: no location, no name, no account and no settings. Every browser gets the same alerts: when the grid is very busy, or its operator warns that supply may be tight, asks people to save power or declares an emergency, and when the operator's notice ends, with quiet hours from 10 PM to 7 AM in the grid's time zone.

Messages are encrypted end to end, so the push service can't read them. It does see that your browser is subscribed to gridpulsemap.com, when messages arrive, their size and urgency, how long to keep trying to deliver them, and a coded label, unique to your browser, that lets a newer alert replace an unread one – never their content or which grid they are about.

The subscription is deleted when you turn browser alerts off on the website (if GridPulse can't be reached at that moment, the next time it tries to send an alert), when the push service says it no longer exists or keeps refusing messages, when your browser said it would expire, and at the latest 180 days after your browser last opened GridPulse with alerts on.

Sharing a region

Share creates a link such as gridpulsemap.com/r/ercot. It names the region only, never your location or anything about you.

Settings kept in your browser

The website remembers a few choices in your browser's local storage: whether the night lights are on (gp-lights), which map layers are on (gp-layers, gp-plants), whether the state lines are on (gp-states), the dashboard's light or dark theme (gp-theme), and which grid this browser gets alerts for and when it last checked in (gp-push). They stay in your browser, are never sent to GridPulse (browser alerts send their own subscription, as described under Browser alerts), and you can remove them by clearing this site's data in your browser. In a browser that can show notifications, opening a region on the map also installs GridPulse's small notification script (a service worker, /sw.js), so alerts can be turned on with one tap. It does nothing and sends nothing until you turn browser alerts on. GridPulse sets no cookies.

Services involved

What we don't do

How long information is kept

Request counters by IP
Memory only; dropped as newer visitors replace them or when the server restarts.
Place searches
Not kept. Each search is answered from GridPulse's own tables and is not cached, logged or written to disk.
Rounded-point lookups
Memory only. A result is reused for up to 24 hours; the entry stays in memory until newer lookups replace it or the server restarts. Weather-grid details for a roughly 10 km area may stay on disk up to 7 days, not linked to anyone.
Alert registration
Until you turn alerts off, 90 days after the app last checked in, or 30 days after Apple reports the token invalid.
Live Activity tokens
Until GridPulse sees the activity end or be dismissed, at most about 8 hours. The optional start token is kept until you turn that option off or your alert registration is deleted.
Browser push subscriptions
Until you turn browser alerts off, the push service says they are gone or keeps refusing messages, the browser's own expiry, or 180 days without a visit.
Disk backups
Render, our host, backs up the disk that holds alert registrations, browser push subscriptions and Live Activity tokens once a day and keeps each backup for at least 7 days, so deleted entries can remain in older backups until Render removes them. If the server ever finds one of those files unreadable, it moves the damaged copy aside on the disk instead of deleting it; that copy is never used to send anything.
Error logs
Method and path only, kept by our host for its standard log period.
Browser settings
In your browser, until you clear them.

Children

GridPulse is a general-audience service. It is not directed to children under 13, and we don't knowingly collect personal information from children. If you believe a child has sent us personal information, for example in a place name or an email, contact us and we will delete it.

Security

Connections to GridPulse use HTTPS. Locations are rounded on your device, device tokens are never written to logs, and the alert registry is kept on the host's private disk, which is not publicly accessible. No system is perfectly secure, but GridPulse keeps very little, so there is very little to protect.

Your choices

Depending on where you live, you may have rights to access, correct or delete personal information about you. Because GridPulse has no accounts and stores no emails or contact details (only device push tokens and the place names you choose), we usually can't tell which information belongs to a particular person; the controls above act on your data directly. For anything else, email us and we will help as far as we can.

Changes to this policy

If GridPulse changes how it handles information, we will update this page and the effective date at the top.

Contact

Questions or requests about privacy: support@gridpulsemap.com. If you email us, we use your address and message only to answer you.