This Privacy Policy describes how MoonyPanda ("we", "us", "our"), developer of the MoonyPanda sleep app ("Slumber", the "App"), handles information when you use our Android app and this website (moonypanda.com). It is written to satisfy the Google Play User Data policy, including the rules for personal and sensitive data, health data, prominent disclosure and consent, and account deletion.
1. Who we are & contact
Developer: MoonyPanda, developer of the MoonyPanda sleep app (package
com.moonypanda.slumber).
Privacy contact: alerts@moonypanda.com.
Contact us there with any privacy question, access request, or deletion request.
2. Data we collect
We collect only data needed for the App's core sleep, meditation, and wellness functions:
2.1 Health and wellness data (personal & sensitive)
- Heart rate, heart rate variability (HRV), and blood oxygen (SpO2) readings.
- Sleep sessions, meditation sessions, steps, movement, and derived scores, trends, and recommendations.
- Sources, only with your permission: Bluetooth wearables you pair (smart rings, watches) and Samsung Health / Wear OS where you connect them.
2.2 Account data
- A randomly generated 16-character app ID (UUID) created on device — no email or phone number required.
- If you register with details: country, language, and optionally email, plus your consent record.
- App settings and preferences (soundscapes, volumes, thresholds, paired-device identifiers such as a Bluetooth MAC).
2.3 Diagnostics (optional)
- Crash and diagnostic log excerpts are uploaded only if you enable Collect Startup Logs in Settings.
We do not collect contacts, call logs, SMS, photos, microphone recordings, precise location, financial data, government IDs, or advertising identifiers, and we do not link persistent device identifiers (IMEI, SIM serial) to your data.
Prominent disclosure (shown in-app before any collection): "MoonyPanda collects health data (heart rate, HRV, oxygen) from devices you connect, including in the background during sleep and meditation sessions, to generate adaptive soundscapes, sleep scores, and wellness insights synced to your account." Collection starts only after you tap to accept and grant the requested permissions.
3. Device permissions we request
Each permission is requested in-app, after the disclosure above, and only for the listed purpose:
- Nearby devices / Bluetooth (scan & connect) — find, pair, and read data from your ring or watch.
- Nearby-device / Bluetooth data from paired wearables — read while sessions you start need it.
- Body sensors & activity recognition — on-device session monitoring and high-rate sensor sampling.
- Notifications — session status, alarms, and health alerts.
- Foreground service (health / connected device / media) — keep recording and audio running during sessions, including in the background.
- Battery-optimization exemption — prevents the OS from killing overnight sessions (optional, requested only when needed).
You can deny any permission; the related feature will simply be unavailable.
4. How we use data
- Run sleep and meditation sessions: adapt soundscapes in real time, compute scores, detect wake-up conditions.
- Build your history, trends, and personalized recommendations.
- Sync your data across your devices and keep backups.
- Send health alerts you configure (e.g., abnormal readings) through channels you choose.
- Fix bugs and improve reliability (diagnostics only, only if you opt in).
We do not sell personal or health data, do not use it for advertising, and limit every use to the purposes above that you reasonably expect from a sleep app.
5. Sharing & third parties
- No sale, no ad networks, no analytics SDKs. Your health data is never sold or shared for marketing.
- Cloud sync provider: encrypted sync storage that hosts your account backup so sessions survive reinstalls and sync across devices.
- Alert channels you enable: if you turn on email, WhatsApp, or Telegram alerts, the alert content is transmitted through that provider solely to deliver your alert.
- Legal: we disclose data only to comply with valid legal process or to protect safety, with notice where permitted.
6. Storage & security
- Local-first: health sessions live in an encrypted on-device database; the app works offline.
- In transit: all network sync uses modern encrypted transport (TLS/WSS).
- Access: your data is keyed to your app UUID; backend access is authenticated per account channel.
7. Retention
We keep your health history so trends remain useful, until you delete it: deleting a session removes it; factory reset wipes local data; account deletion removes everything (see next section). Diagnostic logs are kept only briefly for debugging. Where we must retain narrow records for security, fraud prevention, or legal compliance, we disclose that on request.
8. Account & data deletion
- In the app: Settings → Reset to Factory Settings deletes local data; contact alerts@moonypanda.com from your account email asking for account deletion and we delete your account and all associated server data.
- On the web: email the same address with subject "Delete my MoonyPanda account" including your 16-character app ID (found in the app under Settings); we confirm and delete within 30 days.
- Freezing or logging out is not deletion — deletion permanently removes your data.
9. Your rights & choices
- Grant or deny any permission anytime in Android Settings; the app degrades gracefully.
- Turn cloud sync and log collection on or off in the app's Settings.
- Request access, correction, export, or deletion of your data via the contact above.
- EU/UK/CH users: we process health data on the basis of your explicit consent, which you may withdraw anytime (withdrawing stops future collection; already-recorded data is deleted on request).
10. Children
MoonyPanda is not directed at children under 13 (or the higher minimum age where you live) and does not knowingly collect their data. If you believe a child provided data, contact us and we will delete it.
11. Changes to this policy
If our data practices change, we update this page, revise the effective date above, and highlight material changes in-app where required. Continued use after changes take effect constitutes acceptance.