Privacy

Reading the site

Every page read is counted, with or without an account. The count keeps the page's address, the country, region and city the network places the request in, the name of the site a reader came from, and whether the browser is a phone, a tablet or a desk. A reader is counted as a one way hash of the network address, the browser and the day, mixed with a secret: the address itself is never kept, and one day's reader cannot be matched to the next day's. A crawler is counted apart. The rows go after 92 days.

The pages other than My Station, the console and the master dashboard also carry a web analytics tag, which sets its own cookies to count visits and how pages are used. The network that serves the site counts page loads too, without a cookie.

An account

An account keeps its email, its name and username where they were given, and its passcode as a slow one way hash, never the passcode itself. A confirmation or reset code is kept as a hash for fifteen minutes. The account keeps when it was made, and when it was last at work on the site: the time alone, kept at most once in fifteen minutes, with nothing of the page or the device.

A second factor keeps the authenticator app's secret, each passkey's public key and name, and the recovery codes as hashes. My Station keeps each saved page and its order, the alerts chosen and each saved place's forecast zones and time zone, quiet hours, a record of each alert sent (when, which alert, by email or push, and what became of it), and each device that takes pushed alerts: its name, its push address and keys, used only to send it alerts.

The API and purchases

An API key is kept by its public id alone: the key itself is shown once and kept nowhere. Calls are counted by day and route, and the latest calls of each key keep their route, answer, time, size and country for 30 days. What a call asked for is never kept.

A purchase keeps what was bought, the amount, the way of paying, the name, email and place the payment gave, the paying wallet for a payment in USDC, and the payment's own record. Card details never reach the site.

A payment by the call in USDC is also counted by the hour and the kind of call: each price quoted, each payment refused and the reason it was refused, and each payment settled, with no wallet, transaction or address in the count. Every account, key, purchase, call and page read is kept with the name of the site it was made on.

A device switched on for alerts where it is hands over its point, as the device gives it, while a page of the site is open on it. Only its latest point is kept, with how close the device says it is, when, and the forecast zones the weather service places it in; it is read only to match alerts, and removed two hours after the last one, at once when the switch is turned off, and with the account. The master dashboard counts such devices and never shows a point.

A report a reader sets up for themselves keeps the place it is for, the times and days it goes, the time zone it keeps them in, the parts it carries, any figure it waits for, and how it is sent; what each report sent, or why it held, is kept a week. A report is removed with its place and with the account, and comes in the reader's download. The master dashboard counts reports and their sends, and never shows a report's place or what it said.

Messages

A message sent through Contact is kept with the fields it was sent with, and is not shown, shared or sold.

Who sees it

The site's owner, through the master dashboard: who each account is (its email, name and username), when it joined and was last at work, what it saved, the alerts it chose and was sent, its devices by name, its API keys by public id and their use, and its purchases, with the counts of every page read. The dashboard opens for one account, with its passcode and a second factor proved every time, and every look at it is logged.

It never shows a passcode or its hash, a confirmation, reset or recovery code, an API key, the authenticator's secret, a passkey's key, a device's push address or keys, or a card's details. Nothing kept is sold or shared.

Your data

Signed in at My Station, the account's own page downloads everything it keeps as a file, or deletes the account: its saved pages, alert choices and their record, devices, quiet hours, second factors, sessions and when it was last at work all go with it. A purchase stays in the sales record, the site's own books, and an API key bought keeps working.

Questions

Anything about what is kept can be asked through Contact.