Privacy

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

• No account required. You can use the tools without creating an account. Email subscriptions, save codes, and submissions are optional.
• Your saved place. Your selected town and checklist progress are kept in your browser's local storage. An email subscription or save code also stores the location information needed for that feature.
• Save code (optional). A save code lets your place and garden follow you to another device. Creating one stores your station, town label, coarse coordinates, garden layout, and preferences on our server under a random code. Anyone with that code can read the save. Keep it private; you can delete the save by entering the code.
• Email (optional). We store your email address, town, weather station, edition, signup page and form, consent time, coarse country, and unsubscribe token. If campaign tags are present, we store their source, medium, and name with the subscription record. Active subscriptions and email delivery records are kept in private server storage. We use Brevo to deliver email and record delivery, clicks, bounces, complaints, and unsubscribes. Open counts can include automated privacy-proxy activity. Each email has an unsubscribe link; the confirmation removes your email and location from the active list. A hashed identifier and suppression status remain so an opt-out can be honoured. Restricted migration backups may retain historical records; contact us if you want those removed too.
• 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.
• Website usage. We use Umami and our own session records to understand visits, tool interactions, site-search terms, reading progress, referral sources, and errors. Browser storage holds a random browser identifier and first-seen date; session records include a random session identifier, visited pages, interaction events, device category, and coarse city, region, and country. These records are pseudonymous, rather than a promise of complete anonymity. Do not enter personal information into site search. The application does not store your IP address in these session records.
• Why we measure it. Usage information helps us find broken tools, improve navigation, and understand which pages bring people back. We do not sell personal data or use these identifiers to track you across unrelated websites.
• 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.
• Calendars. Downloaded calendar files are generated in your browser. Optional calendar subscriptions request a server-generated feed using the station and edition in its URL. Treat that URL as location information when sharing it.
• Submissions and enquiries. Tool requests, farm suggestions and claims, roadside-stand listings, feedback, sponsor enquiries, and recipe submissions are kept in a private review queue. We store the fields you submit, which may include contact details and photos, plus submission time and coarse country. Submitted contact information is used to handle the request. A recipe or listing is reviewed before publication; submitting a form does not publish your contact details automatically. The operator may receive a notification to review it.
• Service providers. Vercel hosts the site and its server storage; Brevo delivers email. These services process the information needed to provide those functions. Information you send to an external partner is governed by that partner's policy.
• Public field notes. A field note you post is public, including its text, display name, place, and posting time. Keep private contact information out of it.

For questions or a deletion request, use the contact details on the about page. Last updated September 27, 2026.