Legal document
Terms of Use →Privacy Policy
1.Who operates Napzy
Napzy is a baby-tracking app operated by Lucas Milhan, an individual, hereafter referred to as "we" or "the developer." This policy explains what data the app collects, why, and what rights you have over it.
2.Data we collect
The data involved in using Napzy falls into these categories:
| Category | What it includes | Where it lives |
|---|---|---|
| App usage data | Baby profiles (name, birth date, and sex), feeding, sleep, diaper, growth, and temperature entries, their notes and tags, and the statistics calculated from them | On your device; baby profiles, entries with their notes, and tags also in Cloud backup (Pro) while it is on |
| Settings | Theme, language, whether app lock and feeding reminders are on, and a saved copy of your Pro status | On your device; the theme also in Cloud backup (Pro) while it is on |
| Account profile (only if you sign in) | Account id, e-mail, name, profile photo URL, the date the account was created and, if you delete it, the date it was deleted | Our backend on Firebase (Google) |
| Subscription records (only if you subscribe) | Whether Pro is active, its status, product, plan, expiry date, auto-renew on or off, last update, and the link between your Google Play purchase token and your account | Our backend on Firebase (Google) |
| Crash reports | Failure stack traces, device model, Android version, and app version | Firebase Crashlytics (Google) |
| Usage metrics | Screens visited, basic navigation events, and a few in-app events (such as when the review prompt is shown or you tap Contact us), with no content from your baby's entries | Firebase Analytics (Google) |
Content you create — your baby's entries, notes, tags — is never sent to crash or usage reports. Those tools only receive technical signals about how the app is behaving. Because this content is personal information about your baby, keeping it out of these reports is a deliberate design choice.
PDF reports and share images are created on your device. They only leave it if you share them, and then go to the app you choose. Dictating a note uses your device's speech recognition service; Napzy has no microphone access. App lock uses your device's screen lock or biometrics through Android; Napzy never receives your fingerprint or face data.
3.Optional account and sign-in
Signing in to Napzy is optional: you can use the app without an account, and you only need one for Pro. The only way to sign in is with your Google account.
When you sign in, Google gives us your Google account ID, e-mail, display name, and profile photo URL. We keep them as your account profile, listed in Data we collect, and use them only to run your account.
You can read only your own profile, and only our server can change it.
4.Subscriptions
Pro is a subscription you buy in Google Play. After a purchase, the app sends the purchase token and the product id to our server, which checks them with Google and then stores the subscription records listed above.
Payment is handled only by Google Play. Your card number and billing address never reach us.
5.Security and app attestation
When the app calls our server, it uses Firebase App Check with Google Play Integrity to prove it is the genuine app. This helps us turn away requests from modified copies or scripts.
6.Cloud backup (Pro)
Cloud backup is part of Pro and needs the optional Google sign-in. It is on by default once you are a signed-in Pro, and you can turn it off in Settings → Cloud backup. While it is on, Napzy copies your content to our backend in the background after you change something. It is a backup, not a live sync between devices: the app keeps working from your device.
What it copies:
- Your baby profiles (name, birth date, and sex), their feeding, sleep, diaper, growth, and temperature entries (the time and the details you logged, with the note and its formatting), tags and which entries they are on, and the theme;
- Not copied: language, app lock, the feeding reminder setting, onboarding and review state, your Pro status, and PDF reports and share images.
| What | Where | How long |
|---|---|---|
| Baby profiles, their logs, tags, and the theme | Our backend on Firebase (Cloud Firestore, Google) | Until 12 months after the last backup once your account has no active subscription, or until you delete your account |
To restore, sign in with the same Google account and use Restore from backup in Settings → Cloud backup; Napzy also offers it after you sign in. Restoring merges the copy with what is on the device: the most recent edit wins, and what you deleted stays deleted. Restoring does not need Pro: without it, Napzy never uploads anything and only reads your own backup, so after Pro ends you can still restore until the backup is deleted.
Our backend's security rules let only your signed-in account read your backup. It is not end-to-end encrypted: Google encrypts it in transit and at rest.
Something you delete on your device is removed from the backup at the next backup. Turning Cloud backup off stops new uploads; what is already backed up stays until it is deleted as described above.
7.Android automatic backup
Android may automatically back up Napzy's data (including your baby's entries) to your own Google account, the same way it does for any other installed app — this backup is controlled by you, in your device or Google account settings, not by us. You can disable it at any time in Android Settings → System → Backup.
It is a different thing from Napzy's Cloud backup (Pro), described above: Android's backup goes to your own Google account and is managed by Android, while Cloud backup is a copy on our backend that Napzy makes only for a signed-in Pro.
8.Data retention and deletion
Your app usage data is stored on your device and is removed when you uninstall the app or clear its data, except for any copy kept by Android's automatic backup in your own Google account or by Cloud backup (Pro), described above. Crash reports and usage metrics are retained only for as long as necessary to diagnose issues and improve the app, following Firebase Crashlytics' and Firebase Analytics' own retention settings, after which Google automatically deletes them from its systems.
If you delete your account, your sign-in account is removed right away, and your profile (e-mail, name, and profile photo URL) is marked as deleted and purged after 30 days. Your subscription records are kept, tied only to an id that no longer identifies you, for analytics and accounting, for as long as those purposes require.
Your Cloud backup is deleted right away when you delete your account. Once your account has no active subscription, nothing new is backed up and you can still restore it; it is deleted automatically 12 months after the last backup.
Notifications Google Play sends our server when a subscription changes are stored with your account id for up to 180 days and then removed automatically.
9.Where data is processed
Your account and subscription data, and your Cloud backup, are processed on our backend, which runs on Firebase, on Google servers in the United States. For users in Brazil, the European Economic Area, and the United Kingdom, this is an international data transfer. Google is bound by its own data-processing terms and standard contractual clauses covering these transfers.
Firebase Crashlytics and Firebase Analytics may also process and store diagnostic data on Google servers outside Brazil, including in the United States, under the same safeguards. Diagnostic data and account data are two separate things: we do not link diagnostic data to your account, and it never includes your baby's entries or other content you create in the app.
10.Legal basis
We process account and subscription data, and your Cloud backup, to provide the features you ask for when you sign in, subscribe, or keep Cloud backup on (performance of a contract).
We process diagnostic data (crash reports and usage metrics) on the basis of legitimate interest — necessary to identify failures, fix bugs, and maintain the app's quality and stability.
After you delete your account, we keep the subscription records on the basis of legitimate interest, for analytics and accounting.
11.Data sharing
The only third parties involved are Google services: Google Play, which sells and bills subscriptions, and Firebase, which runs sign-in, our backend, crash reports, and usage metrics. They are used only for the purposes described above. We do not sell, rent, or share your data with advertisers or other third parties, and we do not use it for ads.
12.Your rights
As a data subject, you can at any time:
- Request access to your account data (profile and subscription records) and to the diagnostic data associated with your use of the app;
- Request correction of inaccurate data;
- Delete your account, and request deletion of diagnostic data, or anonymization where deletion is not technically possible;
- Request a portable copy of your account data and of the diagnostic data we hold about your use of the app;
- Object to processing based on legitimate interest, or withdraw your consent, without affecting past processing;
- Disable Android's automatic backup at any time.
Your baby profiles and their feeding, sleep, diaper, growth, and temperature logs are on your device, so you control them directly: delete them in the app, clear the app's data, or uninstall it. Their copy in Cloud backup is deleted with your account.
To delete your account, follow the steps at luczfac.com/napzy/delete-account. For any other request, contact us using the e-mail address in the Contact section below. We will respond within a reasonable time and at no cost, as required by applicable data protection law.
13.Children
Napzy is intended for use by parents and caregivers aged 18 or older and is not directed at children; we do not knowingly collect data from anyone under 18 as an app user. Any information you enter about your baby — such as a name, birth date, or growth measurements — is provided by you and stored on your device, as described above; it is never collected directly from a child. Your account profile holds only your own Google identity as the parent or caregiver, never your baby's information; your baby's profile and logs reach our backend only as your Cloud backup, if you are Pro and keep it on. That copy is readable only by your account and is deleted with it, as described in Cloud backup.
14.Changes to this policy
We may update this policy occasionally to reflect changes to the app or to applicable law. The effective date at the top of this page always shows the most recent version.
15.Contact
Questions, requests, or privacy concerns can be sent to: