numa

Privacy Policy

Numa: Baby Sleep Sounds · Effective 3 October 2026

The short version: Numa does not collect, store, share or sell any personal data. It has no accounts, no ads, no analytics and no tracking, and it does not use the internet.

Who we are

Numa is a free Android app that plays calming sounds for babies. It is developed and published by the developer listed on Numa's Google Play page ("we", "us"). This policy explains how Numa handles information.

Information we collect

None. Numa does not collect any personal or device information. Specifically, Numa does not:

Information stored on your device

To be useful, Numa remembers a few things only on your phone:

This information never leaves your device through Numa and is never sent to us. You can remove it at any time by clearing Numa's storage in Android settings or by uninstalling the app.

If you have turned on Android's own device backup, Android may include these settings in your personal Google backup, as it does for most apps. That backup is controlled by you and Google under Google's terms; we cannot access it.

Permissions

Numa asks Android for only what it needs to play sound reliably:

None of these permissions give Numa access to personal information.

Sharing and selling

Because we collect no data, we have nothing to share, sell or transfer to anyone.

Children

Numa is designed for parents and caregivers to use for their babies. It collects no information from anyone, including children, and contains no ads, in-app purchases or links to outside services.

Third parties

Numa contains no third-party advertising, analytics or tracking software. Google Play, which you use to download the app, has its own privacy policy.

Changes to this policy

If this policy changes, we will update this page and the effective date above. If Numa ever started handling data differently, we would say so clearly here before that happened.

Contact

Questions about privacy? Contact us using the developer email address on Numa's Google Play page, or open an issue here.