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 the five latest cloud snapshots plus the latest copy from each of the previous seven UTC days when a backup was created (up to twelve copies 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.

When family sharing is enabled, signed-in adults can share a diary. Creating a family and choosing to include existing device records sends those profiles and records to Supabase. Family members use the same children and records in the normal diary screens. The diary selector lets you switch between a family and the separate records on this device. Personal cloud snapshots belong to the device diary; shared edits are not automatically merged into those records.

Successful changes to shared child profiles and sleep records also save a separate family backup on the server. Napnix keeps the five latest distinct copies plus the latest copy from each of the previous seven UTC days with changes (up to twelve copies per family), including changes made by editors. Only the family owner can view or download these backups. They are separate from personal device snapshots and are not restored into this browser automatically. Deleting the family also deletes its retained family backups.

The family owner can invite another signed-in account to view or edit all current and future children and records in that family. Editors can change profiles and sleep records; only the owner manages other participants and invitations. Members can export data they can read. Share invitation links only with people you intend to give access to. Links can be used once, expire after seven days, and can be revoked before use.

Napnix stores family membership, the display name each member chooses, invitation status, and the account responsible for changes. Invitation secrets are stored as hashes on the server. A pending invitation can remain in this tab’s sessionStorage for up to 24 hours while you sign in; it is cleared on acceptance, cancellation or sign-out. This browser remembers your selected diary using account and family identifiers. Family profiles and sleep records are kept in page memory while open and are not added to the device diary or offline cache automatically.

Removing a participant prevents new server access. It cannot erase information already viewed or exported by that person. Shared records remain until the owner deletes the family. Owned families must be deleted before an account-deletion request can be completed. Leaving a family or deleting local browser data does not delete the shared diary. An internet connection is required for shared changes.

Technical diagnostic delivery is off by default in this beta. If enabled for a release after its provider and retention period are approved, Napnix may send a small allowlisted set of diagnostics to its telemetry endpoint. 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.

Product-usage delivery has a separate setting and is also off by default in production. Events may be held in a bounded queue in this browser. When delivery is enabled, the beta may send 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.

Public sleep resources also record the first resource path, its topic group, a broad referral/source category and an allowlisted campaign code in this browser. Tool use, product links, onboarding and the first, third and seventh complete logged days can be associated with that original resource. These events contain no entered sleep values, child identifiers, raw referrer URLs or arbitrary campaign text. Public calculator entries are kept only in page memory and are cleared on reload or navigation away.

Use Data & Backup to export the selected diary. With the device diary selected, this screen also provides a local deletion flow that signs out first and removes Napnix-owned data from this browser. It does not delete shared family records, cloud snapshots or the account. Family access provides owner-controlled family deletion.

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 even when app telemetry is disabled. Supabase processes sign-in and the configured cloud features, including personal snapshots and shared family diaries. Google processes sign-in details when you choose Google sign-in. If a separate telemetry relay is configured and the relevant delivery setting is enabled, it receives only the allowlisted diagnostics or product events described above. Diagnostic and product-event delivery remain 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 recent-and-daily retention 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.