TRANSPARENCY & CONTACT
Privacy for Luma & Leaves
Current 1.22.2 notice and archive · updated 7 November 2026
Current: Luma & Leaves from version 1.17
The complete current app privacy notice, including version 1.22.2, is linked below. It covers local play and profile, optional email login, parental approval, cloud saves, scores, studio news, support and deletion.
Archive: versions through 1.16
The following descriptions apply only to older versions without the new online features. Statements about offline operation and no game server do not apply to current optional online features.
Scope and controller
This notice describes the planned data flow of update 1.14.0 (version code 24) for Luma & Leaves, package com.jtsrlab.lumaandleaves. The candidate has been built locally and is still undergoing final testing. This privacy notice does not confirm approval by Google or availability in the closed test or production. It covers local gameplay, including a local profile and user-initiated image sharing, optional email contact and voluntary external support. JTSR Bits and Bytes Lab is the studio name used by an individual. Controller: Jeruyaan Yogarajah, Germany. Contact: contact@jtsr-lab.com.
In simple words
Your garden and gameplay statistics stay on your device. The game does not send your save to us, does not require its own game account and contains no advertising or automated usage analytics. Gameplay works offline. The optional contact feature for adults and parents prepares a message in your external email app; you decide there whether to send it. Your reply email address and message may be processed for this purpose. The protected Google Play version may temporarily need internet access for installation and licence checks. Contact emails, website visits and Google Play are separate from local game storage. Voluntary support through PayPal is also planned for adults. PayPal processes its own data and JTSR may receive payment details. The local age check, external payment and local save are separate processes. An optional nickname and self-declared age group stay local. At your request, the game can hand an image of the game view to an app you choose; the image can show visible game progress. The local adult checks described below apply. The app has no online accounts, multiplayer features or Google age verification.
Request data deletion
Warning: Clearing app data permanently deletes your local save, including progress, garden, inventory, calendar and reward records, and settings. There is no cloud restoration. Follow the steps below only if you want to permanently delete these records.
Local game data can only be deleted on your device: Android Settings > Apps > Luma & Leaves > Storage > Clear data. Labels may vary by device. JTSR cannot access or remotely delete your local save. There is no server account that you need to ask us to delete.
To request deletion of voluntarily sent support emails, write to contact@jtsr-lab.com, preferably from the original sender address. Use the subject “Luma & Leaves – Datenlöschung” and identify the enquiry or email concerned, for example by its date or subject. Do not send unnecessary additional identity information or identity documents.
We delete the associated reply email address, sender address, message and technical email data, together with copies we manage, including any attachments and trash entries, unless legal obligations or specifically justified necessary retention grounds require us to keep them. Any data necessarily retained is deleted when that reason no longer applies. The existing policy remains unchanged: resolved support enquiries are manually deleted no later than six months after closure, subject to those retention grounds.
The game cannot delete drafts or email copies in your email app or held by your external email provider. Clearing local game data does not delete support emails held by JTSR; requesting email deletion does not delete a save on your device. To delete copies in your own account, use your email app’s or provider’s deletion controls.
For payment details JTSR has received following voluntary PayPal support, you may also contact contact@jtsr-lab.com and identify the payment with as little information as necessary. Payment records may be subject to legal retention requirements; the six-month support-email rule is not a general deletion period for these records. PayPal manages account and payment data held by PayPal. Clearing app data does not delete those external records.
For the local profile, use Settings > Your profile > Play without these details: this removes the nickname and age group while retaining progress. The local flag recording that the profile dialog has already been handled remains. To remove generated share images, clear the app cache in Android Settings. Clearing app data or uninstalling removes the profile and cache together with progress. The game cannot recall or delete images or copies already passed to other apps, services or recipients; use their deletion controls or contact options.
Local foreground time, the reminder threshold, any saved mute date and the minor-protection flag are removed by clearing app data or uninstalling, together with progress. “Play without these details” and clearing the app cache do not delete these records. The current daily counter is replaced when time is next recorded on a different local day; the mute date and protection flag have the longer storage periods described in the break-reminder section. JTSR holds no server-side copies of these reminder records.
What the app stores on your device
The private Android app area stores progress, stars, pollen, puzzle attempts with moves, hints and recorded attempt duration, plant colour pieces, inventory, object positions, orientations, land expansions, garden names, regions, weather choices, planting timestamps and settings. Custom size and the timed trail also store local mode, size, attempt and result records, together with rewards already granted. Plant colour pieces and pollen contribute to shared local progress. Timing a puzzle attempt is not a complete record of your overall play time.
The local calendar contains recorded visit dates, calendar stages, decisions about missed days and days recovered with pollen. Gift records contain a date, where applicable the original daily-puzzle date, gift type, stage, promised contents, opened status, exclusive ownership and outstanding entitlements. Historical gift records keep their contents. Visit gifts, recovered gifts and daily-puzzle rewards are distinguished. Statistics can count visit and recovery days saved since the visit calendar was introduced; earlier unrecorded visits are not estimated.
The pollen economy stores local credits, spending and already redeemed star-exchange entitlements. Star exchange counts only campaign stars and does not change level star ratings. Garden suggestions use owned objects and local garden arrangements. All these records support continuing gameplay, rewards and design on your device. Device time is used locally; the app does not access the device calendar or a time server.
The local save also includes markers and credits for one-time automatic visit pollen, stored fixed puzzle packages, and quantities, pollen deductions and inventory balances for multiple-item purchases in the garden shop. They support continued play and prevent duplicate rewards; no additional personal details are collected for them.
Optional local profile
In Settings > Your profile, you may enter an optional nickname and your age. Only a cleaned nickname of up to 20 characters, the derived age group (under 13, 13–15, 16–17 or 18 and over; unknown without an answer) and a flag recording that the profile dialog has been handled are stored in private app storage. Your exact age is not stored. These details support occasional personal greetings and control access to external actions, not advertising. They are not sent to JTSR or an account service. The age is self-declared, not proof of age or identity. Offline play is available without these details.
You can change the details in your profile. Saving with an empty age field keeps a previously stored age group. “Play without these details” removes the nickname and age group, while retaining your progress and the flag recording that the profile dialog has been handled. Input fields are cleared when the dialog closes. Clearing app data or uninstalling also removes the locally stored profile details. In addition, a self-declaration below 18 leaves the break-reminder protection flag described below stored locally; removing profile details does not delete that flag.
Local foreground time and break reminders
For break reminders, the app counts only its own time in the foreground, including time without continuous input. The puzzle and garden views use the same local records. Counting pauses when the app leaves the foreground. There is no access to other apps’ usage time, no permission to access their usage statistics and no analytics service. These time records are not sent to JTSR or a server. They are separate from individual puzzle-attempt durations and external platform reports.
Private app storage holds the last recorded local calendar day, the foreground duration counted for that day in milliseconds, the next reminder threshold and, if selected, the day for which reminders were muted. The default first reminder is scheduled after 30 minutes, with another after an additional 10 minutes of foreground time. Display waits for a suitable moment in the game. These intervals are a game option, not a universally applicable medical or legal screen-time limit; the game does not enforce a lockout.
A person aged 18 or over according to the local self-declaration can mute reminders for the day if no minor-protection flag has been set. No daily mute option is offered for an unknown age group or an age below 18. A self-declaration below 18 sets an additional local protection flag. It prevents the daily mute option from becoming available merely by raising the declared age later. Editing the profile or selecting “Play without these details” does not remove this flag. It is not verified proof of age, a parental role or consent.
When time is next recorded on a different local calendar day, the previous day’s counter and reminder threshold are replaced; no ongoing daily history is created for this purpose. The last chosen mute date can remain stored until the next such choice, even when it no longer takes effect. The protection flag remains stored locally. There is no promise that all these records are automatically deleted after 24 hours. Clearing app data or uninstalling removes them together with progress; clearing the app cache or removing profile details does not. There is no user account or server-side deletion action for these records.
Local adult check before sharing and contact
If the age group is unknown or below 18, the game asks you to hand the device to an adult before sharing or contact. Their day, month and year of birth are checked locally in working memory for an age of at least 18. They are not saved in progress, files or logs and are not passed to JTSR or the chosen app. The fields are cleared after a successful check or when the dialog closes. Invalid entries or entries below the required age remain in the dialog until it closes; the external action is not opened. This approval is not saved as lasting proof of age. For the self-declared age group of 18 and over, this additional check before sharing and contact is skipped.
This is not verified age assurance, proof of a parental role or verifiable parental consent. No identity documents or Google age verification are used. Form saving, autofill and content capture are disabled for the input fields; the keyboard and operating system have their own processing rules. The separate adult check for voluntary PayPal support still applies independently.
Sharing game views at your request
When you choose “Share” and complete any required local adult check, the game creates a PNG image of the current puzzle, flower or garden view. The Android chooser passes the image, the app name and the fixed Google Play link to the app you select. The game publishes nothing automatically and sends nothing directly to JTSR during this action. Your local nickname and custom garden name are hidden in the capture. Visible game progress may be included. Review the image, chosen app and recipient before sending; the chosen app may handle text and images differently and processes the supplied data under its own rules.
The image file is held in the private app cache under shared-scenes. A FileProvider that is not publicly exported grants temporary read access to the supplied file, not access to saves or the profile area and not write access. The receiving app may create its own copy. Expiry of temporary read permission does not delete the cache file or those copies.
When you share again, the app attempts to delete matching scene-…png files in that cache folder whose modification time is more than 24 hours old according to the device clock. There is no scheduled deletion at exactly 24 hours or guaranteed cleanup without sharing again; deleting an individual file can also fail. Android may remove cached files. You can clear the app cache in Android Settings without deleting your progress; “Clear data” is a different, comprehensive action. Clearing app data or uninstalling also removes these cached files. Copies already handed to another app or recipient are not deleted by those actions.
Local statistics
Statistics read existing values from the local save, including levels, best stars, plants, garden bonus and area, pollen, plant vouchers, recorded daily successes and visit and recovery dates recorded by the visit calendar. These values have different meanings and are not expanded into an estimated complete play history. They are shown on your device; no usage events or statistics reports are sent to JTSR, and there is no telemetry, Firebase or analytics integration of our own. A recorded puzzle-attempt duration is distinct from an overall play-time statistic. The separate local daily foreground-time counter for break reminders is described in its own section; it is not a usage report sent to JTSR.
No transmission of your game saves
These game saves are not sent to JTSR or a game service. There is no game login, game server, public garden page, leaderboard or chat. The app contains no advertising, Firebase or its own analytics SDK.
Permissions
Under the current source configuration for 1.14.0, the app requests VIBRATE for optional haptic feedback. INTERNET, network-state and billing permissions are removed. The protected Google Play version may contain additional permissions such as com.android.vending.CHECK_LICENSE. Contact and external support do not require access to contacts, camera, microphone, location or photos. At your request they open an external email app or browser. Image sharing also needs no camera or photo access: it renders the game view locally and grants access only to the generated file as described above.
Automatic protection of the Google Play version
The protection component added by Google communicates with the Play Store to check app entitlement and processes technical information such as the package identifier. Local game storage and processing by Google Play are separate processes. According to Google, protection checks can generally work offline; if the Play Store has been offline for a prolonged period, installation checks may temporarily require an internet connection. Offline gameplay therefore does not mean unlimited network independence for the protected Play version or that Google or Android process no data. Google Play standard reports are explained below.
Shop and prepared billing library
The garden shop uses only earned pollen with no monetary value. The prepared Google Play purchase library remains disabled. There is no active real-money shop or PayPal payment SDK in the game. Voluntary support outside the app is separate and gives no in-game benefits. The game receives no payment details or payment status; JTSR as a payment recipient may receive payment details from PayPal.
Music, images and device time
Prerendered music is bundled with the app and played locally, without streaming or downloading. The garden grid and furniture geometry are generated locally. Plant and animal artwork is bundled with the app. Short effects may be stored in the private app cache; textures are bundled with the app. The app makes no image, audio or AI requests to external services. Growth and daily puzzles use local device time, not a time server. Weather is a game setting, not a lookup of the weather at your location.
Storage, updates and deletion
Android cloud backups and device transfers are disabled. JTSR offers no cloud restoration. Since the historical package change in version 1.8.1, the app has used com.jtsrlab.lumaandleaves and its own private storage, separate from the earlier app with a different identifier. Saves from that earlier app are not transferred automatically; keep that installation and its data. Version 1.14.0 retains the same identifier and does not introduce another package change. Updates require a matching app ID and compatible signature. Uninstalling or clearing app data removes the local save, including calendar, reward and statistical records. Format migrations apply only within the respective app storage. There is no server-side game account. Clearing game data does not delete drafts or sent emails in your external email app.
Google Play and Android
The app has no analytics integration of its own and does not send your local save to us. When distributing through Google Play, we use only the standard reports it provides on usage and technical quality. Processing by Google Play and Android is separate from this app’s local data storage and follows the respective Google services and settings. No additional analytics integration such as Firebase is currently included.
Diagnostic reports and their limits
Android Vitals uses shared usage and diagnostic data from supported devices. APKs installed directly from outside Google Play are not included there. These platform reports are not complete personal gameplay histories; coverage of every player or guaranteed anonymity of all reports is not promised. This app’s offline design does not mean that Google or Android never process data.
Website, support and testing
The privacy link in the app opens this website in an external browser. No saved progress or user identifiers are appended to its URL. Website visits and voluntarily sent emails are also covered by the website privacy notice, including the existing operator, hosting and email details and data subject rights.
Optional contact for adults and parents
The contact feature is intended for adults and parents and is not required to play. If you use it, a reply email address and a message are required. Provide only information needed to handle the enquiry, without passwords, identity documents, complete private saves or unnecessary information about children. Addressing the feature to “adults and parents” does not verify identity, age or parental status and does not establish verified parental consent. The reply address is checked only for a valid format; its reachability or ownership is not verified. Children are asked to have an adult write the message and send it from the adult’s email account. The contact form itself does not request age or birth date. Before it opens, the local adult check described above applies if the age group is unknown or below 18.
Handing information to your email app
The game holds your reply email address and message temporarily in working memory, not in its save, files or logs. The input fields are not saved as a persistent form draft and do not use autofill. They are cleared when the contact dialog closes or after the email app opens successfully. If no email app can be opened, the entries remain in the dialog until it is closed or another attempt is made. Only when you select “Prepare email” are the details passed to your external email app for a message to the fixed recipient contact@jtsr-lab.com. The reply address appears in the message body; the account selected in your email app determines the actual sender address. The email app may save a draft even if you do not send it. You review and send the message there yourself. The game does not send emails directly or add attachments, saves, usage statistics, identifiers or diagnostic files. Opening the email app confirms neither sending nor delivery; the game receives no proof of sending. The keyboard, email app and their providers process information independently. Temporary storage in the game is not a promise about their storage.
Processing received contact emails
When a voluntarily sent email reaches us, we process the reply email address, sender address, message and technical transmission data to handle and answer the enquiry. Voluntarily sent messages are also reviewed manually to investigate reported bugs and assess suggestions for improving the app. We use the reply email address for contact and support, not to analyse gameplay behaviour. For Google Play purpose disclosures, manually investigating bugs and reviewing improvement suggestions falls under “Analytics” for messages/emails, in addition to app functionality; the reply email address is used solely for app functionality and support. This means the operator reviewing content you voluntarily send, not automated usage analytics, gameplay telemetry or an additional analytics SDK. These details are not used for newsletters, advertising or account management. The published website privacy notice explains the existing IONOS support processing and your rights. The contact mailbox contact@jtsr-lab.com remains hosted by IONOS SE. Under the existing policy, resolved support enquiries, including managed copies, attachments and trash, are manually deleted no later than six months after closure; necessary statutory or specifically justified longer retention remains subject to that notice. Your external email app and email provider process their own drafts and messages under their own rules. Local game-save storage therefore does not mean that contacting us involves no personal data processing.
Age check for voluntary support
The planned support area is intended for adults. A neutral day, month and year of birth entry is checked on the device to determine whether the entered age is at least 18. It is not identity verification or verified parental consent. The date stays temporarily in memory; it is not stored in saves, files or logs and is not sent to JTSR or PayPal. The fields are cleared after a valid check and when the dialog closes. Invalid entries remain visible until corrected or the dialog closes. Form saving, autofill and content capture are disabled for these fields; your keyboard and operating system have their own rules. Without passing the check, no PayPal action is offered. No identity documents are requested.
PayPal outside the game
Support is optional and provides no pollen, stars, items or other in-game benefits; it is not a charitable donation. Only an explicit action copies the fixed recipient address contact@jtsr-lab.com to the clipboard. The app does not read existing clipboard content. Separately, “Open PayPal” opens the official send page https://www.paypal.com/myaccount/transfer/ in an external browser. The link contains no birth date, save, identifiers, amount or payment status. You enter the recipient, check the details and decide for yourself whether to pay there. The button in the game does not send money. The game receives no payment confirmation and stores no payment details.
PayPal processes account, device and payment information under its own rules when you use its service. JTSR as the recipient may receive a name, contact details, amount, date, transaction reference or a message you include, where PayPal provides these for the transaction concerned. These details are used to identify and administer the support, answer related enquiries and meet any legal record-keeping duties. They are not linked to your local save. Necessary payment records are kept for as long as required for these purposes or legal duties and then deleted. Your rights and the operator contact channels also apply to these details. PayPal is responsible for its own processing.
Future changes
If data processing changes, for example through new online features, automated usage analytics or active real-money purchases, this notice will be updated accordingly. Automated usage analytics and real-money purchases are not active in the version described here.