Privacy Policy

We collect only what we need to run the app for you:

• Account info: the email address you sign up with, or the unique ID provided by Apple or Google when you use those sign-in options. Plus an optional display name and profile photo you choose.
• Gardening data: the gardens, plants, areas, placements, journal entries, harvests, and seed inventory you create. This is your own record, scoped to your account.
• Location info:if you enter a zip code, we use it to look up your USDA hardiness zone and frost dates so we can schedule your planting tasks. We don't track your real-time location.
• Photos: any images you attach to journal entries or plant records. These are stored privately, scoped to your account.
• Settings: display preferences (units, theme) and task completion state.

• We don't run ads.
• We don't sell your data. To anyone. Ever.
• We don't run advertising or cross-site tracking SDKs, and nothing we collect is used to build a profile of you or follow you to other sites. We do record a fixed set of usage events — see “How the app is used” below for the full list, and how to switch it off.
• We don't access your device contacts, calendar, microphone, or real-time location.

We record a small, fixed set of events about how the app is used, so we can tell a feature nobody wants from one nobody can find. It is tied to your account, and you can switch it off.

This is the complete list of what is recorded:

• Reaching, completing or skipping a step of the setup guide.
• Starting the season-planning flow, saving a plan from it, and whether it found anything you still need.
• The first time you add a plant, create a garden, or plant something in a bed.
• Opening the layout editor, marking a task done, logging a harvest, generating or applying a garden plan, and running an export.
• Following a link to the shop, adding something to the cart, and starting checkout.
• Being shown an upgrade prompt, and tapping one.
• Signals that something did not work: a search that returned nothing, an empty screen, or returning to a screen without doing anything on it.
• Opening a screen and leaving again within a few seconds without doing anything on it — which screen, nothing else.
• Opening a form, typing something into it, and leaving without saving — which kind of form (a plant, a garden, a journal entry, and so on), never what you typed.

No content from your garden is ever included. Not plant names, not varieties, not notes, journal entries, photos, or search terms. Not which garden, bed or plant an action involved. An event records that something happened and, at most, which kind of task it was — never what you grow.

That is enforced in the code rather than by policy: event properties can only take values from a fixed list, so there is no field a plant name could be put into.

We create no new identifier for this — no advertising id, no session id, no device fingerprint. Events are stored under your own account in the same database as the rest of your data, which means you can read them and they are deleted with your account. Signed out, nothing is recorded at all.

You can turn this off in Settings. It is per-device today, so switching it off on your phone does not switch it off on your laptop.

Your data is private by default. Nothing you create is visible to anyone else unless you deliberately share it.

You can create a read-only linkfor one specific garden or one specific garden plan. Anyone holding that link can view it in a browser without an account, and can never change anything. A link covers only the one garden or plan you made it for — not your account, and not your other gardens.

A shared link shows:

• For a garden: its name, its beds and pots and their sizes, what is planted in each, and the planting schedule for the current season.
• For a plan:the plan's crops, quantities, category coverage and written rationale.

A shared link never shows:

• Your journal entries, photos, or harvest log.
• Notes you've written on a garden or on an individual planting.
• Your location — no zip code and no hardiness zone.
• Your name, email address, profile photo, or account identifier.
• The answers you gave the Garden Plan wizard, such as household size or dietary preferences.
• Which tasks you have marked done, and anything from your other gardens.

The link itself is the only thing protecting what it points at. It contains a long random code, it is not listed anywhere, and we ask search engines not to index it — but anyone you send it to can forward it to someone else. Treat it like a password, and share it only with people you would show the garden to in person.

You can see every link you have created, and switch any of them off, at Settings → Shared links. Revoking a link takes effect immediately: the next person to open it sees a “this link has been turned off” page, not your data. Your links are also deleted when you delete your account.

Opening a shared page is recorded the same way as a visit to any other page on our site. We don't ask viewers to identify themselves, and we don't tell you who has opened your link.

Your data is stored in Google Firebase (Firestore for structured data, Cloud Storage for photos, Authentication for accounts). Firebase is a Google Cloud product. Their security and privacy practices apply on top of ours; you can read theirs at firebase.google.com/support/privacy.

Firestore security rules ensure each user can only read and write their own records. The one exception is a read-only share link you create yourself, described above: that is served by our own server, which reads only the specific garden or plan the link names and sends only the fields listed above. We never access your gardening data manually unless you ask us to (e.g. for a support request).

• Firebase (Google) — authentication, database, file storage, and serverless functions.
• Open-Meteo — weather forecasts. We send a latitude/longitude derived from your zip code; we do not send any account info.
• OpenAI — used to power some Premium features (Garden Plan, Insights, plant autofill). When you trigger one of those features, we send the inputs needed for that specific request (e.g. your plant kind and growing zone). We do not send your photos, journal text, or email address.