Your family’s sleep data starts on this device

Napnix stores child names or nicknames, age details, time zone, sleep logs and notes, preferences, and progress in this browser using IndexedDB and localStorage. Core profile and sleep records are not uploaded merely because you use the tracker.

Local data remains in this browser until it is replaced, imported over, or cleared with the browser’s site-data controls. Clearing browser data, using private browsing, or losing the device may remove it.

Birth month and year help Napnix choose age-based guidance. You may use an age range instead. An exact birth day is optional and enables birthday moments and a more precise age calculation.

Napnix is intended for a parent or legal guardian managing a child’s routine. Use a nickname if you do not want to store a child’s full name, and do not let a child enter account or profile information directly.

Cloud backup is optional and requires sign-in. If it is configured and you sign in, the authentication service receives account information such as your email address, and Napnix can create backup snapshots containing exported profile and sleep data. Snapshots may be created automatically while you remain signed in.

Napnix retains up to five recent cloud snapshots per account. You can view the snapshot count and delete one or all snapshots from Cloud Backups. Signing out does not erase local data or snapshots already created.

Napnix may send a small allowlisted set of technical diagnostics to its telemetry endpoint so the beta can be kept reliable. This can include an error category, a normalized route group, app environment, and non-sensitive status flags. Raw error messages, stack traces, email addresses, authentication tokens, child profiles, notes, and sleep logs are not included in structured telemetry.

The beta may also send a limited set of product-usage events, such as opening the app, completing onboarding, exporting a backup, installing the app, or submitting button-only feedback. These events use a random installation identifier stored in this browser. It is not linked to your account or authentication identifier and is removed by the in-app local deletion flow.

Product events do not include a child identifier or name, birth details, email, notes, exact sleep times, sleep-log contents, time zone, or backup contents. App-open events include only a calendar date and a broad allowlisted route group. Feedback is limited to the choices shown in the interface and has no free-text field. Activation is reported only on a later calendar day, not when a sleep window appears.

Use Data & Backup to export local data. The same screen provides an in-app local deletion flow that signs out first and removes Napnix-owned data from this browser. It does not delete cloud snapshots or the account.

Cloud snapshots can be deleted from Cloud Backups. To request account deletion, follow the steps in Support.

Napnix does not include advertising or sell profile and sleep data. Hostinger hosts the production app and may process request, security, and application logs. Supabase processes sign-in and cloud snapshots when cloud backup is configured, and Google processes sign-in details when you choose Google sign-in. If a separate telemetry relay is configured, it receives only the allowlisted diagnostics and product events described above. Product-event delivery remains disabled until a production provider and retention period are approved. Local data remains until you delete it; cloud snapshots remain until deleted or rotated out of the five-snapshot window; account records remain until an account-deletion request is completed. Infrastructure logs may be retained under the applicable provider’s operational policy.

This notice may change as the beta adds or removes features. Material changes should be reflected here before release. Contact alextovt2@gmail.com with privacy questions.

Also read Data Safety for product limits and practical backup guidance.