Privacy, ads and about

このページの一部はまだ英語のままです。Read it in English.

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, rented or shared for marketing. The weather sources never learn who you are: this server fetches the data and passes it on.
• 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 "Cookie choices" at the bottom of the map page.

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 storage, no analytics beyond Google Analytics on the map page (see Advertising) and no fingerprinting, apart from the one-time check described under Free trial when you start one. Clearing site data in your browser removes all of the above、the page then starts as a new visitor.

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

The free trial of Pro or Ultra, and the free month of Ultra while that promotion runs (given on signing in), asks for no payment. So that each person gets one, the server keeps, when a trial starts, keyed one-way hashes of: the account's email address (dots and "+" tags in a Gmail address set aside), this browser's device and visitor cookies, the network address the trial was started from (an IPv6 address by its first half), and a few traits any web page can read from the browser (its name and version, languages, screen size, time zone and processor count, combined by the page into one value). A hash cannot be turned back into the address or the traits、it only shows that the same one started a trial before. The hashes are kept for two years apart from the account, so deleting the account does not reset the trial, and they are used for nothing else.

From December 1, 2026 the free trial is 7 days of Ultra and starts with a debit or credit card on Stripe's checkout page、when the 7 days end, the card is charged for Ultra monthly until you cancel (cancel before then and nothing is charged). The card number goes to Stripe only and never reaches this site. To keep it to one trial per person, the server also keeps, beside the hashes above, a keyed one-way hash of the card (Stripe's fingerprint for it, the same for the same card number) and of the billing address, and a record of the trial encrypted at rest (AES-256-GCM): the IP address and device cookie it was started from, the card's brand, last four digits, type and expiry, the billing address and the account's email address. Only the site's operator can open that record, to look into repeated trials、it is kept for two years like the hashes and used for nothing else.

Offers and a place for lightning alerts

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

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、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 to send you the codes and the alerts you asked for, and for nothing else. There are no newsletters, no marketing, and no sharing with anyone. 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, so no more alerts are sent to it. 30 days later the record is deleted with everything in it, and an email to the account's address tells you that date、signing in before then keeps the account as it was. A free account that has not signed in for about 18 months and never bought anything is removed by itself. There is no export button: the account page shows everything the account holds. Payment records may be kept by the payment processor under its own rules.

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. 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 proves itself about twice a day while you use it, and whenever the server asks: the iPhone app with Apple's App Attest, the Android app with Google Play Integrity. On iPhone the app makes a key in the phone's secure chip, which Apple vouches for once, and signs a fresh challenge from this server with it、the server keeps the key's public half, its id and a use counter with the app's seat. On Android, Google Play gives the app a token carrying the server's challenge, Google reads it for this server, and the server keeps only Google's three verdicts with the seat: whether Google Play recognises the app, whether the device passes Google's integrity check, and whether the app is licensed through Google Play. A check that fails is noted with the seat and in the server's log, with the reason. Apart from these and the time of each check, nothing is kept from either check.

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. The Android app contains Firebase's messaging part alone, without Firebase Analytics, and gets Firebase's settings from this server once you sign in. 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, 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.

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, and are not removed when the account 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

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, 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, and station locations from public station lists. 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 see ads served by Google AdSense、paid plans see none. Third-party vendors, including Google, use cookies, web beacons and IP addresses to serve ads based on your prior visits to this website or to other websites. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visit to this site and/or other sites on the Internet.

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.

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 (whether its ads arrive, whether Google's ad servers can be reached from the phone, and on Android whether a known ad-blocking DNS service is set) and sends the result to this server with your account: loading, blocked or unknown, and those signals. Free accounts whose ads load get updates every 2 minutes in the app、when several checks over at least 20 minutes find the ads blocked (never a slow connection), 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, it sets no cookies and sends Google only cookieless pings (that the page loaded, with any ad click identifier removed). 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と_ga_*, kept for two years) to tell returning visitors from new ones. With "Essential only", no answer, or a browser sending Global Privacy Control, it sets no cookies and sends Google only cookieless pings (the same counts, with no identifier kept between visits). 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 寄付 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.

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.

Fair use, security and logs

The server keeps short-lived counters in memory, by visitor id and by network address, to spread the shared weather feeds fairly and to stop abuse: how often a page or the status was requested, how many station details and which stations were opened in the last hour, how many codes were sent, wrong answers to the picture puzzle, and whether a request was refused. Heavy use (many station requests in a minute, more than 100 different stations in an hour, many searches in a minute) 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: its spelling, whether its domain takes mail (a DNS lookup) and whether it is a throwaway inbox、when an alert email bounces or is marked as spam, the mail service tells this server, and email alerts to that address pause after repeated bounces 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 a limited time and rotated 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

• 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.

Children

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

Changes

When this page changes, the date at the top changes with it. The tracker's own code, including this page, is what actually runs、the description here is kept in step with it.

お問い合わせ

Questions, deletion requests or corrections: support@stationclosed.com.

Back to the tracker