Privacy, ads and about

In short

• You can use the map without an account. The page then keeps one visitor cookie and a few settings in your browser, and nothing else about you.
• An account stores the email address or mobile number you sign in with (encrypted on the server), the stations you watch and your alert settings. You can delete it yourself at any time.
• Your browser talks only to this site while you use it, plus Google Maps or PayPal when you tap those buttons, Google's tag and ad code on the map page, where the page has them (see Advertising), and CARTO for its street map when you zoom in on streets outside the US and Canada.
• Nothing is sold or rented, and nothing is shared for marketing unless you press "Accept all" for Google's advertising cookies on the map page (see Your privacy rights). The weather sources never learn who you are: this server fetches the data and passes it on.
• Wherever you live, you can see, download, correct and delete what an account holds, from the account page or by writing to the contact below (see Your privacy rights).
• The StationClosed apps for iPhone and Android use the same account. What they add (the app check, notification tokens, store purchases, and Google's ads on the free plan) is under The iPhone and Android apps.

About this tracker

The tracker shows, for Amazon Flex delivery stations and other Amazon sites in the United States, Canada and around the world, the weather reports and advisories that usually go with a station closing its doors: severe weather warnings, tornado warnings, lightning within a few miles, and Flexers' own reports. It adds the national weather radar with the model's hour ahead, and a 12-hour and 3-day forecast per station. Everything comes from public sources: the National Weather Service and NOAA for advisories, radar, forecasts and lightning, Environment Canada for the Canadian stations' forecasts, warnings and lightning (Data Source: Environment and Climate Change Canada, under its Data Server End-use Licence), Visual Crossing and MET Norway for the forecasts and warnings elsewhere, the Japan Meteorological Agency for Japan's warnings, lightning and thunder nowcast, the Meteorological Service Singapore's lightning network through data.gov.sg for the strikes around Singapore (Singapore Open Data Licence), Open-Meteo for the weather models' thunderstorm forecasts behind the lightning risk (Weather data by Open-Meteo.com, CC BY 4.0), Rainbow.ai for the radar beyond NOAA's reach and the world view's next-hour rain, NASA's GIBS service and EUMETSAT's EUMETView for the world view's moving satellite clouds (Meteosat: contains modified EUMETSAT Meteosat product, CC BY 4.0), airport weather reports, national lightning databases, and public station lists. This server asks them for the weather; none of them is ever told who is looking. It is an independent tool built by a driver for drivers, run on a single small server at stationclosed.com. The About and FAQ page explains how the status is worked out.

It is not affiliated with, endorsed by or connected to Amazon.com, Inc. or its affiliates. "Amazon Flex" names the delivery program the tracked stations belong to. The status shown is an unofficial reading of public weather information; station leadership makes the final call on closures, and a block is never guaranteed either way.

What the page keeps in your browser

Everything below is essential to the site working (signing in, fair use, your own settings) and is set without asking. The only optional cookies are Google's, on the map page when ads are on: Google personalises its ads only if you press "Accept all" in the cookie bar, and never when your browser sends a Global Privacy Control signal. "Essential only", or not answering, keeps ads non-personalised, and keeps the Google tag, where the page has it, from setting any cookie (see Advertising). Change your answer any time with "Your privacy choices" at the bottom of the map page, or "Cookie choices" in its menu.

On an https address the sign-in, device and visitor cookies carry the browser's __Host- prefix, which pins them to this site. Apart from Google's optional cookies above, there is no other browser storage, no third-party analytics beyond optional Google Analytics on the map page (see Advertising) and no fingerprinting apart from the limited station-preview security checks below and the one-time check described under Free trial. Clearing site data removes the browser storage listed above, but does not reset server-side account limits or the short-lived preview checks.

Station-preview security checks

A signed-in Free account's station-change clock is saved with its account, not in a browser cookie. Signed-out live station previews also use short-lived, purpose-specific keyed fingerprints of a network address combined with a coarse browser/operating-system label, and of the signed visitor identifier where present. IPv6 addresses are grouped by network prefix. The security file contains fingerprints, a selected station code and an expiry time, not raw network addresses or full browser strings. These checks are separate from advertising and are not sent to ad providers. No canvas, installed-font or hardware fingerprint is collected for this purpose.

The station wait lasts 30 minutes from your selection. Refreshing that station does not restart the wait. Expired preview records are removed from the active security file within about a minute while the server is running, or on the next startup. Clearing cookies or restarting the server does not reset them. People using similar browsers on a shared connection can be grouped together; sign in to use your own account's allowance. Changing both network and browser identity can evade these checks, so they are not proof of who someone is. General security logs and backup retention are separate, as described below.

Closure alerts without an account

If you tap the bell on a station and allow notifications, your browser gives this server a push subscription: an address at your browser maker's push service (Google, Apple, Microsoft or Mozilla) and the keys to encrypt messages to it. The server stores that subscription encrypted, with the station or stations you picked, your page language and a count of today's notifications, and nothing that names you. The notifications are encrypted end to end; the push service only carries them. Tap the bell again to turn a station off; when you turn off all of them, block notifications or uninstall, the subscription is deleted (the push service tells the server when it no longer works).

Free trial

New free trials are 7 days of Ultra, with no card, checkout or automatic charge. Start one from your account. When it ends, your account returns to Free unless you choose to buy a plan or have a separate grant. The Android and beta free-month gifts remain separate promotions; existing grants and subscriptions keep their original terms. This change does not cancel an existing card subscription or change its renewal agreement.

To check trial eligibility and prevent repeats, the server keeps a keyed fingerprint of the normalized email permanently, separately from the account. Deleting an account and signing up again with the same email does not restore a free trial. Gmail dots, plus tags and googlemail.com aliases are normalized for this check. The permanent record is a fingerprint and trial-use time, not a plaintext mailing list, and is used only to prevent repeat trials. Other device, browser, network and historical billing-check signals expire after two years. New no-card trials collect no card or billing address. Historical card-trial records are encrypted and expire after two years. Virtual-card screening is not used. If a trial is refused and you think that is wrong, contact support for review.

Offers and a place for lightning alerts

Optional driving time. For a signed-in user, the station summary offers a button to estimate driving time. Opening the summary does not request or show an estimate. Only pressing "Use my location" asks your browser for a fresh location reading, with at most one additional device-location attempt if the first reading is old or imprecise. If you allow it, your coordinates, reading age and accuracy go in an HTTPS request body to this server. A moderately approximate reading requires a separate Use approximate location choice before it is sent for routing. The server sends the starting point, station destination and departure time to Mapbox Directions, not your account id, email address or network address. The same request matches the starting point to a nearby drivable road within a bounded distance; it does not change the station pin. The browser does not load a Mapbox tracking script or contact Mapbox directly for this feature. Mapbox processes the route under its privacy policy.

You can instead save a supported US ZIP or full ZIP+4 as an approximate starting area. Your ZIP is kept with your account and encrypted at rest. You can remove it in Starting point and ETA settings; your own ZIP preference is included in your account data download and follows account deletion. Local Census ZIP-area points and supplemental GeoNames postal localities (CC BY 4.0) supply an approximate origin without sending your ZIP to a geocoding service. ZIP+4 is retained in full, but the on-page estimate uses its five-digit area, not an address or delivery point. Not every postal ZIP has a usable driving origin, and these datasets are not USPS address validation. Saving a ZIP or viewing a station does not request a new route. Pressing Estimate from saved ZIP checks for a saved estimate and can request a route from that ZIP area without reading your device location. Google Maps directions links also include the full saved ZIP when set; Google receives it only when you open that external link, under Google's privacy policy.

We do not save or log device coordinates, reported accuracy or route geometry. A bounded private server-memory cache can keep only the calculated duration, distance, arrival/calculation times, origin type and ZIP label where applicable for up to 30 minutes, so the same account can reuse an estimate without another provider call. It contains no device coordinates or route geometry, is gated by sign-in and station access, and is lost on restart. While signed in, returning to a station can show its earlier estimate until it expires, without sharing your location again or requesting another route. Page-memory estimates clear on account or saved ZIP changes, or when you close the page. We keep aggregate daily request counts and hashes combining account and station ids with request times to enforce one route request per station every 30 minutes across devices and restarts. Expired hashes are removed at the next routing request; if there are no requests, they can remain until routing resumes. These records contain no coordinates or raw ZIP, station or account ids. Earlier account-wide cooldown records retain only their remaining wait during migration. ZIP and exact-location estimates share the station allowance. Denying browser location permission sends nothing for that location request; a route already sent can still use the allowance if you cancel or the provider fails. Routing is optional and separate from advertising consent; there is no background location tracking.

The Block Earnings Calculator can estimate a home round trip on request. It uses the five-digit ZIP area as the Mapbox route origin and shares the station request limit above. Your block log can save the estimated commute mileage and how often you drove it. The calculator’s ZIP stays out of your saved account settings and block log.

Offers (a discount, a free month with a month bought, a free day) are given at random to accounts in a similar situation, so the tracker can see which ones help; some accounts get none. Which one an account got, whether it was used and whether a plan was bought within two weeks are kept with the account's id, nothing more. When a subscriber cancels the renewal, the chance of a thank-you gift to stay depends on what the account has paid, how long it has been with the tracker and how many stations it watches; it is decided once a year.

On Pro and Ultra you can choose a place for lightning alerts with "Use my location" (the browser asks first) or by typing an address. An address is sent from this server to the US Census Bureau's public geocoder to find where it is, and is neither kept nor logged here. Either way the tracker keeps only that one point, rounded to about 100 meters and encrypted, with the name you give it, and uses it for nothing but those alerts and the circle drawn on your own map. Remove it from the account page at any time.

Accounts

The homepage’s optional local article feed asks this server for weather-related headlines matching your selected station’s city and region. The server sends those public place names to the GDELT Project; it does not send your account ID, email address, exact device location or browser cookies. Results are shared in a bounded server cache. External publishers receive your connection only when you open an article; no publisher images or full article bodies are loaded into this feed. The local weather view reuses the station forecast and observation services described on this page and requests official US point warnings when viewed.

Station-closure alert emails stop after one calendar year without a sign-in, including closing-soon notices, extensions and closure roundups. Signing in again restores eligibility under your existing plan and notification settings. Subscription payments, background polling and delivered alerts do not reset this cutoff. It does not block sign-in, security, billing or inactivity-warning emails, or change the separate rules for device notifications and lightning alerts for a saved place.

Personal station-type choices are stored with your account and appear only in your own view. A classification report includes the station code, current tags, proposed type and any explanation you provide; it is sent to support and kept with your support tickets.

You don't need an account to see the map. If you create one, this server stores: the email address or US mobile number you sign in with (encrypted at rest with a key kept apart from the data, and only ever shown masked in logs); when the account was created and last used; the stations you watch and your home station; your alert radius, quiet hours and muted stations; the devices signed in (a coarse label such as "Windows · Chrome", never the full browser string); any passkeys or authenticator app you added; any push-notification subscriptions your browsers registered (encrypted); your plan and the purchase records that gave it to you; the country the account was opened from (from Cloudflare's reading of your network address, which itself is not kept), your page language and your time zone, for the region lock, the language and the times of your emails; the notices shown to the account and whether you closed them; the app's check on whether ads load, on the free plan; counts of the alert emails sent to you (by kind, with the times of the last month's closure emails) and of the times you used a Share button (by the way you shared, never what or with whom); and reports you send about a station being closed or open, kept 30 minutes under a keyed hash of your account. Sign-in codes are never stored: they live in memory for ten minutes and are gone.

