Verdalune Privacy Policy
Effective date: November 7, 2026
Verdalune is operated by DataNaat. For privacy, access, correction or deletion requests, contact info@datanaat.com. This policy describes the Verdalune V2 iPhone, iPad and Android apps and its connected services. Mandatory rights under applicable law remain intact.
We use information to provide the features you request and secure the service. We do not sell account or garden data, use garden content for advertising, or provide public profiles or a social feed. Optional product measurement requires your explicit opt-in, as described below. Garden reminders have no server delivery service. Optional local reminders and Apple’s silent CloudKit notifications are described below. Purchase records support subscription reporting as described below. An optional identification photograph is subject to the separate rights explained below.
1. Account, country and recovery
For email accounts, we process your email, password, chosen country and authenticated account identifier to create and secure access. Our account infrastructure handles authentication and stores a protected password representation; your country is an ordinary two-letter ISO profile field, not GPS data or a permission. With Apple or Google, we process its sign-in identifier and any email it provides, never the external account password.
Registration alone does not establish that you control a mailbox. Where the app requests email confirmation, account verification requires the provider-confirmed result, not just a submitted registration. Use an address you control and protect your password. Apple, Google and email accounts are not automatically merged. The authenticated account identifier, rather than an email address, owns account services and separates local gardens.
Password recovery is initiated only when you choose Forgot password. It may send a provider link to the requested address. Open it in the same app installation that initiated recovery; the app verifies it before accepting a new password. A request response does not prove inbox delivery. The website recovery page passes a one-use authorization code to the app only after you press its button; it does not collect passwords or exchange tokens. Hosting infrastructure receives the page request, including its temporary code. The page removes the query from visible browser history, uses no tracking or third-party script, and does not retain it in browser storage.
2. Local garden and personal photographs
Plants, personal places, notes, memories, symptoms, care history and personal or progress photographs are saved locally, separately for each authenticated Verdalune account; the signed-out garden is separate. On iPhone and iPad, you may explicitly enable iCloud sync in Options. It sends that account’s garden records, photographs, notes and care records to Apple’s private CloudKit database so supported Apple devices using the same iCloud account and the same Verdalune account can synchronize. Other Verdalune accounts and the signed-out garden are not merged. This iCloud feature does not synchronize with Android.
On Android versions with account cloud saving enabled, the app automatically saves the garden of your signed-in Verdalune account in private Supabase Database and Storage so supported Android devices using that same account can synchronize. This includes plants and their chosen images, personal places, notes and photographs, seed progress, care observations and review schedules, garden layouts, guided plans and saved drafts. The signed-out garden stays local until you choose to add it to your account; this transfer is offered when the account garden is empty and does not automatically merge two existing gardens. Other accounts are not merged. This Android service does not synchronize with the separate iCloud garden service.
Android cloud saving requires connectivity. Offline changes wait for reconnection and synchronization resumes while the app is open. Signing out stops that account’s synchronization on the device and is not account deletion. Concurrent edits may require review. A local confirmation alone does not prove that a remote copy exists. To help review conflicts, the app may keep up to 500 earlier versions on that device; acknowledging a conflict does not remove that local copy. These copies are removed when their related entity is deleted or the local account garden is erased.
Turning iCloud sync off stops further synchronization on that device; it does not delete existing local or CloudKit copies. Synchronization needs connectivity and available iCloud access, and changes made offline may wait for reconnection. Signing out is not account deletion. System and provider backups depend on their settings. Apple may deliver silent CloudKit notifications to refresh synchronized changes; this is separate from visible local care reminders.
Saving a personal or progress photograph does not send it for identification or prove growth, identity or disease. The app reconstructs the image without original metadata before saving or preparing an upload. Removing a plant or memory first removes its local record. A failed photo-file cleanup is retried when that garden is reopened; record removal is not a guarantee of immediate physical erasure. Copies you keep elsewhere must be managed there.
3. Optional photographs for identification
Each new photograph needs your separate affirmative choice before upload. A prepared image goes through our authenticated backend to Kindwise (plant.id), operated by FlowerChecker s.r.o., for plant identification. This V2 flow does not attach your email, name or weather area. The backend forwards the image and does not store the original; it records limited account-linked usage for access limits and security. You can search by name without submitting a photograph.
You keep ownership, but Kindwise’s standard API terms require a non-exclusive, unlimited and irrevocable image license. It may retain or modify the image, improve its AI, include images in other customers’ results and share them under Creative Commons Attribution-ShareAlike 4.0 or later. Send only photographs you may authorize and avoid people or private documents. Withdrawing consent stops future uploads but does not reverse earlier copies, uses or licenses. Kindwise makes submitted photographs, queries and results available to Verdalune through its API for six months. It states that end users’ personal data is anonymized six months after receipt. This period of availability and stated anonymization do not mean that photographs, copies or derivatives are deleted at that time, or that earlier licenses end. A suggestion is not a confirmed identity or diagnosis; you choose the plant before care becomes active.
When you view comparison photographs returned with a suggestion, the app loads them directly from the provider’s image CDN. That host receives the network request and may process your IP address and ordinary connection metadata. A web-search link opens Google only when you choose it; Google then receives that request and the search text. These actions are separate from uploading a new identification photograph.
4. Weather, payments and technical services
You may enter a city or choose a one-time approximate-location lookup. The app saves a weather area locally and requests a forecast using an approximate geographic cell. Its weather client does not attach your account identifier. For autocomplete city searches, the Verdalune backend and hosting infrastructure receive the entered search text and ordinary connection metadata. The backend sends the text to the paid Open-Meteo places service; the weather provider sees the proxy connection rather than your device IP in this flow. Forecast requests likewise use the Verdalune proxy and an approximate weather cell. A separate place-name lookup explicitly requested through the device may send the entered city or location to Apple on iPhone or iPad, or Google on Android. These device services may receive the device connection metadata. None of these lookups tracks movement in the background. Remove the area in Options or revoke device permission to stop its use. A personal place name or icon is organization, not a light, temperature or growing-method measurement.
Forecasts are shared by approximate weather area rather than fetched separately for each account. City-search caching stores a hash of the normalized search and language together with returned place results, not the original search text, account identifier or device IP. Successful place results are reusable for up to seven days and empty results for fifteen minutes; expired cache entries are removed during subsequent cache maintenance. This cache is separate from limited connection/security records.
Apple processes iPhone and iPad purchases through the App Store and StoreKit; Google processes Android purchases through Google Play Billing. RevenueCat receives your authenticated account identifier, purchase history and subscription or one-time purchase status to show, restore and verify access and provide purchase reporting. Restoration preserves the license association with the original account; it does not transfer your local garden or identification-credit wallet. Purchased identification credits have no expiry. Trial/Pro allowances and purchased-credit usage are recorded separately to enforce their UTC limits and avoid duplicate grants or charges; a disputed or uncertain balance remains under review until verified. This does not include your garden or photographs. We do not receive your full card number. The confirmed store offer governs price, period and any trial. No subscription benefit, free trial or price is guaranteed by this policy.
The connected services have these functions:
- Supabase Auth, Database, Storage and Edge Functions provide account authentication, profile country, account operations and service limits, private Android account-garden saving as described in section 2, receive voluntary proposals, and process optional product events as described below. Optional Apple-device garden sync uses private CloudKit.
- Apple provides Sign in with Apple, the device’s place lookup, App Store/StoreKit purchases on iPhone and iPad, and optional garden synchronization through its private CloudKit database and silent change notifications. Google provides Google sign-in, Android device place lookup and Google Play Billing purchases. The chosen device place lookup may process the requested city or location.
- RevenueCat verifies, restores and reports subscription and one-time purchase rights using the account and purchase information described above; original account association is preserved.
- Open-Meteo provides paid forecasts and city-search results through our backend proxy using the approximate weather cell or submitted search text. The proxy does not forward your device IP to Open-Meteo.
- Cloudflare Pages hosts the public website, recovery page and guest proposal challenge page. Cloudflare Turnstile verifies guest proposal interactions against abuse.
- Google Workspace/Gmail delivers operational proposal notifications from our backend to the Verdalune team. Those messages contain the submitted proposal details and reply email only if you supplied it. This server-side mail service does not connect to your personal mailbox.
Network services may receive IP address, time and limited request/error information for delivery, security and support. The app does not activate advertising identifiers. Optional Android advertising measurement with Google is described separately below. Copyable identification diagnostics exclude photos, credentials and email. Information may be processed internationally; contact us about applicable safeguards or your rights. We may disclose limited information when legally required or necessary to address serious fraud or security incidents.
For optional App Store review requests, the app keeps local usage days, saved-care identifiers and request-attempt history to limit interruptions. This bookkeeping is not sent to Verdalune or an analytics service, and it does not record whether a review dialog was shown or a review was submitted. Care ownership bookkeeping is cleared when the account context changes. Apple controls its own review interface and processing.
Optional local reminders
Care reminders are off until you enable them and grant the device notification permission where required. You choose a local time. Reminder preferences and scheduling stay on the device; this reminder feature does not send garden content or a push token to Verdalune or an external notification service. The operating system may display reminder text on the lock screen according to your settings. Disable reminders or revoke notification permission to stop them. Local scheduling and account ownership are handled separately from server-side operational proposal emails.
Optional promotional messages on Android
Supported Android versions offer an explicit choice to receive Verdalune news and offers. Some versions present care reminders, news and offers in one notice during initial setup. Explicit acceptance enables only the choices described there, with separate stored preferences that you can change in Options → Privacy and notifications. Earlier versions retain their individual controls. Existing refusals and withdrawals are respected. The device notification permission is still required. Google usage/ad measurement has its own consent, and promotional delivery can work while optional Analytics remains off. Buying, restoring and ordinary app use do not require promotional permission.
With this choice enabled, Google Firebase Cloud Messaging registers a Firebase installation identifier (FID) and processes the technical app/device information needed to deliver messages. Verdalune stores that delivery identifier, random installation and binding identifiers, the verified technical purchase owner, language, app version, consent version, last-known notification permission and timestamps. We use them to deliver a relevant promotion, prevent duplicate sends and check that the recipient is eligible. Google receives the delivery identifier and minimal campaign/delivery routing identifiers. This delivery flow does not send your garden, photos, email, complete receipts or purchase tokens to Google.
Our records distinguish selection, send attempts, FCM acceptance, the receiving app’s verification request, requests to display a notification and reported opens. A send acceptance or display request does not prove that you saw a message. A reported open does not prove a trial or payment. Confirmed purchases keep their separate store-verification rules. Messages can appear on the lock screen according to your device settings.
You can turn promotional messages off in the app or block notifications in device settings. The app stops showing new promotions when its choice is off. Server withdrawal is retained and retried if you are offline, so the server may learn about the change later. After an account change, a currently verified association is required before a promotion can be shown or opened. Access and deletion requests can be sent to info@datanaat.com.
The server clears the delivery identifier when it processes withdrawal or confirms invalidity. Daily cleanup removes delivery identifiers after 30 days without refresh. Registration and withdrawal proofs are removed after 90 days without activity once associated campaign records no longer need them. Campaign outcomes and their technical recipient/delivery identifiers are removed after 90 days past the campaign expiration date. Removal takes place on the first daily cleanup after these thresholds. Campaign copy and configuration can remain without personal recipient identifiers. Account deletion removes associated records when the verified account or linked technical identity is deleted; pending identity cleanup can delay completion. Google’s service data follows its own applicable processing terms.
Voluntary plant and feature proposals
If you choose to send a proposal, you provide its type (plant or feature), your message and, only if you enter it, a reply email address. A plant name, scientific name and country are optional details you choose to include. We do not automatically attach your account email, photographs or garden. We use this information to consider improvements and handle your request. Our protected Supabase backend stores the proposal before attempting to notify the Verdalune team through Google Workspace/Gmail authorized on our server. A saved proposal is not a promise of implementation, a date or an individual reply.
Authenticated submissions are linked to your account; guest submissions use an anti-abuse challenge. Limited technical data, including server time and request identifiers, protects the service. Account deletion includes linked proposals, their reply email addresses and traceable notification copies in the team mailbox we control. Guest or older submissions that cannot be linked safely to your account need a separate verified request at info@datanaat.com. We do not erase another person’s messages or copies outside our controlled mailbox.
Optional product and download measurement
Android usage analytics is off until you explicitly allow it. A new installation without a saved choice may offer “Allow analytics” and “Continue without analytics” during onboarding, with the detailed notice available before permission. Closing the notice, continuing without analytics, installing, updating or accepting general terms does not authorize collection. A prior refusal is preserved. In newer versions, review or change this choice in Options → Privacy and notifications. Earlier versions keep Privacy and legal → Usage analytics.
When you explicitly opt in, Android may send a pseudonymous random installation identifier and allowlisted product events to Verdalune through our Supabase service. These include the first app opening we observe, use of product features, purchase-flow steps and outcomes, app and Android version, selected plan and offer, normalized error codes and response timing, and normalized acquisition source. We use these events to understand product use, diagnose failures and measure campaign performance. A first opening is not a certified installation or proof of an advertising conversion. Google Play Install Referrer provides an observed source label; it does not prove your residence or identity. Only permitted source, medium, campaign and placement categories are retained, not the raw referrer URL. We do not use an advertising ID, fingerprint, garden content, photo, email, credentials or precise location for these events. We do not sell these internal measurement events. The separate optional Google measurement described below requires its own permission. If an event arrives with your verified signed-in account, it can be linked to that account. In Android 0.1.13 (build 17) and later, earlier guest observations are not retrospectively assigned: pending observations are discarded and the installation identifier is rotated whenever the account context changes, including the first sign-in from guest mode. Earlier Android versions with usage analytics can retain consented, unsent guest observations at the first sign-in and send them linked to the account signed in at that time. These are pseudonymous records, not anonymous data. After opt-in, the app may attempt or retry transmission even when the collector is unavailable. A disabled collector rejects these events without storing them; hosting services may still receive ordinary connection metadata.
We rely on your consent for this optional usage and campaign measurement. You can leave it off or withdraw consent without losing ordinary app access, care features or purchase rights. Turning it off clears unsent observations and the local installation identifier and stops future sends. It cannot recall a request already dispatched or automatically erase data already received; contact info@datanaat.com to request access or deletion. Withdrawal does not invalidate processing already performed with your consent. Raw app observations have a 90-day retention period and are removed by the next scheduled hourly cleanup; the installation binding is removed when no retained observation needs it, and account deletion removes associated observations and bindings. Daily aggregates without account or installation identifiers have a 365-day retention period and are removed by the next scheduled cleanup. Necessary account, purchase-verification, selected-promotion reservation and security records are separate service operations, continue independently of the analytics choice, and retain their own conditions described in this policy.
For app versions that use the new first-opening counter, we also keep a separate duplicate-prevention receipt containing only a random event identifier and its receipt time. It contains no account identifier, installation identifier, photograph or event payload. The receipt may remain after the related event or account has been deleted, solely to reject a replay of the same event without counting another opening or recreating the deleted observation. It is removed by the next scheduled cleanup after 90 days from receipt. Aggregate daily counts follow the 365-day retention described above. This counter still requires your optional analytics consent and does not measure every download or a verified number of people.
On the website, optional download measurement requires a separate unchecked choice for that page. It stores no visitor, session or installation identifier and uses no cookies or browser storage. It distinguishes a QR being visible, the QR destination being opened and a Google Play outbound action. Event identifiers exist only to reject duplicates for up to 24 hours; identifier-free daily download aggregates may remain for up to 365 days. The phone makes its own consent choice: we do not join a desktop visit to an individual phone or installation. The existing launch-form aggregate counters remain separate under their notice, including their 90-day retention. No raw URL, arbitrary referrer, form content, advertising identifier or network identifier is included in these event payloads. Hosting services still receive ordinary technical connection metadata. Delivery is best effort, and these counts do not measure unique people or completed purchases.
Optional measurement with Google
Only with your explicit permission, Verdalune uses Google Analytics for Firebase and Google Ads to measure Android usage and which ads lead to trials and purchases. Previous permission for internal metrics does not enable this feature. You can decline and keep caring for your plants, buying and restoring without signing into Verdalune.
Google receives a pseudonymous identifier for this app installation, permitted usage events and technical app and device information. Our server may send verified purchase facts: operation type, plan, date, original amount and currency, linked to a consented installation when that link is reliable. This measures advertising results; we do not send emails, passwords, garden content, photos, notes, complete receipts or purchase tokens. This integration does not enable ad personalization or the Android advertising identifier.
You can withdraw permission in the app. Optional device collection stops and the app asks our server to stop associated transmissions. Offline requests are retained and retried, so the server may receive the withdrawal later. An already transmitted request cannot be recalled. Records needed for purchases, security and access rights remain subject to their separate processing. Contact info@datanaat.com for access or deletion. This information is pseudonymous, not anonymous.
Google may derive approximate geography from connection information. We do not send precise location for this measurement. Acquisition geography, billing country and device language are different data sources. With permission, the SDK can also record app lifecycle and store purchase events automatically. Confirmed server records are used separately for our financial reporting.
Backend retention: the Google delivery payload is removed after 30 days; installation links and withdrawal capabilities after 90 days of inactivity; measurement proof records after 90 days; and event and subscription-chain records after 400 days. Cleanup runs with the existing scheduled job, not at the exact deadline. Account deletion includes this measurement data; necessary commercial records follow their separate rules. Google Analytics user-level and event-level retention is set to two months, without resetting on new activity. This setting does not limit standard aggregated reports or set a deletion deadline for Google Ads reporting.
5. Retention and account deletion
You can start account and associated server-data deletion through the web deletion page without reinstalling the app. It requires fresh sign-in, the appropriate password or Google/Apple identity proof and a separate confirmation. Google proof is checked against the linked Google identity; Apple uses an operation-bound authorization and required revocation checks. The service distinguishes verified removal of the sign-in account from completion of all associated cleanup. A submitted request or an HTTP success response alone proves neither. The web page reports full completion only after its required cleanup checks pass. Contact info@datanaat.com if you cannot sign in or need assistance.
The website keeps passwords, sign-in access tokens and the Google provider access token in browser memory, not persistent browser storage. A short-lived PKCE verifier and sign-in state are stored in the browser tab to complete authorization. A minimal protected deletion receipt (operation reference and private recovery capability) is kept in that tab’s session storage so you can check or resume the same operation after a connection interruption or after the sign-in account has been removed. Treat this receipt as private; it is not a public reference. It is cleared when you end the web session or clear the site’s browser storage, and server receipt access expires under the deletion-receipt rules below. The website cannot directly erase copies that exist only on your devices. For an enrolled iCloud garden, protected deletion markers let participating Apple devices stop further synchronization and remove the corresponding private CloudKit garden when they reconnect with the same iCloud account. An offline device, changed iCloud account or unavailable CloudKit can delay that process. Do not treat web account deletion as proof of immediate removal from every device or backup; manage independent copies separately. Store subscriptions and billing records are handled by Apple or Google and are not cancelled or erased by account deletion.
Account and linked service data are retained while the account is active. Once the sign-in account is removed, minimal protected operation records and provider targets remain as needed to finish pending cleanup. Full server-side cleanup includes linked proposals, purchase-ownership records, traceable proposal messages in our controlled mailbox and the RevenueCat customer record. Background retries continue without requiring the app to stay open, but provider failures or ownership checks can delay completion. Provider and system backups may have separate retention. Shared catalog and approximate weather data are not private account records.
Android cloud garden records and deletion markers remain until account deletion, subject to the deletion process described here. Synchronization operation receipts contain no garden content and expire after 30 days; server conflict records contain technical metadata only and expire after 180 days. These records are removed by bounded cleanup when that account synchronizes. Unreferenced uploaded photos are eligible for cleanup after 24 hours. Cleanup and disconnected devices can delay physical removal; independent copies saved elsewhere are managed separately.
Options → Delete account requires a connection, a separate confirmation and fresh identity proof using the appropriate password, Apple or Google method. After required proof checks, durable cleanup preparation, owned server-file removal and verified sign-in-account removal, the app can show “Account deleted”, sign out and erase that account’s garden, photographs, notes, care history and credentials on this device. Other accounts and the signed-out garden remain. This immediate local exit does not claim that every external copy is already gone: RevenueCat and controlled-mail cleanup can remain pending, and full completion is reported only after their removal and remaining server data are verified. A private receipt preserves status and recovery after sign-out; pending cleanup is also retried by the server. Before sign-in-account removal, a failed or unverified request must not be presented as an account deletion, and a retry may require fresh identity proof.
For enrolled iCloud gardens, the installation also keeps a private deletion-recovery capability. Supabase retains protected device/owner proofs and an erased-status marker, not garden content, to let an offline participating installation recognize a deleted account when it reconnects and prevent renewed uploads. These minimal markers are separate from the ordinary thirty-day deletion-status receipt; they can remain while needed for that offline-deletion protection and cannot restore the account or its garden.
A private receipt lets the app check and resume an interrupted deletion. Once deletion has started, the minimum information needed to finish it remains while the request is pending. After completion, status access lasts thirty days; limited receipt metadata is removed on the next cleanup after that period, not necessarily on day thirty. The receipt contains no password or photos and replaces the account identifier with a protected proof. A separate protected trial-use fingerprint expires thirty days after deletion. A protected purchase fingerprint prevents the same purchased credits from being granted again; it has no fixed expiry while those credits do not expire. It contains no account identifier, email, purchase amount or readable transaction identifier. These are pseudonymous technical proofs, not anonymous data; they cannot restore the account or its content. If Apple permission cannot be revoked, the app explains the separate manual step. Deletion does not cancel an Apple or Google Play subscription or erase store billing records, independent device copies, provider/system backups or previously licensed Kindwise images and their later uses. Participating iCloud copies follow the reconnection and account conditions described above. For access, correction or deletion requests, contact info@datanaat.com.
Deletion does not cancel a store subscription or necessarily recall previously licensed identification images, and cannot guarantee immediate erasure from offline devices or independent copies. Cancel renewal separately in the store. You may request access, correction, deletion or another applicable right at info@datanaat.com; we may verify identity before acting and explain the outcome. Sending a message is not confirmation that deletion is complete.
6. Security, age and changes
We use protected connections, account-based access controls and restricted service credentials, but no system is infallible. Verdalune is intended for people aged 13 or older. Where applicable law requires parental or guardian authorization for consent-based processing, that authorization is required before the processing takes place. Mandatory legal protections remain in force. If data handling changes, we update this policy and request a new choice when required. You may contact a competent privacy authority where applicable law gives that right.
iOS guest purchases and optional measurement
This section applies to iPhone and iPad versions that include these features and takes precedence over earlier descriptions of account identifiers or Apple-device garden contents where they differ. Other platforms and older versions retain their stated behavior.
In iPhone and iPad versions that offer guest purchases, you can view plans and buy without creating a named Verdalune account. Supabase creates a technical purchase identity with a random identifier; its session credentials stay in protected device storage. RevenueCat uses that same identifier to verify subscriptions, purchased credits and restoration. It does not receive garden photographs or notes through this flow. This identity has no ordinary account or cloud-database permissions and does not turn on garden synchronization or optional measurement.
If you later sign in, the service verifies both identities before linking purchase ownership. It keeps the original purchase ledger and prevents another account from claiming it. Linking purchase rights does not merge gardens. When an associated account is deleted, linked technical identities are also processed through the verified deletion workflow; an unavailable provider can leave cleanup pending. Limited protected anti-duplication proofs and store billing records remain subject to the retention and deletion limitations above.
With your explicit permission, supported iOS versions send a random installation alias, app/build and OS major versions, named screen/feature steps and success/error categories to our service. They do not include your email, account identifier, garden, photographs, messages, exact location or advertising identifier. Changing accounts rotates the alias and clears unsent events; withdrawing permission stops collection and clears unsent events. The first-open count only covers eligible new installations with permission; it is not the App Store download total. Raw observations are kept up to 90 days and daily aggregates up to 365 days, with scheduled cleanup. These events never establish a purchase, subscription, trial or entitlement. Measurement remains independent of purchases and gardening features.
Optional iCloud synchronization can include supported plot layouts and positions, plant links and saved unfinished care responses alongside the garden records already described. Only compatible Apple versions participate. An unfinished response is not an observed care action and is never automatically submitted as one.