Privacy

2.1 Your email address, if you subscribe

Subscribing stores your address, the time you subscribed and whether you have confirmed it. It records whether you want the Monday brief itself and whether you opted in to alerts between Mondays: conditions changing, a score crossing its line, or an outsized move in a market input. If you set pause and resume lines for your own plan on the planning page, it stores them as numbers on the two scores for each area you chose, held unconfirmed until you click the link. If you left that box ticked, it also stores the runway band you had chosen when you set those lines, and the date. The band is one of four, such as 12–24 months, and never a cash or runway figure. It is replaced or cleared with the lines. Finally, it stores a random token for the unsubscribe link and, while a request is waiting for you, a separate one-time code for its confirmation link. It keeps the times of any confirmation emails sent to your address in the last day, so that no one can send it more than three in an hour or six in a day. It is held in Cloudflare KV and used to send you those emails and nothing else. Nothing is sent until you confirm. Any later request for your address changes nothing until you open the link it sends and press Confirm on the page that link shows. That holds for turning alerts or the Monday brief on or off, setting plan lines, and subscribing again after leaving. The email and that page say what the request would change. A confirmation link works once, for 7 days, and stops working when a newer request is made for your address. Every email carries an unsubscribe link. It opens a page with one button, so a mail filter that opens links to scan them cannot unsubscribe you. Pressing it deactivates the record immediately and drops any request still waiting.

2.2 A random identifier for your browser

Your browser generates a random identifier and keeps it in local storage the first time you use a feature that saves something: recording a decision, or saving a Decision Shield preset. It is sent with those requests so that what one browser saved can only be read back by that browser.

It is not derived from anything about you, is never joined to your email address, and is not part of any measurement. Clearing site data in your browser removes it. The next thing you save gets a new one, and the old records become unreachable.

2.3 Things you deliberately save

Decisions you record are stored in Cloudflare KV against the identifier above, with the reading at the time so a later week can be compared against the decision's own assumptions. Everything else you set stays in your browser and is never sent: your operator profile, Decision Shield presets, drafts of your own pause and resume lines, the last guidance this browser saw, the number of decisions you last recorded, the theme, and the one-time explainers you have dismissed. The brief reads that number so it asks for your record only when there is one. A Decision Shield link you copy is the exception. The plan you typed is written into the link, so whoever opens it sends that text to this site. There it can appear in the request logs described in 2.6.

2.4 Two cookies, set only if you calibrate the guidance

Picking a company stage writes a cookie so the panels on a page agree with each other and the guidance is calibrated the same way everywhere. Picking a cash runway band writes a second one for the same reason. Each holds only the band you picked, never a cash figure. Each is read only by this site and set by no other action.

2.5 Usage measurement

Pages report how fast they loaded, which route was moved to from which, whether a subscription was made, and whether the brief was copied and in which format. They also report the shape of a search, described above. A visit to the brief also reports where it arrived from, as a coarse bucket: a search engine, a link or typed directly, never the referring URL. It reports whether this browser had opened the brief before, and whether the visit used any control on the page, though not which one. These go to Cloudflare Analytics Engine, and section 5 turns them off for one browser.

What is written is the event and nothing around it: no IP address, no user-agent string, and none of the identifiers above. The intake refuses any record carrying a field it does not expect, so a stream cannot quietly start carrying more than it says.

2.5a Pages saved for offline reading

Your browser keeps a copy of the pages you have opened, and of the fonts and scripts they need, so the brief still opens without a connection. It is a copy of what this site already sent you. No record of what you read is made here or anywhere else, and nothing about it is sent back. When you are offline the page says which reading it is showing you rather than letting an old one pass for the current one. Clearing site data removes it.

2.5b Browser notifications, if you turn them on

If you ask this browser to notify you when conditions change, your browser generates a subscription: an address its own push service assigned, and two keys it made. We store those three things against the random identifier above. That is the whole record: no email address, no reading, and no history of what was sent. It is used to wake this browser when conditions change (a handful of times a year), and for nothing else.

The notification itself carries no content. What it says is fetched by your browser when it is shown, so it cannot deliver a stale reading. Turning notifications off in the page removes the stored subscription; blocking them in your browser stops them arriving either way.

2.6 Abuse limits and server logs

Endpoints that send email or accept public writes are rate-limited against the network address Cloudflare reports for the request. That address is used as a counter key inside Cloudflare's rate limiter; this site does not store it.

This site runs on Cloudflare, so Cloudflare processes every request to serve it, and request-level logging and tracing are enabled for debugging. Cloudflare acts as our infrastructure provider and handles that data under its own terms.