Your address is used for sign-in codes, requested alerts and account-service messages, including inactivity reminders. These reminders are not marketing. Delete your account from the account page ("Delete this account"), after the same confirmation step as any other security change: a plan renewing through this site is cancelled first, then the account is switched off at once, with every device signed out and its push subscriptions deleted. The account data is deleted 30 days later; an email tells you that date, and signing in before then keeps the account. Automatic inactivity deletion instead follows three calendar years after the later of last signed-in use and the end of the last paid subscription, with emails at one year, two years and two weeks before deletion. Active subscriptions and unused paid credits remain protected. Signing in resets this clock; receiving alerts does not. "Download a copy of your data" on the account page exports its account data, Scan and Go log and support messages. Separate trial-abuse prevention fingerprints and tax records outlive account deletion as described under How long it is kept.

If you sign in with Google or Apple, the sign-in dialog sends you to Google's or Apple's own page and they send you back; neither company's code runs on this site. This server receives only their id for you and your email address once they confirm it (with Apple's "Hide My Email", the relay address Apple gives the tracker); it keeps the id, encrypted like your address, so the same button opens the same account next time, and asks for nothing else: no name, no photo, no contacts. If an account already uses that email address, it is the one opened, and the address gets an email saying so. Remove the Google or Apple sign-in from the account page at any time; your email code keeps working. Google's and Apple's own privacy policies apply on their pages.

