Privacy policy

Last updated 6 September 2026

We collect as little as we can:

• Waitlist: your email address, your selected interest tier, an optional 4-digit postcode, and — only if you tick the optional box — a single yes flag saying you have or would consider a home weather station or garden thermometer. If you leave that box unticked, nothing about it is sent or recorded at all: your answer is simply absent, and we treat absence as not interested. Stored in a locked database (insert-only from the public form; not readable via the public key). Used only to send one launch email, to prioritise which climate zones we build first, and — for the yes/no station flag — to decide whether a feature that reads your own sensor is worth building at all. The flag is a boolean; we never ask for, receive, or store any reading from a device you own. Never sold or shared. Delete-on-request: email us and we remove your row, the station flag included.
• Free app: the app works without an account. Your garden profile (location label, climate zone, growing conditions, preferences) is stored on your device, not on our servers. If you type a plant name the reviewed catalogue does not carry, the app tells you so and records nothing.
• No tracking. The waitlist page has no analytics, ads or pixels, and nothing on it profiles you. It is not, however, a page that talks to nobody: submitting the form sends your email, your interest, your optional postcode and the station flag (only if you tick it) to our database, which is hosted by Supabase. That request is the only one the page makes on your behalf. We do not sell what it sends. Email hello@gardnery.com to have your row deleted.
• Purchases. When the “My Garden” subscription is available it is bought through Apple’s App Store or Google Play, and they take the payment and hold the billing relationship under their own privacy policies. We never see a card number, a billing address, or your store account. All the app keeps is a flag on your device saying whether a subscription is currently active, which product it is, and when the store last said so. That flag is stored in the app’s own settings on the phone, it is never sent anywhere, and it is deliberately left out of the backup file the app can export.
• Reminders. If you turn reminders on, the notifications are built and scheduled on your device from the plantings you added. Nothing about them leaves the phone and there is no push service.
• Gardnery’s own code still makes no network request. Everything the app answers with is in the app. Subscriptions are handled by Google Play Billing on Android and StoreKit on iOS; those libraries talk to Google Play and the App Store, and on Android that is why the app carries the internet permission. There is no account, no analytics SDK and no advertising. Those store libraries are in the binary even in this free preview, where nothing is on sale: on Android a Google transport library bundled with Play Billing may send its own diagnostics to Google, and we neither receive nor read that traffic.
• Your device’s own backup. The app keeps your profile, plantings and ticked tasks in the phone’s ordinary app settings, and Android’s Auto Backup is left on for exactly that one file (allowBackup is true and the backup rule set in the app names FlutterSharedPreferences.xml and nothing else). So Google’s backup — or iCloud’s, on an iPhone — may copy those settings off the device to your own cloud account. That is the operating system’s backup under its own privacy policy, not a Gardnery server; we cannot read it, and you can turn it off in your device settings. The diagnostics log is deliberately outside that rule and is never backed up.
• “Report a problem”. The app writes a short local log of recent errors. It leaves the device only if you open the report yourself and pick a destination in your phone’s share sheet — it holds recent error text, the app version and the device type, and it does not contain your garden.
• If we add accounts later, this policy will be updated first, and the new collection will be spelled out before it starts.

We are an Australian operation; data is hosted with Supabase (database) and Vercel (website), and those providers may store waitlist and website data outside Australia. We use them only to run the waitlist and this site. Complaints: contact us first at hello@gardnery.com; you may also contact the OAIC (oaic.gov.au).