Mossby

Privacy Policy

Effective date: 15 August 2026  ·  Last updated: 2 September 2026

This Privacy Policy explains how Mossby (the “App”), published by Nyxelium (“we”, “us”, “our”), handles information when you use the App. Mossby is a plant-care and watering-reminder app available on Google Play (package com.nyxelium.mossby).

The short version

Which version am I reading about? This policy describes Mossby as it ships today. If the copy on your device has no Help improve Mossby switch under You → Privacy, it is an older build: it contains no Analytics SDK and makes no network request of any kind.

1. Information stored on your device

Mossby is designed to work offline. The following stays on your device and is not transmitted to us:

This data is removed when you delete the App or clear its storage. Because it never leaves your device, we cannot retrieve or restore it for you.

2. Manual backup and restore

Mossby lets you create a plain-JSON backup through the operating system’s save sheet and restore a file you explicitly select. You control the destination. If you choose a cloud-storage provider or another third-party location, that provider handles the file under its own terms and privacy policy.

The backup contains garden structure, schedules, care history, custom plants and catalog preferences. Plant photos are excluded, as are device-specific photo paths and App preferences. Mossby does not automatically upload or read backup files.

3. Information collected or shared

The App includes no advertising, crash-reporting, account, social or purchase SDK. It includes one optional measurement SDK, described in section 4.

We never collect or receive your plant, pot or zone names, notes, photos, greeting name, feedback text, file paths or backup contents. The fixed Analytics allowlist cannot carry them.

If a future version adds a networked service, advertising, accounts or purchases, we will update this policy and the relevant store disclosures before distributing that version.

4. Optional usage measurement

To understand which parts of Mossby work and where fixed App interactions fail, the App can send pseudonymous usage events using Google Analytics for Firebase, provided by Google LLC as our processor.

Where it starts, and how to change it

Which state the App installs in depends on where your device is:

The App decides which of the two applies from your device’s region settings and time zone. That determination is never sent anywhere, and a device it cannot place with confidence is treated as being in the first group — off.

Once you have set up the App and cared for a plant, it shows a one-time notice naming what is collected and letting you change the setting on the spot. Where consent is required the notice is a question with two equally weighted answers and no pre-selected reply; elsewhere it says measurement is on and offers to turn it off. Closing it without answering changes nothing and it does not return.

The switch in You → Privacy always shows the state collection is actually in, so it can never read “off” while the App is collecting. Switching it off stops collection and tells the SDK to discard the random App-instance ID held on your device, so a later opt-in starts as a new App instance.

There is no other way to enable it. Mossby does not ask during setup and has no advertising consent banner.

What Analytics can collect

Google Play data typeWhat it means in MossbyPurpose and choice
App activity → App interactions Fixed events such as screen opens, care actions, setup steps, reminder outcomes, backup or restore outcomes, feedback entry points, and bounded failure categories. No free text, crash log or stack trace. Analytics; optional; not shared.
Device or other IDs A random App-instance ID that identifies this installation for Analytics. It is not an account ID, Advertising ID, Android device ID or cross-App ID. Analytics; optional; not shared.
Location → Approximate location Google derives coarse geography from the masked IP address used for an Analytics upload. Mossby never asks for location permission and never sends GPS or other location coordinates. Google Analytics does not log or store the IP address. Analytics; optional; not shared.

Google also attaches coarse technical context, such as device model, operating-system version, App version and language. Events are encrypted in transit. Google Signals, Ads linking and advertising personalization are not used.

What Analytics can never collect from Mossby

Plant, pot or zone names; notes; photos or anything derived from them; the greeting name; feedback message text; error messages, crash logs, stack traces or file paths; exact garden counts; purchase history; account information; the Advertising ID; or the Android device ID (SSAID). The Advertising ID and ad-attribution permissions are removed from the App and those identifiers are disabled in configuration.

Stopping collection and deletion

Switching measurement off stops future collection and discards the App-instance ID held on the device. It does not identify or retroactively isolate earlier aggregated events in Google Analytics. Because Mossby has no account and we cannot map an App-instance ID to a person, we cannot look up past events by your name or email.

5. In-App feedback

The Feedback & about screen does not transmit anything. It places the text you review on the device clipboard; nothing leaves the device unless you paste it into your own email App and send it yourself.

An optional technical block, off by default, can add App and operating-system versions, displayed language, theme, a garden-size range, reminder and notification-permission state, and current-session error counts with fixed source labels. It never adds names, notes, photos, greeting text, error messages or file paths.

A card on that screen asks about possible future photo-symptom research. That feature does not exist. The card does not inspect or upload a photo and does not register you for anything; it only prepares editable feedback text on the same screen.

6. Device permissions and system features

Mossby holds no camera permission of its own, and does not request contacts, precise or approximate location, microphone, broad storage access, exact alarms, the Advertising ID or an in-App account.

7. Android backup behavior

Mossby opts its App data out of Android automatic cloud backup and device-to-device transfer. A manual backup is created only when you choose the backup action and select a destination.

8. Data retention and deletion

Local data remains until you delete it in the App, clear App storage or uninstall the App. Copies you manually exported remain wherever you saved them and must be deleted there by you.

If you enabled measurement, Analytics events are retained for the period configured for the Nyxelium Analytics property and are then deleted automatically. Switching the setting off stops future collection and resets the device’s App-instance ID as described in section 4.

9. Security

Mossby relies on Android’s App sandbox for local data. Imported backups are treated as untrusted and checked for size, structure, version and collection limits before restoration. Analytics uploads use TLS and the App disallows cleartext network traffic.

10. Children’s privacy

Mossby is a general-audience utility and is not directed to children under 13 or the equivalent minimum age in a user’s country. The App has no account and does not collect garden content, names, notes, photos or contact details. Optional pseudonymous measurement can be switched off at any time, and is off by default wherever prior consent is required.

11. Your privacy rights

Depending on where you live, you may have rights concerning personal data. You control local garden content in the App and through Android settings. You control measurement through You → Privacy; withdrawing consent stops collection immediately. Optional Analytics carries no account, name, contact detail, advertising identifier or free text, but it does use a random App-instance ID that we cannot map to a person or account.

For a privacy question, or a request concerning information you separately sent to Nyxelium, contact us below.

12. International processing

Google may process Analytics data in countries other than yours. Google states that most Firebase services use global infrastructure and provides contractual and legal safeguards where required. See the linked Google and Firebase privacy information.

13. Changes to this policy

We may update this policy when the App changes. We will revise the “Last updated” date and provide any notice required by law or store rules.

14. Contact us

If you have questions or requests regarding this policy or your data:

Nyxelium
Email: kowalski.dev07@gmail.com