The Block tracker / Scan & Go tracker, on every plan, keeps what you log there (your blocks, payouts, times of day and package counts) on this server with your account, with when it was last saved, so it opens on any phone or computer where you're signed in, on the website or in the StationClosed app. If you enter a station code, business miles, vehicle settings or a block estimate, we keep those with your log to calculate and display driving costs. Since October 10, 2026 it is stored as you entered it, with no passphrase: it is no longer encrypted in your browser before it is sent. A tracker saved encrypted before then asks for its passphrase or recovery code one last time when you next open it, and is then stored the same way. Download a copy from the tracker at any time; delete it there and it is removed at once, or delete your account and it is removed with the account 30 days later. If your plan ends, the tracker is kept and stays readable and deletable, but can't be added to.

The iPhone and Android apps

The StationClosed apps for iPhone and Android (with their widgets, and the Apple Watch and Wear OS apps) show this tracker and use the same account as this site: what is written above under Accounts applies to them as well. You sign in with a code sent to your email address, or with Google or Apple as described above. Each app you sign in on is one of the account's devices, listed on the account page as "iPhone app" or "Android app", with no other detail about the phone; on the free plan the website and an app share one seat, so signing in on one signs the other out. The apps get the weather, radar and stations from this server alone, and the widgets check your Main Station with it on the app's own sign-in. On the phone the apps keep your sign-in, the station list, the last view for the widgets and the watch, and the app's own settings; removing the app removes them. The watch apps get their stations from the phone, through Apple's or Google's own link between phone and watch, and never connect to this server themselves.

So that only the genuine apps use this server, each app checks in from time to time with Apple's App Attest (iPhone) or Google Play Integrity (Android), which vouch for the app and the device to this server. The server keeps, with the app's seat, the result and time of each check (and on iPhone the public key the app made for it), and notes a failed check in its log; nothing else is kept from these checks.

Closure alerts reach the apps through Apple's push service on iPhone and Google's Firebase Cloud Messaging on Android, once you allow notifications. The app then gives this server the token Apple or Google issued for it (on iPhone, with which of Apple's two push services it belongs to), and the server stores it encrypted with the app's seat, like a browser's subscription. Each alert goes to Apple or Google with its title and text (the station, or the name you gave your place, and what changed) and, for a station, which one to open; they deliver it to the phone. Unlike the website's notifications these are not encrypted end to end, so Apple or Google can read that text, but nothing else about you is sent with it. Both apps contain Firebase's crash reporting (Crashlytics) and usage statistics (Google Analytics for Firebase), described below; the Android app also contains Firebase's messaging part. Signing the app out, removing it from the account's devices or deleting the account stops the alerts, and a token Apple or Google reports as no longer working is deleted.

Lightning near a place (Pro and Ultra) works in the apps as on the website (see Offers and a place for lightning alerts). On iPhone you can tap the map, use your Main Station, type an address, or press "Use my location": only then does the app ask the phone for your location, once, with your permission (iOS asks the first time). The Android app never reads your location: it offers your Main Station or an address. An address is looked up through this server as on the website, and is not kept. The app sends this server nothing about where you are until you save the place; then it sends that one point, and the server keeps it rounded to about 100 meters and encrypted, with the name you give it, and uses it for nothing but those alerts and showing it to you. The alerts name the place by that name and give the strike's distance, never the place's position. If you have let the iPhone app use your location, its map also shows where you are; that stays on the phone. Remove the place in the app, or on the account page, at any time.

Plans and the Countrywide Pass bought in an app are paid to the store you got the app from: Apple's App Store, Google Play, or Samsung's Galaxy Store. The store handles the payment; this server never sees your card or bank details. Each purchase carries a random id made for your account that names nothing else, so the store's records and this server's can be matched. The app sends this server the store's proof of the purchase (Apple's signed transaction, Google's purchase token or Samsung's purchase ID); the server checks it with the store and keeps, with your account, the store's id for the subscription, the plan, whether it is active and until when, and the purchase record (the plan, the amount and the store's transaction id). It later asks the store, or hears from it, about renewals, cancellations and refunds. A plan bought in a store is managed and cancelled in that store. Where an app offers paying on the website instead, it opens this site's checkout through a one-time link (see Purchases below). A payment made through the Android app's link from Google Play is reported to Google, as Google's program for such links requires: the amount before tax, the tax, the time and the country, with Google's token for the link, and each renewal the same way; nothing else about you.

