Privacy Policy
Last updated: 13 November 2026
This privacy policy applies to the app “Leafy – Plant Care” and to this website. It explains which personal data we process, for what purpose, and what rights you have.
1. Controller
foodsoption UG (haftungsbeschränkt)
Dördelweg 24, 58638 Iserlohn, Germany
Represented by: Johannes Schmidt
Email: support@heyleafy.app
We have not appointed a data protection officer; we are not legally required to do so.
2. Overview of processing activities
Types of data processed
- Master data (email address, name if provided by Sign in with Apple or Google)
- Content data (photos of your plants, plant names, watering intervals, notes)
- Friends feature data (display name, avatar colour, invite codes, friendships, bonus plant, stickers and messages, reports and blocks)
- Promo code data (code redeemed, number of bonus plants, time of redemption)
- Usage data (features used, timestamps, in-app events)
- Meta, communication and process data (device and push identifiers, IP addresses)
- Contract data (status of your subscription)
- Ad measurement data (events such as opening the app, advertising identifiers) — only in app versions before 2.0; from Leafy 2.0 measurement is switched off (section 15)
Categories of data subjects
- Users of the Leafy app
- Visitors of this website
- People who contact us
Purposes of processing
- Providing the app and its features (identification, watering schedule, reminders, diagnosis, friends)
- Managing accounts and authentication
- Processing and managing subscriptions
- Security, troubleshooting and improving the app
- Preventing misuse of the friends feature (reporting, blocking, word filter)
- Redeeming promo codes and evaluating how many redemptions and purchases result from the codes and campaign links of creators, shops and the press (section 16)
- Measuring the success of ads on Facebook and Instagram — only in app versions before 2.0; switched off from Leafy 2.0 (section 15)
- Answering support requests
3. Legal bases
Below is an overview of the legal bases under the GDPR on which we process personal data. In addition to the GDPR, national data protection rules may apply in your or our country of residence. Where more specific legal bases apply in an individual case, we state them in the relevant section.
- Consent (Art. 6 (1) (a) GDPR) — you have given consent to the processing for one or more specific purposes.
- Performance of a contract and pre-contractual requests (Art. 6 (1) (b) GDPR) — processing is necessary to perform a contract with you or to take steps at your request prior to entering into a contract.
- Legal obligation (Art. 6 (1) (c) GDPR) — processing is necessary for compliance with a legal obligation to which we are subject.
- Legitimate interests (Art. 6 (1) (f) GDPR) — processing is necessary for the purposes of our legitimate interests, provided your interests or fundamental rights do not override them.
4. Security measures
Taking into account the state of the art, implementation costs and the nature, scope and purposes of processing, we implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk.
These include in particular encrypted transmission of all data (TLS), storage of plant photos in a non-public storage area, database-level access restrictions (row level security) limited to your account, as well as procedures ensuring the exercise of data subject rights and the deletion of data. Whatever you share through the friends feature reaches your friends only through server functions that check the friendship and your sharing settings on every request.
5. Transfers and international data transfers
As part of our processing we share data with service providers that support us in operating the app (see the sections below). We conclude the legally required data processing agreements with these recipients.
From Leafy 2.0 the app transmits no data to Meta (Facebook, Instagram): ad measurement is switched off. Older app versions (before 2.0) transmit data to Meta in order to measure the success of ads. Meta is not a processor in this context: we and Meta are joint controllers for the collection and transmission (section 15).
Where we process data in a third country outside the EU/EEA or transfer data there, we do so only in accordance with legal requirements — based on an adequacy decision (Art. 45 GDPR), standard contractual clauses (Art. 46 (2) (c) GDPR) or your explicit consent. Several of the providers listed below are certified under the EU-US Data Privacy Framework.
6. Your rights
As a data subject you have the following rights under the GDPR:
- Right to object: you have the right to object at any time, on grounds relating to your particular situation, to processing of your personal data based on Art. 6 (1) (e) or (f) GDPR. Where your data is processed for direct marketing, you may object at any time.
- Right to withdraw consent: you may withdraw consent you have given at any time with effect for the future.
- Right of access: you may request confirmation as to whether we process data concerning you, access to that data and a copy of it.
- Right to rectification: you may request the completion or correction of inaccurate data.
- Right to erasure and restriction of processing: you may request that data concerning you be erased without undue delay, or that its processing be restricted.
- Right to data portability: you may receive the data you provided in a structured, commonly used and machine-readable format.
- Right to lodge a complaint: you have the right to lodge a complaint with a supervisory authority, in particular in the member state of your habitual residence, place of work or the place of the alleged infringement.
To exercise your rights, an email to support@heyleafy.app is enough.
7. This website
This website is a purely static information page. It sets no cookies, embeds no analytics or tracking services, loads no external fonts and uses no contact forms. A cookie banner is therefore not required.
When you visit the site, our hosting provider processes technically necessary access data (server log files): IP address, date and time of access, page requested, amount of data transferred, referrer, and browser and operating system information. This data is required to deliver the page and serves the security and stability of the service. Legal basis: legitimate interests (Art. 6 (1) (f) GDPR).
Hosting provider: IONOS SE, Elgendorfer Straße 57, 56410 Montabaur, Germany. The website is hosted on web space in a data centre within the European Union; a data processing agreement is in place with the provider. No transfer to a third country takes place.
Invite page for friends
Invite links from the app (section 11) lead to the address heyleafy.app/f/?c=… with the invite code at the end. This page is static as well. A script reads the code from the address in your browser only and puts it into the “Open in Leafy” button, which hands it to the app. The page does not connect to Supabase or any other service, does not store the code in your browser and shows neither the name nor any photos of the person who invited you. Whether an invite is valid is only checked by the app.
So that the code also arrives if you have yet to install Leafy: when you tap a store badge, the page puts the invite code — only the code, nothing else — on your device's clipboard. The link to Google Play also carries the code as a so-called install referrer, which Google Play passes on to the app after installation. How the app reads both on first launch is described in section 16 under “How a code gets into the app”.
Because the code is part of the address requested, it may — like any page requested — appear in our hosting provider's server log files described above. If Leafy is installed on an iPhone, the link usually opens directly in the app without the page being requested. The links to the App Store and Google Play lead to services of Apple and Google; their privacy notices apply there.
Campaign links and promo codes
Creators, shops and editorial teams we work with get their own link from us to the page heyleafy.app/app/?c=… (also as a QR code). The identifier at the end only names the partner, for example “cr-example”, and says nothing about you. It is also a promo code (in capital letters, e.g. CR-EXAMPLE) that gives you an extra plant in Leafy (section 16).
This page is static as well and does not measure anything itself: no cookies, no analytics or tracking services, no connection to Supabase or any other service, nothing is stored in your browser. A script reads the identifier from the address in your browser only, shows the code and inserts the identifier into the links to the app stores:
- iPhone and iPad: only when you tap a store badge does the page put the text “leafyapp://promo/CODE” on your device's clipboard (Safari only allows this after a tap) and open the App Store. The link to the App Store contains the identifier as campaign information. From this, Apple shows us aggregated figures per campaign in App Store Connect, such as page views, downloads and purchases, without any information about individual people.
- Android: the page redirects to Google Play right away. The link contains the code and the campaign (type of partner and identifier) as a so-called install referrer. Google Play passes this information on to the app after installation; in the Play Console we see aggregated figures per campaign, without any information about individual people.
- Computer: the page shows the code and both store badges with the same links; clicking a badge also puts the code on the clipboard.
How the app reads and redeems the code is described in section 16. Like any address requested, the identifier may appear in our hosting provider's server log files (see above). In the App Store and on Google Play, the privacy notices of Apple and Google apply.
8. App: account and sign-in
Using Leafy requires an account. Sign-in works via “Sign in with Apple” or “Sign in with Google”. We process the information provided by the respective service — usually an email address (with Apple optionally an anonymised relay address) and a unique user identifier. We do not store a password.
- Purpose: providing your account, associating your plants with it and backing up your data across devices.
- Legal basis: performance of a contract (Art. 6 (1) (b) GDPR).
- Providers: Apple Inc. and Google Ireland Limited — their privacy notices apply to the sign-in service itself.
9. App: backend and storage (Supabase)
Account, plant and care data as well as your plant photos are stored with our backend provider Supabase. Photos are kept in a non-public storage area; access rules limit access to your account. Photos you share through the friends feature are the exception (section 11).
If you choose which plants stay active without Leafy Pro (terms of use, section 6), we store that choice and when you made it; it is deleted together with your account.
- Provider: Supabase, Inc. You will find the provider's address and contact details in its privacy notice (link below); a data processing agreement is in place with Supabase.
- Storage location: the database and file storage are located in the region eu-west-1 (Ireland, EU).
- Third-country transfer: processing outside the EU is nevertheless possible, for example by server functions that run close to the respective device or through maintenance access by the provider; safeguarded by standard contractual clauses.
- Legal basis: performance of a contract (Art. 6 (1) (b) GDPR).
- Deletion: you can delete individual plants along with their photos in the app at any time. If you delete your account, we remove your account, all plants, photos, care and event data, your push identifier, your friends feature data and a redeemed promo code at Supabase. What remains with other providers afterwards is described in section 17.
- Privacy notice: supabase.com/privacy
10. App: AI identification and plant doctor (Google Gemini)
To identify the plant species automatically and for the doctor feature (assessment of possible problems), the photo taken is transmitted via our server to Google's “Gemini” AI interface (Gemini API) and analysed there. Only the image, the app language and — for the doctor feature — the plant name are transmitted. For a plant's care profile (such as watering and fertilising intervals) only its name is transmitted, no photo. No account or profile data: no user identifier, no name, no email address.
We use the Gemini API on a paid plan. Google processes the transmitted content as our processor and does not use it for training or for improving its own AI models and products. Under Google's terms, the content is logged only for a limited period in order to detect misuse and to meet legal obligations. We store the result of the analysis together with your plant at Supabase (section 9).
- Purpose: identifying the plant species, assessing possible problems (plant doctor) and creating the care profile.
- Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (or Google LLC, USA); a data processing agreement is in place with Google.
- Third-country transfer: processing may take place in the USA, safeguarded by standard contractual clauses and the EU-US Data Privacy Framework.
- Legal basis: performance of a contract (Art. 6 (1) (b) GDPR) and your consent by using the feature (Art. 6 (1) (a) GDPR).
- Note: the AI provides general, non-binding assessments and does not replace expert advice.
- Privacy notice: policies.google.com/privacy
11. App: friends
The “Friends” feature lets you connect with other Leafy users, view their plants and put stickers on their plants. Friendships are mutual: anyone who accepts your invite becomes your friend, and you both see each other's plants to the extent you have shared them. Friends can only view your plants, not edit them.
Leafy only creates a friends profile for your account once you use the feature — for example when you open “Invite friends” or “Friends & privacy”, accept an invite, or change your name or settings. As long as you neither share nor accept an invite, nobody sees this profile.
What data we process
- Display name: the name your friends see you by. It is prefilled with your first name from Sign in with Apple or Google (if none is available, with a generic placeholder name) and can be changed at any time under Settings → Friends & privacy (1–40 characters). Friends do not see your email address.
- Avatar colour: one of six colours, assigned automatically.
- App language: so that notifications to you are written in your language. Friends do not see it.
- Invite codes: the random code in your personal invite link, with its creation and expiry time. A code is valid for 14 days and can be invalidated immediately at any time with “Reset link”.
- Friendships: who is friends with whom, since when, and who accepted the invite.
- Bonus plant: if a new account accepts your invite, you both get one extra plant each, on top of the free plants. “New” means: the account was created after the invite code used, and you were not friends yet. Each person gets at most one such bonus plant. For this we store who received it, whether as the inviting or the invited person, the respective other person, the invite code used and the time. Only your own account can retrieve your entry. When the inviting person receives their bonus plant, the notification about the new friend points this out (section 12).
- Stickers: which sticker was put on whose plant, by whom and when, optionally with a short message (up to 140 characters).
- Sharing settings: your switches under “Friends & privacy” and the visibility of individual plants.
- Read status: when you last looked at the updates, so the app can count unread updates.
- Misuse prevention: the times of the stickers you have sent (no more than 30 within 24 hours) and a log of who removed whom as a friend and when. Both are used on the server only and are not visible to anyone in the app.
What your friends see
You control what your friends see under Settings → Friends & privacy. Confirmed friends see:
- your display name, your avatar colour and since when you have been friends;
- with “Show my plants” (default: on) your plants that are visible to friends — this can be switched off for each plant individually (default: visible). Shown are the photo, name and botanical name, the care status with details such as watering, fertilising and misting intervals and the time of the last care, the number of your visible plants and of their ongoing cuttings, and, in the updates, plants you add after your friendship began;
- with “Show history” (default: on) the history of these plants, i.e. entries such as watering and fertilising as well as progress photos and notes;
- with “Show diagnoses” (default: off) additionally the plant doctor's results including the photo;
- when you last added a visible plant or created a visible history entry;
- the stickers on your visible plants with the sender's name and avatar colour. The message attached to a sticker (up to 140 characters) is visible only to you as the plant's owner and to the sender. If you have allowed notifications, it also appears in the text of the notification to you (section 12).
With “Allow stickers and messages” (default: on) you decide whether friends may put stickers on your visible plants. Please keep in mind: whatever your friends can see, they can technically also keep outside the app, for example as a screenshot.
Photos: shared photos also remain in the non-public storage area. To display them, our server creates signed links that expire after two hours and hands them out only to confirmed friends — and only for photos that are visible according to your settings. The only exception are the preview photos of a valid invite (see below).
Invites
You invite friends via your personal link. Anyone who opens it while signed in to Leafy sees, in the app and before accepting, your display name, your avatar colour, the number of your visible plants and up to three photos of the visible plants you added most recently. Anyone who accepts the invite becomes your friend.
A link is valid for 14 days and can be used by several people until then — so only share it with people you want to have as friends. “Reset link” immediately invalidates all your previous links. Someone you remove as a friend can no longer use links you created before removing them. What happens when the link is opened in a browser is described in section 7.
If you install Leafy only after opening an invite link, the link itself does not reach the app. The app can then take the code once on first launch from the clipboard (iPhone) or from Google Play (Android), or you enter it on the sign-in screen. How this works is described in section 16 under “How a code gets into the app”.
Notifications
If you wish, Leafy notifies you when someone puts a sticker on your plant or accepts your invite. How this works and how to switch it off is described in section 12.
Reporting, blocking and word filter
Reporting: you can report people and sticker messages in the app — on the friend's profile via “…” → “Report”, or by long-pressing a sticker with a message on your plant. For a report we store who reported whom, the reason chosen, your optional text (up to 500 characters), for a sticker message a copy of the sticker and the message, the reported person's display name at the time of the report, and the time and processing status of the report. The copy remains even if the sticker itself is removed later. Only we can see reports, not other users; the reported person is not notified. Each account can file no more than 10 reports within 24 hours.
Email for every report: so that we can review reports promptly, our server sends us an email for every report. It contains the reason, the optional text, the display names and user identifiers of the reporting and the reported person, the sticker and message where applicable, the number of open reports against the reported person and the time. The email passes through our own mail server, which keeps a copy, and arrives in our support mailbox support@heyleafy.app at IONOS.
- Mail server: operated by Schmidt WebDev (mail.schmidtwebdev.de) on a server of IONOS SE, Elgendorfer Straße 57, 56410 Montabaur, Germany, in a data centre in Germany; emails are sent via IONOS's email service.
- Mailbox: support@heyleafy.app at IONOS SE (address as above; IONOS also hosts this website, section 7).
Blocking: if you block someone (friend's profile “…” → “Block”), we store who blocked whom and when. Blocking ends the friendship, deletes the stickers and messages between the two of you and, until you unblock the person, prevents a new friendship via old or new invite links, the preview of your invite, and stickers and notifications between you. The blocked person is not notified. You can unblock under Settings → Friends & privacy → “Blocked people”.
Word filter: our server automatically checks sticker messages and display names against a list of offensive terms. If there is a match, the message or name is rejected; a first name taken over from sign-in that triggers the filter is replaced by a generic placeholder name. The app checks in advance with the same list so that you see a hint right away.
Purpose, legal basis and storage location
- Purpose: providing the friends feature you want to use — invites, friendships, shared plants, stickers, updates and notifications.
- Legal basis: performance of a contract (Art. 6 (1) (b) GDPR).
- Bonus plant: granting the bonus plant to both sides of an invite and making sure that each person gets it only once. Legal basis: performance of a contract (Art. 6 (1) (b) GDPR).
- Misuse prevention: the times of stickers sent limit spam. The log of removed friendships prevents removed people from returning via old links and prevents repeated notifications after removing and re-adding a friend. Legal basis: legitimate interests (Art. 6 (1) (f) GDPR) in protecting our users and in secure operation.
- Reporting, blocking and word filter: moderating the friends feature and protecting our users from objectionable content and harassment. Legal basis: performance of a contract (Art. 6 (1) (b) GDPR) insofar as you use these features, and legitimate interests (Art. 6 (1) (f) GDPR) in secure operation and in protecting our users — also for the data of the reported or blocked person.
- Storage location: all friends feature data is stored with Supabase like the rest of your app data (section 9). The server functions that check sharing settings, create photo links, trigger notifications and filter texts also run there. The exception are the emails about reports (see above).
Retention and deletion
We keep your profile, settings and read status for as long as your account exists, and friendships until one of you ends them. In detail:
- Invites are valid for 14 days and cannot be used afterwards. Expired codes are deleted as soon as you get a new link; “Reset link” deletes all your previous codes immediately.
- Removing a friend ends the friendship for both of you and deletes it; you no longer see each other's plants. Stickers already placed stay on the plants: the plant's owner still sees them with the sender's name, avatar colour and message; other friends who may see the plant see them without the message. The plant's owner can remove any of these stickers at any time.
- Log of removed friendships: an entry of who removed whom and when remains until either of you deletes their account.
- Bonus plant: the entry remains even if the friendship ends, and is deleted together with your account. If the other person deletes their account, you keep your bonus plant; the reference to that person is removed.
- Stickers are deleted when the plant's owner or the sender removes them, when the plant is deleted, or when either of them deletes their account.
- Times of stickers sent: entries older than 24 hours are deleted with the next sticker you send, at the latest together with your account.
- Blocks remain until the blocking person unblocks or either of the two deletes their account.
- Reports are stored until the reporting or the reported person deletes their account. The email about a report and its copy on the mail server are not covered automatically; we delete them once the report has been dealt with, unless statutory retention obligations apply.
- Deleting your account (Settings → Delete account) removes your friends feature data: profile, friendships in both directions, invites, stickers you sent and stickers received on your plants, settings, read status, the times of stickers sent, all entries in the log of removed friendships that concern you (including those others created when they removed you), blocks you created or that exist against you, your bonus plant entry, and all reports you filed or that concern you.
12. App: notifications
So that Leafy can remind you to water your plants, we process a push identifier (token) for your device — provided you allow notifications. Delivery runs through Expo's push service and the system services Apple Push Notification service (APNs) and Firebase Cloud Messaging (FCM).
Leafy can also notify you when someone puts a sticker on your plant or accepts your invite (section 11). These notifications are triggered by our server. For this, we store your device's push identifier together with your account at Supabase and transmit it, along with the content of the notification — your friend's display name and, for stickers, also the plant name, the sticker and any message — to Expo's push service, which delivers it to your device via APNs or FCM. So that no more than one notification is sent per event, we store whether it has already been triggered. Push identifiers that Expo reports as no longer registered are deleted.
- Providers: Expo (650 Industries, Inc., USA), Apple Inc. (USA/Ireland), Google Ireland Limited (Ireland).
- Legal basis: performance of a contract (Art. 6 (1) (b) GDPR) and your consent by granting the notification permission (Art. 6 (1) (a) GDPR).
- Withdrawal: you can disable notifications at any time in the app or system settings. Notifications about stickers and new friends can also be switched off individually under Settings → Friends & privacy → Notifications.
13. App: subscriptions (Leafy Pro)
Leafy Pro is offered as an in-app purchase through the Apple App Store or Google Play. Payment is handled exclusively by the respective store — we receive no payment data such as card or account numbers.
To manage entitlements we use the service RevenueCat, which processes a pseudonymous user identifier, the purchase status and technical information about device and store.
A connection to Meta is set up at RevenueCat that can report purchases for ad measurement. It only transmits purchases for which the app has passed identifiers for Meta to RevenueCat. Leafy 2.0 passes no such identifiers to RevenueCat, because measurement is currently switched off (section 15).
- Provider: RevenueCat, Inc., 300 Delaware Ave, Wilmington, DE 19801, USA.
- Third-country transfer: processing in the USA, safeguarded by standard contractual clauses.
- Legal basis: performance of a contract (Art. 6 (1) (b) GDPR).
- Privacy notice: revenuecat.com/privacy
14. App: usage analytics
To understand which features are used and where people get stuck, we record individual product events inside the app — for example that onboarding was completed, a plant was added or the paywall was viewed. These events are stored in our own database at Supabase and associated with your account. We do not analyse the content of your photos, we build no advertising profiles from these events, and we do not pass them to third parties for analytics or advertising purposes. How we also use these events to evaluate promo codes is described in section 16.
Events sent to Meta are a separate matter: from Leafy 2.0 the app sends no events to Meta, ad measurement is switched off. Older app versions (before 2.0) report, among other things, the opening of the app to Meta (section 15).
- Purpose: error detection and improvement of the app.
- Legal basis: legitimate interests (Art. 6 (1) (f) GDPR).
- Objection: you may object to this processing at any time by email.
15. App: ad measurement (Meta)
The app includes Meta's (Facebook, Instagram) software development kit (SDK). It can be used to measure whether installations and purchases result from ads for Leafy on Facebook and Instagram. Leafy itself shows no ads — this is therefore not about personalised advertising in the app, but about the success of our own ads.
From Leafy 2.0: measurement switched off
From Leafy 2.0, ad measurement is switched off. This means:
- The Meta SDK is included in the app but is not started. We have switched measurement off via a switch on our server; as long as it is off, the SDK stays off.
- The app shows no “Ad measurement” dialog and no app tracking prompt (App Tracking Transparency).
- The app sends no events and no identifiers to Meta.
- The app passes no identifiers for Meta to RevenueCat (section 13).
- The advertising ID permission has been removed from the Android app.
Older app versions (before 2.0)
In app versions before 2.0, Meta's SDK is active. It can be used to measure the success of ad campaigns and to attribute installations; for this it reports, among other things, the opening of the app (event “app activated”) to Meta. On iOS devices, advertising identifiers (e.g. IDFA) are processed only if you have expressly agreed in the App Tracking Transparency (ATT) prompt. Without your consent, no such tracking takes place.
If you are still using an older version, please update Leafy to the current version — from Leafy 2.0 this measurement no longer takes place.
- Legal basis: consent (Art. 6 (1) (a) GDPR).
- Withdrawal: you can withdraw your consent at any time in your device's system settings (iOS: Settings → Privacy & Security → Tracking; Android: reset or delete the advertising ID) or update Leafy to the current version.
If we switch measurement on in the future
If we switch measurement on in the future, we will update this privacy policy beforehand. The following will then apply:
- Only with your consent: the app does not ask you on first launch, but on the home screen after you have added your first plant — in a separate dialog “Ad measurement” with the equally designed buttons “Allow” and “Decline”. Swiping the dialog away counts as declining. Leafy works the same either way. Without your consent the Meta SDK is not started and no data is sent to Meta.
- App tracking on iOS: only after you have chosen “Allow” in Leafy does the system additionally show its own prompt about app tracking (App Tracking Transparency) — provided you have not already decided on it.
- What the app transmits to Meta: the installation and opening of the app (“app activated”), the events “registration completed” and “upgrade page viewed” (with the place in the app from which you opened the page), an app identifier generated by Meta (Anonymous ID), device data (model, operating system version, language and time zone) and your IP address; on Android your device's advertising ID, on iOS the advertising ID (IDFA) only if you have additionally allowed app tracking. Meta never receives your plants or photos.
- Purchases via RevenueCat: purchases of Leafy Pro are not reported by the app but by RevenueCat (section 13), server-side via the Meta Conversions API — product, price, currency and time of purchase as well as subscription renewals. For this, the app passes Meta's Anonymous ID, device identifiers (on iOS the IDFV and, only if app tracking is allowed, the IDFA; on Android the advertising ID), your IP address and your email address (on iOS only if app tracking is allowed) to RevenueCat. RevenueCat passes the email address to Meta only in hashed form (SHA-256).
- Aggregated measurement: on iOS, Apple reports installations resulting from ads to the ad network via SKAdNetwork or AdAttributionKit, aggregated and without personal reference; Meta evaluates events in aggregated form via its Aggregated Event Measurement. If you open Leafy on iOS via a Leafy link, for example from an ad, the app passes this link to the Meta SDK only with your consent. Invite links from friends (section 11) are never passed on.
- Purpose and legal basis: measuring whether installations and purchases result from Leafy ads on Facebook and Instagram, evaluating the success of our advertising and optimising the delivery of our ads — based on your voluntary consent (Art. 6 (1) (a) GDPR and § 25 (1) TDDDG, the German Telecommunications Digital Services Data Protection Act).
- Withdrawal: at any time with effect for the future in the app under Settings → Privacy → “Ad measurement”. After that the Meta SDK no longer records anything, and the identifiers passed to RevenueCat (Meta's Anonymous ID, email address and, where applicable, advertising ID and IP address) are removed or no longer transmitted. On iOS you can additionally revoke the tracking permission under Settings → Privacy & Security → Tracking. The lawfulness of processing carried out before the withdrawal remains unaffected.
Provider, responsibility and third-country transfer
- Joint controllership: insofar as data goes to Meta (in older app versions or after measurement is switched on in the future), we and Meta are joint controllers (Art. 26 GDPR) for the collection of the data in the app and its transmission to Meta. This is based on Meta's joint controller agreement for its Business Tools (“Controller Addendum”): facebook.com/legal/controller_addendum. Meta is solely responsible for the subsequent processing. Under Art. 26 (3) GDPR you can exercise your rights against both us and Meta.
- Provider: Meta Platforms Ireland Ltd., Merrion Road, Dublin 4, D04 X2K5, Ireland.
- Third-country transfer: Meta may transfer data to Meta Platforms, Inc. in the USA, safeguarded by the EU-US Data Privacy Framework, under which Meta is certified, or by standard contractual clauses.
- Retention: how long Meta stores the data is governed by Meta's policies. We ourselves do not store any additional data for ad measurement.
- Meta's privacy policy: facebook.com/privacy/policy
16. App: promo codes and campaign links
Leafy works with creators, shops and editorial teams. They get their own campaign link with a promo code from us (section 7). Anyone who redeems such a code gets an extra plant (bonus plant) in Leafy, on top of the free plants. At the same time we see how many redemptions and purchases result from which code.
How a code gets into the app
A promo code reaches the app in one of the following ways. Since Leafy 2.1, invite codes from friends have also reached the app in the same ways (section 11).
- Android: on the first launch after a new installation, the app reads the Google Play install referrer once, i.e. the information the link to Google Play passed along (section 7). If it contains a promo code, an invite code or a campaign, the app takes this information over.
- iPhone and iPad: after a new installation, the app checks the clipboard once as soon as you have completed the onboarding (on the sign-in screen). If the clipboard contains text, iOS first asks you whether Leafy may paste; if you decline, the app receives nothing. The app only takes into account a promo link of the form “leafyapp://promo/CODE” and a Leafy invite code or invite link. It ignores any other content: it is neither stored nor transmitted.
- Entering it: on the sign-in screen you can enter a code yourself under “Have a code?”.
- Link: if you open a Leafy promo link (“leafyapp://promo/…”) while the app is installed, the app takes the code over directly.
If an account is already signed in on the device, for example after an update, the app reads neither the clipboard nor the install referrer. Until you sign in, the app stores a code it has found only on your device.
Redeeming
After you sign in, the app redeems the code via a server function at Supabase (section 9). For this we store your user identifier, the code, the number of bonus plants and the time of redemption. Each account can redeem a promo code only once. If a code is unknown or no longer valid, or your account has already redeemed a code, the app shows a notice and discards the code. After redeeming or a final refusal, the app deletes the code from your device. Only your own account can retrieve your redemption; other users do not see it.
Evaluation per code
So that we know which collaborations make Leafy better known, we evaluate per code how often it was redeemed and how many of the accounts that redeemed it then bought Leafy Pro, and with which plan. For this we link the redemption with the app's product events (section 14), such as the event for a completed purchase. These events also include the way a code arrived, whether it was redeemed or refused and — on Android only, once per installation — the campaign from the install referrer (type of partner and identifier). The revenue itself is kept at RevenueCat (section 13) under the same pseudonymous user identifier; for the evaluation per code we can combine the two.
Partners receive no personal data. Creators, shops and editorial teams do not learn from us who redeemed their code or bought Leafy Pro.
Purpose, legal basis and retention
- Bonus plant: redeeming the code, granting the extra plant and making sure that each account redeems only one code. Legal basis: performance of a contract (Art. 6 (1) (b) GDPR).
- Evaluation per code: measuring how many redemptions and purchases result from the collaboration with individual creators, shops and editorial teams. Legal basis: legitimate interests (Art. 6 (1) (f) GDPR) in measuring the success of these collaborations.
- Objection: you may object to this evaluation at any time by email.
- Storage location: redemptions and events are stored at Supabase (section 9); until you sign in, a code that has been found is kept only on your device.
- Retention: we keep the redemption for as long as your account exists. If you delete your account (Settings → Delete account), it is deleted together with your account and your event data.
17. Retention and deletion
We store your data for as long as it is necessary for the purposes stated or as long as statutory retention obligations apply. You can delete individual plants and their photos in the app at any time. The rules in section 11 also apply to friends feature data.
You can delete your entire account in the app under Settings → Delete account. This permanently removes your account, all your plants and photos, your care and event data, your push identifier, your friends feature data (section 11) and a redeemed promo code (section 16). Alternatively you can request deletion by email.
What remains: your purchase history remains stored at RevenueCat (under a pseudonymous identifier, section 13) and at Apple or Google. It is needed to process purchases and to meet statutory retention obligations. Deleting your account does not cancel an active subscription — you do that in your store's subscription management. Data that older app versions have already transmitted to Meta is stored by Meta according to its own policies (section 15). Section 11 applies to emails about reports.
18. Contact requests
If you contact us by email, we process your details in order to handle your request. The legal basis is the performance of a contract or pre-contractual measures (Art. 6 (1) (b) GDPR) and our legitimate interest in responding to enquiries (Art. 6 (1) (f) GDPR). We delete requests once they have been dealt with, unless statutory retention obligations apply.
19. Changes to this privacy policy
We adapt this privacy policy when the legal situation or our processing changes. The current version is always available on this page. We will additionally inform you in the app about material changes.
This English version is provided for convenience. In case of any discrepancy, the German version prevails.