Privacy policy of What's that flower?

Updated 17 October 2026

This policy explains what the What's that flower? app for Android and iOS (sk.ab.herbs) does with personal data. The app is provided by Adrian Benko. You can write to support@whatsthatflower.com.

Account

You can use much of the app without an account. An account is needed for some features, including saving finds to your account, naming plants from photos beyond the free allowance, and subscriptions.

You can sign in with an email address and password, with Google, with Apple, or with a phone number. We receive the identifier that service gives us, which may include your name, email address, or phone number. We store that account in Google Firebase Authentication. We do not receive your password from Google or Apple.

You can delete the account in the app. Deletion removes the sign-in and the account record we keep for it. A find you already shared may remain until you delete that find.

Finds you save

When you save a plant you have seen, we store the plant name, the date, any note you write, and any photo you attach. If you allow location and a place is available, we also store the latitude and longitude of that find. Private finds stay on your account. Private photos are stored so only that account can read them.

If you choose to share a find, we copy the plant name, date, place, and photos into the shared list and mark them for review. The note is not copied. The shared entry does not show your name. The entry is still tied to your account so you can withdraw it. Photos you share are published under the CC0 dedication described in the terms.

Naming a plant from a photo

When you ask the app to name a plant from a photo, the photo is sent to our server and then to Plant.id, operated by Kindwise, which returns possible names. That request is used to name the plant. It is not added to the public catalog. If you then save the find, the photo is kept as described above.

A signed-in account has a monthly allowance of names. We store the count of names used, and a hash of a recent photo so the same photo is not submitted again within a day. The hash is not the photo.

Location

Location is optional. If you allow it, the app uses it to record where you saw a plant and to set the floristic region of a list. We do not sell that place, and we do not use it ourselves to choose which ads you see.

Advertising

The app shows ads through Google AdMob. AdMob may also request an ad from Meta Audience Network. The ad networks may receive an advertising identifier: the Android advertising ID, or, on iOS, the Identifier for Advertisers if you allow tracking. On iOS they may also receive an install-conversion signal through Apple's SKAdNetwork. That signal does not include your name or account.

In the European Economic Area, the United Kingdom, and Switzerland, the app asks for your consent before ads are personalized. The question is Google's certified consent message. You can consent or manage options, including refusing. If you do not consent, the app can still show limited ads that are not based on your advertising profile.

After you have made that choice, open You and choose Ad privacy choices to change it or withdraw consent. Withdrawing consent does not affect ads already shown. You can also refuse tracking in iOS Settings, and you can reset or delete the advertising ID in Android settings.

If you watch a rewarded ad to gain an extra photo name, AdMob tells our server your account id and that the ad was completed. We use that only to add the name. We do not send your plant photos to the ad networks.

Analytics, crashes, and notifications

We use Google Analytics for Firebase to see which screens are used and how the app performs. Firebase Analytics follows the same consent choice as ads. In the European Economic Area, the United Kingdom, and Switzerland, it stays off until you allow that choice. You can change it under Ad privacy choices. Outside those places, Firebase Analytics is on by default. We use Firebase Crashlytics to receive crash reports, including the device model, the operating system, and the state of the app at the crash. These are used to operate and improve the app.

If you allow notifications, we store a Firebase Cloud Messaging token for the device and subscribe it to the language you use, so we can send a notice when new plants are added. You can turn notifications off in the system settings.

Purchases

Subscriptions and other purchases are paid through Google Play or the App Store. Those stores handle the payment card. We store which product ids the account owns so the app can unlock the matching features.

How long we keep data

Account data and private finds are kept while the account exists. You can delete a find, and you can delete the account, in the app. Shared finds stay until you delete them or we remove them after review. Analytics and crash data are kept by Google under its own retention. Ad choices are stored on the device by Google's consent tools until you change them or remove the app.

Your choices and rights

If the GDPR applies to you, you can ask to see, correct, or delete your personal data, to restrict or object to processing, and to receive data you provided in a portable form. You can withdraw consent at any time. You can also complain to the data protection authority where you live. To use these rights, write to support@whatsthatflower.com.

The app is not directed at children under 16. We do not knowingly collect their personal data. If you believe we have, write to us and we will delete it.

Who else processes data

Their own privacy notices describe how they process that data.