Free accounts see Google AdMob ads in the apps, as described under Advertising, together with the apps' check on whether ads load. On iPhone, Apple's tracking prompt also appears once, after Google's consent message; the phone's advertising identifier reaches Google only if you choose "Allow" there. On Android, Google's ad code may use the phone's advertising ID, which you can reset or delete in the phone's settings. When you watch a rewarded ad for a boost, AdMob tells this server itself that it was watched, with your account's random id from the paragraph above and AdMob's id for that view, which the server keeps so that the view counts once. "Ad privacy choices" on the app's Account screen opens Google's consent choices again where the law requires it. Paid plans see no ads, and the app does not ask them about ads. Apart from Google's ad code, the apps carry no analytics, tracking or crash-reporting code, and no other ad network.

As with the website, the apps' connection to this server goes through Cloudflare. Beyond that, the apps involve these companies, each under its own privacy policy: Apple (sign-in with Apple, App Attest, push notifications, App Store purchases, the link to an Apple Watch, and Apple Maps, which draws the iPhone app's maps and gives directions), Google (sign-in with Google, Play Integrity, Firebase Cloud Messaging, Firebase Crashlytics and Google Analytics for Firebase in both apps, Google Play purchases, AdMob on the free plan, the link to a Wear OS watch, and Google Maps for the Android app's map and directions, unless you open directions in another maps app) and, in the Galaxy Store version only, Samsung (Galaxy Store purchases). The maps load the part of the map shown from Apple or Google, which see the phone's network address and that area.

Crash reports and usage statistics: when an app crashes or freezes, Firebase Crashlytics sends Google a report of what the app was doing (the code that failed, the app's version, the phone's model, system version, free memory and storage, and the last few screens opened), so the crash can be fixed. Google Analytics for Firebase counts which screens are opened and a few actions in the app (for example, opening a station or the map). Both identify the phone only by a random id Firebase makes for the installation, which reinstalling the app replaces; neither is sent your email address, phone number, name, sign-in, location or the stations' names, and this server sends them nothing about your account beyond your plan (Free, Pro or Ultra) and the app's language. Google keeps them under Firebase's own terms and data retention settings. Turn either off on the app's Account screen ("Send crash reports", "Share usage statistics"); test versions of the apps send neither.

Feedback you send from the apps ("Send feedback") goes to this server: your words, what kind of message it is, any screenshots you attach, and, unless you switch off "Include device details", the app's version, the phone's model and system version, its language, time zone, screen size, network type (Wi-Fi or mobile) and your Main Station. Signed in, it is kept with your account's id; signed out, with the reply address you give, if any. Screenshots have their hidden details (such as where and when a photo was taken) removed before they are kept, and everything is kept encrypted on this server, read only by the operator, and not answered; it is deleted with the account, and a year after it was sent in any case.

A message you send from Help in the apps becomes a support ticket on this server, with your account's id, email address, plan, Main Station and country and the app's version; the operator gets it by email and answers by email, and you can follow it in Help. Tickets are kept encrypted on this server, apart from the account; they are deleted with the account, and any ticket with no new message for two years is deleted.

Delete the account in either app (Account, then "Delete account") or on the account page. It is switched off at once: every app and browser is signed out, and the account's notification subscriptions and tokens are deleted. 30 days later it is deleted, with its stations, settings, devices, purchase records and Scan and Go tracker log, and an email to the account's address tells you that date; signing in before then keeps it as it was. A plan bought in an app store keeps renewing until you cancel it in that store. Removing an app from the phone does not delete the account.

Weather data and other sources

Nearby gas reports use a shared server cache from GasBuddy's publisher service, collected in recurring 16-hour cycles. A saved public gas-station directory avoids repeating completed discovery searches. Only public station-area coordinates are used, not your saved starting ZIP, device location or account. Listings have partial coverage and can be outdated. Publisher prices without a cash or credit designation are labelled Reported price. Directions to a gas station open Google Maps only when you press the link, passing that public destination. Google can ask you for a starting point under its own privacy policy.

For signed-in accounts, first-party counters record requests for ETA, traffic and directions, including gas directions. They count automatic ETA requests separately. While your account is on Free, the website and shared tools in the apps also count actions such as opening gas prices, opening the Block Earnings Calculator, applying an estimate, opening road reports, local weather, articles, events or order volume, and opening or requesting a driver invitation. Account counters store totals with the first and last use times. They are available to the operator and in your data download and are deleted with your account. A separate site-wide total counts invitation and reminder emails accepted for sending without recording the sender or recipient in that total. Global Privacy Control stops these optional counters. Navigation, estimates and invitations still work when counters are blocked.

This server fetches everything itself, on a schedule, for everyone at once: advisories, tornado-warning polygons and forecasts from the National Weather Service, the Canadian stations' forecasts and tornado warnings from Environment Canada, base map tiles from USGS and Natural Resources Canada, radar frames from NOAA, the hour-ahead radar from NOAA's forecast model, lightning reports from national lightning databases, forecasts outside the US and Canada from Visual Crossing and MET Norway, radar outside NOAA's reach from Rainbow.ai, airport weather reports, a global forecast model's gusts and thunder from NOAA, the weather models' lightning and thunderstorm forecasts from NOAA, Deutscher Wetterdienst, Environment Canada, ECMWF and the Met Office, official warnings from the national weather services (the Japan Meteorological Agency, the India Meteorological Department through NDMA's SACHET, the Met Office, Mexico's SMN, Brazil's INMET and MeteoAlarm), Japan's weather stations and lightning network from the Japan Meteorological Agency, security-incident notes from police dispatch and local news, station locations from public station lists, and the European Central Bank's daily exchange rates, for plan prices in your own currency. Those services see this server's address and a contact email, never yours. Your browser downloads the results, the map libraries and the fonts from this site alone, with one exception: outside the US and Canada, from the city zooms in, the street map comes from CARTO (© OpenStreetMap contributors, © CARTO), whose terms require your browser to load its tiles from CARTO directly. CARTO then sees your network address and which part of the map you are looking at, under its own privacy policy; it is not told anything else about you.

