Privacy

The short version: we keep as little as we can, and only what you hand us on purpose.

• No accounts. Nothing to sign up for, so nothing to breach.
• Your place stays with you. The city you choose and any checklist progress are saved in your browser's local storage on your device. They are never transmitted to us.
• Save code (optional, the one exception). Everything stays on your device unless you deliberately create a save code, which exists only so your place and garden can follow you to another phone or computer. When you do, that data, your station, town label, coarse coordinates, garden layout, and preferences, is stored on our server under a random code you keep. There is no name, no email, no account, and nothing that identifies you. The code is the only key: anyone who has it can read that one save, and you can delete it at any time by entering the code. If you never make a code, we still never have your data.
• Email (optional). If you ask us to email the almanac dates for your town, we store your email address and the town you chose, and nothing else. No name, no account. We use it only to send those dates, every email has a one-tap unsubscribe, and you can have your address deleted at any time. If you never give it, we never have it.
• Location button. If you tap "Use my location," your browser asks your permission, the coordinates are compared against the station list on your device, and they are not sent to or stored on any server of ours.
• Analytics. We use self-hosted, cookie-free analytics (Umami) to understand how the tools are used: page visits, how far down a page people read, which sections hold attention, which tools and buttons get used, and the words typed into the site search, so we can see which tools people look for and build the ones that are missing. This is measured as anonymous, aggregate events. So a returning visit can be told apart from a new one, your browser holds a single random id we generated and the date it was first set; they live on your device, identify a browser and not a person, are never linked to a name or account, and never follow you to another site. There are no logins, no advertising identifiers, no device fingerprinting, no cross-site tracking, and no sale of data, ever. We can see that a tool was used and whether a browser has been here before; we cannot see who used it, and nothing is ever tied to you as an individual.
• Why we measure it. So we can make the tools faster to use and the answers easier to find. If a section confuses people or a tool is hard to reach, the anonymous pattern tells us, and you get a better Almanac. That is the only use.
• Affiliate links. Where a page carries a clearly marked affiliate link or quote form, the destination site's own privacy policy applies once you leave. Forms on partner sites are theirs, not ours. We count clicks on outbound commercial links anonymously (which page, which link), so we can tell which pages help; the count carries no cookie, identifier, or anything tied to you. The rules these links live under are published on the funding page.
• Calendar files. ICS downloads are generated inside your browser. The events never touch our servers.
• Tool requests. If you use the Request a Tool form, we store the idea you typed and an optional note about what you would use it for, so we can build it. There is no name, no email, and no account, and your address is never written down. It is a suggestion box, nothing more.

Contact: see the about page. Last updated June 2026.