Greenly — Privacy Policy

Last updated: 25 September 2026

Greenly ("the app") helps you grow vegetables, herbs, berries, houseplants and flowers: a care calendar, reminders, photo identification and diagnosis, a journal and weather warnings. This policy explains what data the app uses, why, where it goes and how to delete it.

The app is published by Greenly Garden ("we"). Contact: publicsomeday@gmail.com.

The short version

• You can use the app without an account. Your garden, calendar and reminders work on the phone, even offline.
• We do not sell data, show ads or use an advertising ID.
• Photos you send for identification or diagnosis are sent to our server and plant-recognition and AI services to get an answer. We do not keep the photo on the server.
• Usage statistics and crash reports are sent only if you say "yes" when asked. You can change your answer in Settings.
• You can delete your account and all its data from the app: Settings → Account → Delete account and data.

What we collect and why

Your garden

Places, plants, tasks, journal entries, notes and diagnosis results. They are stored on your phone. To back them up and to sync them between your devices, the app also stores them in our cloud database (Supabase), linked to an account: an anonymous one created automatically, or the one you sign in to. Journal photos are uploaded to private cloud storage that only your account can read, and so are photos attached to notes.

Email address

In the app, only if you sign in with Google: Google tells us the address of your account, and it is used to sign you in. Partners of the referral programme sign in to their page on the site with a code sent to their email. We do not send newsletters.

Location

Approximate location (the app asks for coarse location only), or a city you type in. It is used to:

• show the weather forecast and frost and heat warnings: the coordinates are sent from your phone to Open-Meteo;
• work out typical frost dates for your area: the coordinates are sent to our server, rounded to a grid cell of about 25 km, and the frost dates for that cell are stored without any link to you;
• find a city you type in: only the typed name is sent to Open-Meteo;
• name the place the phone found ("Odesa, Ukraine"): the coordinates go to the phone's own geocoding service (on most phones Google's, part of Android).

The app does not track your location in the background and does not keep a location history.

Photos and questions

When you identify a plant, diagnose a problem or ask a question, the photo or the question text (with the plant, its environment and stage, and optionally your region) is sent to our server. The server passes it to the Pl@ntNet plant identification service and to one of the AI providers listed below, and returns the answer.

• The server does not store the photo. It keeps a fingerprint (hash) of the photo and the answer, so the same photo is answered again without a new request. The answer is not linked to you.
• Your diagnosis results are saved in your garden (see above).
• The AI providers receive the photo or text without your name, email or account.

Purchases

If you subscribe or buy a scan pack, Google Play handles the payment. We receive a purchase token and check it with Google to know until when your premium lasts or how many scans to add. We never see your card details.

Invitations

If you invite friends, your account gets an invitation code. If you install the app from someone's invitation link, Google Play passes that code to the app once, on the first start (the "install referrer"), and the app sends it to our server so the invitation counts. Nothing else is read from it, and no advertising data is involved. The person who invited you sees only how many of their friends joined and subscribed, never who you are.

Statistics and crash reports (only with your consent)

At the end of onboarding the app asks once whether it may send usage statistics and crash reports. Nothing is sent until you answer "yes". If you do, Firebase Analytics receives seven kinds of events: onboarding finished, plant added, task done, identification used, diagnosis used, subscription screen shown, subscription started. The events carry only fixed values, such as "greenhouse" or "watering", and never text you typed. Firebase Crashlytics receives crash reports: device model, Android version and the technical details of the crash. You can turn this off at any time in Settings → Data. Turning it off also deletes the app's analytics ID and any unsent reports.

The app does not read the advertising ID. It does not use Google's ad attribution or install referrer.

Who processes the data

| Service | What it receives | Why | |---|---|---| | Supabase (database, sign-in, storage, server functions) | your account, garden, journal photos, requests to the server | storing and syncing your data, running identification and diagnosis | | Open-Meteo | coordinates, or a typed city name | weather, frost dates, city search | | Pl@ntNet | plant photo | identifying the plant species | | AI providers: Hugging Face, Groq, Nebius, NVIDIA, Requesty, unorouter, Google Gemini, AnyAPI, Mistral, OpenRouter | plant photo or question text, the plant and its conditions | identification, diagnosis, answers to questions | | Android geocoding service (Google on most phones) | coordinates found by the phone | the name of the place | | Google Play | purchase token | subscription | | Google (Firebase Analytics, Crashlytics), only with consent | events and crash reports described above | improving the app and fixing crashes | | Google Sign-In, only if you choose it | your Google account email | signing in |

Each service processes the data under its own privacy policy. Some of them are outside your country. Data is sent over encrypted connections (HTTPS).

Plant pictures in the catalogue come from Wikimedia Commons. Plant descriptions come from Wikipedia, Wikidata, GBIF, iNaturalist, Open Plantbook and Perenual. The app downloads these pictures and texts; it sends them nothing about you. When you search for a plant that is not in the catalogue, the name you typed goes to our server, which looks it up in these sources and adds the plant to the catalogue for everyone.

How long we keep data

• Your garden and journal stay in the cloud until you delete them or delete the account.
• If you cancel a subscription, your data stays and can still be read.
• Deleting the account removes the account, the garden and all journal photos from the cloud, then clears the app on the phone.
• Anonymous frost dates per grid cell and cached answers are kept without any link to a person.
• Analytics data is kept by Firebase for the retention period set in the Firebase console (2 to 14 months).

Your choices and rights

• Use without an account. Nothing is required to start.
• Delete everything. Settings → Account → Delete account and data. It needs an internet connection. If you cannot use the app, write to publicsomeday@gmail.com and we will delete your data.
• Export. Settings → Data → Export data gives you your plants, tasks, journal and diagnoses as a file.
• Consent. Turn statistics and crash reports on or off in Settings → Data.
• Location. You can refuse location access and type a city instead, or withdraw access in Android settings.

Depending on where you live (for example in the EU/EEA, the UK or California), you may have the right to access, correct, delete or port your data, and to object to or restrict its processing. Write to publicsomeday@gmail.com. You may also complain to your data protection authority.

Children

The app is not directed at children under 13, and we do not knowingly collect their data.

Health and safety

Diagnoses and treatment suggestions are reference information, not professional advice. Follow the label of any product you use.

Changes

If this policy changes, the new version will be published at this address with a new date.