A station's "Share" button opens your phone's own share menu, or offers links to WhatsApp, Facebook and Reddit: nothing goes to any of them unless you pick one, and then only the station's link and status, as you send it. The tracker counts each press of a Share button and which way the share went (the share menu, WhatsApp, Facebook, Reddit or the copied message), with your account when you are signed in; never the message, the station or who received it. A shared link shows a preview (the station's status, and a picture of it this server draws itself), which the app showing the preview fetches from here.

On the Spanish pages, the weather services' own words (forecast phrases, warning headlines) and the long pages like this one are translated by a machine-translation service when the operator has set one up: this server sends it only those texts, never anything about you, and keeps each translation so a text is sent once. The rest of the Spanish site is translated by the tracker itself.

Two buttons open other companies' sites in a new tab: "Directions" (Google Maps) and checkout (PayPal). Their privacy policies apply from the moment you tap. The site is served through Cloudflare, which relays traffic between your browser and this server and applies its own privacy policy to what it handles.

When you search for a station by address, the page ranks the stations nearest you first. For that it may use the country, state or province and rough position (to about a kilometre) that Cloudflare works out from your network address and passes along with the page, the station you already picked, and your device's time zone. The country also picks where the page starts: the stations of the country you are in, until you choose another in the menu. Nothing of this is stored or sent anywhere: it only orders the results and sets the starting view in your browser.

The "Near me" button asks your browser for your location, once each time you press it, and only then. The page uses it to list the stations closest to you and to put a dot where you are on the map. It is not stored, not sent to this server and gone when you leave the page. Your browser asks you first, and you can refuse.

Advertising

Visitors and free accounts can see ads served by Google AdSense; paid plans see none. Outside the regional consent-message path described below, optional Google advertising and analytics code loads only after a current Accept all choice. With Essential only, no choice or a Global Privacy Control request, that optional code is not loaded. Google and its partners may use cookies, web beacons and IP addresses for advertising and measurement after permission. Advertising cookies can enable ads based on visits to this and other websites. Non-personalized advertising is not treated as cookie-free.

You may opt out of personalised advertising by visiting Google Ads Settings, or opt out of third-party vendors' use of cookies for personalised advertising at www.aboutads.info. How Google uses information from sites that use its services is described at policies.google.com/technologies/partner-sites. Visitors from the European Economic Area, the United Kingdom and Switzerland are shown no ads and load no ad code at all.

The ad code runs only on the map page, in the three labelled ad spaces; there are no ads in dialogs or over the map. The account page, the sign-in steps and this page share no document with it, so nothing an ad loads can read what you type there.

In the StationClosed apps, free accounts see ads from Google AdMob; paid plans see none. Google's own consent message asks first where the law requires it, and how Google uses the data is described at policies.google.com/technologies/partner-sites. On the free plan the app also checks now and then whether its ads can load, and sends the result to this server with your account. Free accounts whose ads load get updates every 2 minutes in the app; when the ads are found to be blocked, updates come every 6 minutes instead, until an ad loads again.

The map page also loads the Google Ads tag (Google's gtag.js), which tells Google when a visit came from one of the tracker's own ads on Google, so the operator can see which of those ads bring drivers in. If you press "Accept all" in the cookie bar, it sets Google's advertising cookies (such as _gcl_au) and may add your browser to a list for showing the tracker's ads to past visitors elsewhere. With "Essential only", no answer, or a browser sending Global Privacy Control, the tag is not loaded and sends no measurement pings. It is not loaded on the account page, the sign-in steps or this page, nor for paid plans or visitors from the European Economic Area, the United Kingdom and Switzerland. How Google uses the data is described at policies.google.com/technologies/partner-sites.

The map page also runs Google Analytics through the same tag, which counts visits and page views and, with Google's default settings, how far the page was scrolled and which outside links were tapped (the tracker sends it no events of its own), so the operator can see how many drivers use the tracker and when. If you press "Accept all" in the cookie bar, it sets Google's analytics cookies (_ga and _ga_*, kept for two years) to tell returning visitors from new ones. With "Essential only", no answer, or a browser sending Global Privacy Control, the tag is not loaded and sends no measurement pings. Google Analytics does not log or store IP addresses. It is not loaded on the account page, the sign-in steps or this page, nor for paid plans or visitors from the European Economic Area, the United Kingdom and Switzerland. How Google uses the data is described at policies.google.com/technologies/partner-sites.

Purchases

PayPal handles checkout: you pay on PayPal's own pages and PayPal tells this server that the order was paid. This server keeps the PayPal order id and the purchase record with your account; it never sees your card or bank details. A PayPal subscription is set up and billed by PayPal each month or year: this server keeps its subscription id and the payments PayPal reports, and tells PayPal to stop it when you cancel from your account page. PayPal's privacy statement covers what PayPal keeps.

Stripe handles card payments (and Link, Stripe's saved-details wallet): you pay on Stripe's own checkout page and Stripe tells this server the payment went through. This server keeps the checkout session id and the Stripe customer id (and for a renewing plan the subscription id) with your account; it never sees your card number. A payment the card's issuer reports as likely fraud is refunded and the plan taken back. Stripe's privacy policy covers what Stripe keeps.

We use Stripe for payment, analytics, and other business services. Stripe collects identifying information about the devices that connect to its services. Stripe uses this information to operate and improve the services it provides to us, including for fraud detection. You can learn more about Stripe and read its privacy policy at https://stripe.com/privacy.

Bitcoin invoices give you a fresh address derived from the site's public key. The server watches the public Bitcoin blockchain for the payment through a block explorer and keeps the address and the transaction id with your account. Blockchain transactions are public by nature.

Solana invoices are recognised by a reference key on the public Solana network. The server keeps the transaction id with your account; the paying wallet address is visible on the public blockchain, as all Solana transactions are.

ETH invoices (Ethereum and Robinhood Chain) are recognised by their exact amount, read from the network's public block explorer (Blockscout). The server keeps the transaction id with your account; the paying address is visible on the public blockchain, as all such transactions are.

The Donate button in the top bar, the menu and the donations banner over the map open a donation in Bitcoin, Solana or ETH on this site. A donation needs a free account: it is an invoice like a plan's (the same coins, addresses and records as above), and the amount, the coin and the transaction id are kept on your account's purchase record. The first donation of $22.00 or more on an account gives it a year of Ultra (once per account). Closing the banner is remembered in your browser's storage only, until the next day.

Local events

The server requests shared event listings for cities with eligible Flex and DSP stations from Ticketmaster every two days. Local event headlines come from a news index and available local publisher feeds. These services receive public station-area information and the server's network address, not your account, saved starting ZIP or device location. Headlines link to their publishers; no article text or images are copied. Event listings and news can be incomplete or outdated. Following an event or publisher link opens that company's website under its own privacy policy.

Sign-in codes and alerts

Sign-in codes and closure alerts go by email. Email goes through the operator's mail provider; every alert carries a stop link and a one-click unsubscribe header. Push notifications use your browser's own push service (Google, Apple, Microsoft or Mozilla, depending on the browser): the server stores the subscription address your browser gives it and sends encrypted notices through it; the push service cannot read them.

Free accounts get station-closure alerts by push notification, not email. Closure emails stop when upgraded access ends. Eligible Free users may receive one courtesy email inviting them to Ultra, sent through a one-time campaign or automatically when upgraded access ends, unless they have unsubscribed or already received it. Its Ultra monthly link shows the price and payment terms before any purchase.

Unsubscribing permanently stops our reminder and marketing emails. Resuming closure alerts does not turn those emails back on. We retain a keyed email fingerprint and unsubscribe date separately from your account so deleting and recreating an account does not undo your choice. A separate one-time courtesy-email record prevents repeat welcome-back messages. These records contain no plaintext email address and survive account deletion. Sign-in codes, receipts, security notices and replies to support requests are separate.

Driver invitations. A signed-in email user may ask us to send one invitation to someone who wants to receive it. We pass that address to our email service to deliver the invitation, not to weather or event providers. The invitation is in English and includes a stop link that works without an account. Existing email opt-outs apply. Keyed sender and recipient fingerprints and request times enforce one invitation per recipient every 30 days, plus sending limits; they do not contain plaintext addresses or create accounts. Expired invitation-limit records are removed when the service reloads. Unsubscribe fingerprints remain separately so later invitations and marketing stay blocked.

Fair use, security and logs

The server keeps short-lived counters in memory, by visitor id and by network address, of how the site is being used (pages and stations asked for, codes sent, puzzle answers, refused requests), to share the weather feeds fairly and to stop abuse. Unusually heavy use brings up a picture puzzle before the page carries on, as does asking for a sign-in code. Before a code goes to an email address, the server checks that the address can receive mail; when an alert email bounces or is marked as spam, the mail service tells this server, and email alerts to that address pause until you confirm the address again. Those counters are not written to disk, and network addresses are never stored with an account. The server's log records start-up, errors, refused requests, sign-ins and administrative actions, with the network address they came from; ordinary page views and data requests are not logged at all. The log is kept on the server for 30 days, then deleted by the operating system. If a browser reports that the page's security policy blocked something, the report (the blocked address and the page, nothing personal) is logged the same way. The site is reached through Cloudflare, which keeps its own short-term traffic logs under its policy.

Your choices

• Use the map without signing in.
• Sign out from the account page, sign out any other device from the device list there, or delete the account there.
• Stop alerts with the link in any alert email, or reply STOP to a text.
• Pick light or dark mode in Settings; allow or block ads in your browser: the page works either way.
• Opt out of personalised ads with the links under Advertising.
• Download a copy of everything the account holds, from the account page.
• Use any of the rights under Your privacy rights.

Who is responsible for your data

The tracker, its apps and everything this page describes are run by the operator of stationclosed.com (name and postal address on request from the contact below). For the privacy laws below that is the "controller" (the "business" in California, the "data fiduciary" in India, the "controlador" in Brazil and the "responsable" in Mexico and Quebec). The same person, reached at support@stationclosed.com, is the contact for privacy: the person in charge of the protection of personal information (Canada and Quebec), the data protection officer (Singapore), the "encarregado" (Brazil) and the grievance officer (India).

Why your data is used, and on what grounds

Each use above has one purpose, and nothing is used for anything else. The laws of the UK, the EU, Brazil and several others ask for the ground each use rests on:

• To give you the service you asked for (contract): your account, stations, settings and alerts, the apps' seats and notification tokens, the plans and passes you buy, the Scan and Go Tracker and your support messages.
• Your consent: Google's advertising and analytics cookies on the map page ("Accept all"), the apps' personalised ads (Google's consent message, and Apple's tracking prompt on iPhone), and a place you save for lightning alerts. Withdraw it at any time, as easily as you gave it: "Your privacy choices" at the bottom of the map page, "Ad privacy choices" in the apps, or removing the place.
• Legitimate interests, weighed against yours: keeping the service secure and fair (sign-in checks, the picture puzzle, fair-use counters, the log, the apps' check that they are genuine, the one-trial-per-person check), funding the free plan with ads that are not personalised, and learning which offers and features help (offers, Share counts). You may object to any of these by writing to the contact below.
• Legal obligations: tax and accounting records of payments.

Under India's Digital Personal Data Protection Act the tracker relies on the consent you give when you open an account or turn a feature on (withdraw it by deleting the account, or the feature's data), and on the uses the Act allows without it. No decision with legal or similarly significant effects is made about anyone by automated means alone: the automated checks only refuse a second free trial, slow down a visitor making too many requests and pick offers at random, and a person will look again at any of them if you write.

How long it is kept

• An account and its account data: until you delete it, then 30 days switched off, then deleted. Automatic inactivity deletion uses three calendar years after the later of your last signed-in activity and the end of your last paid subscription. Receiving weather alerts does not reset that clock. Reminder emails are scheduled after one year, after two years, and two weeks before deletion. Signing in resets the clock. Active paid subscriptions, remaining paid time and unused paid credits protect an account from automatic deletion. Email accounts are not automatically deleted until the final warning has been sent successfully and at least two weeks have passed; an already-overdue account receives that full warning period first.
• Sign-in codes: ten minutes, in memory only. Reports of a station being closed or open: 30 minutes.
• Push subscriptions and app notification tokens: until you turn notifications off, sign out, or the push service says they no longer work.
• Support tickets: deleted with the account, and otherwise two years after their last message.
• A free trial's keyed email fingerprint and trial-use time: permanently, to prevent repeat trials after account deletion. Other trial-check hashes and encrypted historical trial records: two years.
• Tax records of payments taxed by this site (PayPal and crypto: the account's id, the plan, the country, the amounts and the tax, no name or address): as long as tax law asks, up to ten years. Payment processors and app stores keep their own records under their own rules.
• The server's log: 30 days. Fair-use counters: in memory, for an hour at most.
• The offers record of a deleted account is kept for the counts under a random key that no longer leads to anyone.

Where it is kept and who else handles it

The server is in a DigitalOcean data centre in New York, in the United States, so whatever you send from another country is transferred there. These companies handle data for the tracker, only to do their part: DigitalOcean (the server), Cloudflare (the connection to the site and the support email address), the email service that sends codes and alerts, Apple and Google (push notifications to the apps, and sign-in with Apple or Google when you choose it), and the US Census Bureau's geocoder (an address you type for a place, without anything about you). Stripe, PayPal, Apple's App Store, Google Play and Samsung's Galaxy Store handle payments under their own privacy policies, as do Google's advertising, analytics and reCAPTCHA services described above. Where data reaches these companies from the UK or the EU, they rely on the EU–US Data Privacy Framework and its UK extension, or on the European Commission's standard contractual clauses in their terms. The United States has no general federal privacy law like the UK's, the EU's, Japan's or Brazil's; some states, such as California, have their own. The safeguards that apply wherever the data is are described under Security and breaches.

Your privacy rights

Wherever you live, you can:

• See and get a copy of what the tracker keeps about you: the account page shows it, and "Download a copy of your data" there gives it all as one JSON file you can take elsewhere.
• Correct it: change your stations, settings and addresses on the account page, or write.
• Delete it: "Delete this account" on the account page (sign in at stationclosed.com/account) or "Delete account" on the apps' Account screen, or write to the contact below without signing in (all of it on one page: Delete your account). The account is switched off at once and deleted 30 days later with its account data (see The iPhone and Android apps). Tax records and the separate trial-abuse prevention records follow the periods under How long it is kept.
• Withdraw consent and object to a use, as described under Why your data is used, and ask for a use to be paused while a question about it is settled.
• Opt out of the sale or sharing of your data and of targeted advertising: nothing is sold, and Google's advertising cookies are used only after "Accept all" and never when your browser sends a Global Privacy Control signal. "Your privacy choices" at the bottom of the map page changes your answer.
• Be treated the same whichever of these rights you use: the price and the service do not change.

To use any of them, use the account page, or write to support@stationclosed.com from the address the account uses (or say which account it is: you will be sent a code to confirm it is yours). It costs nothing, and you get an answer within 30 days (Brazil: a full copy within 15 days). Someone you authorise may ask for you with your signed permission, and you will still be asked to confirm. If a request is refused you are told why, and you may appeal by replying to that answer: a different look is taken and you get its result within 45 days. You can also complain to your privacy regulator at any time.

California and other US states. In the past 12 months the tracker has collected: identifiers (an email address or mobile number, the account's id, device and visitor ids, network addresses in the log); commercial information (plans and purchases); internet activity (Share counts, the ads check, offers); geolocation (a rough region worked out from the network address and not stored, and a place you save for lightning alerts, which is "sensitive" precise geolocation and used for nothing but those alerts); account sign-in details (passkeys and authenticator apps, never passwords); and what you write to support or log in the Scan and Go Tracker. They come from you, your browser or phone, and the payment processors and app stores. They are used for the purposes above, kept as above, and disclosed only to the service providers above for business purposes. The tracker does not sell personal information for money and does not knowingly sell or share that of anyone under 16. With "Accept all", Google's advertising cookies on the map page count as "sharing" for cross-context behavioural advertising under California law; you can stop it with "Your privacy choices" or Global Privacy Control, which the page honours. No personal information is disclosed to others for their own direct marketing. If an appeal is refused, you may contact your state's Attorney General.

UK and European Union. Your rights under the UK GDPR and the GDPR include access, correction, erasure, restriction, portability and objection. Complain to the Information Commissioner's Office (ico.org.uk) or the authority where you live. What the website shows visitors from there is under Advertising.

Canada. Your rights under PIPEDA, and in Quebec the Act respecting the protection of personal information in the private sector, include access and correction, withdrawing consent, and in Quebec having your data given to you in a structured format. Nothing that can identify, locate or profile you is switched on by default: your location is read only when you press "Near me" or save a place, and ads are personalised only after "Accept all". Complain to the Office of the Privacy Commissioner of Canada (priv.gc.ca) or, in Quebec, the Commission d'accès à l'information (cai.gouv.qc.ca).

Brazil. Under the LGPD (article 18) you may confirm whether your data is processed, access it, correct it, have it anonymised, blocked or deleted, take it to another provider, learn who it is shared with, and revoke consent. Complain to the ANPD (gov.br/anpd).

Mexico. Under the Federal Law on the Protection of Personal Data Held by Private Parties you may access, rectify, cancel or oppose the use of your data (your ARCO rights), and revoke consent, by writing to the contact below. Complain to Mexico's data protection authority (since 2025, the Secretaría Anticorrupción y Buen Gobierno).

India. Under the Digital Personal Data Protection Act you may get a summary of your data and of who it was shared with, have it corrected, completed, updated or erased, withdraw consent, and name someone to use these rights for you if you die or cannot. Write to the grievance contact below first; you get an answer within 30 days, and you may then take it to the Data Protection Board of India.

Japan. Under the Act on the Protection of Personal Information you may ask for your data, and records of its provision to others, to be disclosed, corrected, or no longer used or provided. The safeguards taken are those under Security and breaches, and the data is kept in the United States (see Where it is kept). Complain to the Personal Information Protection Commission (ppc.go.jp).

Australia. You may access and correct your data under the Australian Privacy Principles. Data is held in the United States. If you are not satisfied with the answer to a complaint, take it to the Office of the Australian Information Commissioner (oaic.gov.au).

Singapore. Under the Personal Data Protection Act you may access and correct your data and withdraw consent. Complain to the Personal Data Protection Commission (pdpc.gov.sg).

Security and breaches

Every connection is encrypted (HTTPS, with the apps checking the site's certificate). Addresses, sign-in methods, push subscriptions, places and support tickets are encrypted on the server (AES-256-GCM) with a key kept apart from the data; the server's files are readable by the tracker alone; only the operator can reach the server, with a key and not a password; and nothing is kept longer than the times above. If a breach ever puts your data at risk, you and the regulators the law names are told what happened, what was involved and what to do, as quickly as those laws ask (in the UK and EU within 72 hours of learning of it; in India the Data Protection Board at once and you without delay).

Children

The tracker is for adult delivery drivers, 18 and older, and is not directed to children. No account is knowingly kept for anyone under 18; write to the address below to have one removed.

Changes

When this page changes, the date at the top changes with it; a change to how your data is used is announced on the map page before it applies. The tracker's own code, including this page, is what actually runs; the description here is kept in step with it.

Contact

Questions, requests about your data, appeals or complaints: support@stationclosed.com.

Back to the tracker