Privacy Policy

1. Controller and contact

Napverse is operated by LLAPPS LTD, EIK 208492694, Bacho Kiro 1 street, floor 8, office 8-3, 9000 Varna, Bulgaria. LLAPPS LTD is the controller for the processing described in this policy unless a listed provider acts as an independent controller under its own terms.

For privacy questions or requests, use Contact Support in the app or email support@napverse.app.

2. Information kept on your device

Napverse stores the information you enter and the views it calculates locally so ordinary tracking can work quickly and offline. Depending on the features you use, this can include:

• Baby profiles: name, birthday or expected due date, gender, profile color, and birth measurements.
• Daily care: sleep, breastfeeding, bottles, pumping, diapers, temperature, growth measurements, times, durations, amounts, sides, moods, and notes.
• Memories and Time Capsules: journal entries, ratings, recipients, photos, videos, audio, documents, and related metadata.
• Settings and calculated views: reminders, notification preferences, schedules, widgets, Live Activities, summaries, charts, pattern segments, and prediction state.

Local information may also be included in an iPhone backup if you enable Apple backup features. Some security or installation identifiers stored in the iOS Keychain can survive an app reinstall.

3. Information sent by the iPhone app

Optional Napverse Sync and caregiver sharing

Napverse Sync is optional. When you connect a Napverse cloud account and enable Sync for a baby, Napverse sends that baby's profile and complete history of sleep, breastfeeding, bottle feeding, pumping, diaper changes, temperature, growth measurements, medicine, and solid-food entries to a named European-region Firebase database. It also sends the text and metadata of the shared Memories journal and your own Time Capsules for that baby. Sync also processes account, consent, membership, permission, version, conflict, deletion, and device-delivery records needed to keep the service secure and consistent.

Shared profile, activity history, and Memories belong to the baby. Only the owner can approve a caregiver and choose whether each activity category and Memories are hidden, view-only, or editable. A person with Memories access can read the shared journal; a person with edit access can add, edit, and delete entries. Time Capsules remain private to their creator. Activities and Memories a caregiver added remain in the shared history after the caregiver leaves or is removed, but the former caregiver's identifying attribution is retired.

Memory attachments and Time Capsule attachments have separate settings and both are off by default. When a setting is off, Napverse Sync sends the related text and metadata but does not send the attachment, filename, thumbnail, preview, Base64 data, or local file URL. When you turn a setting on, available existing files on your devices and future files may be uploaded. Turning off Memory attachment uploads blocks new transfers and cancels unfinished uploads, but finalized shared copies remain with the baby for authorized caregivers. Turning off Time Capsule attachment uploads deletes that creator's remote copies while retaining local originals. If no device still has an original, deleting a Time Capsule cloud copy may permanently lose that private attachment.

When Napverse Sync is available and enabled, its care data and synced attachments use named European-region Firebase and Google Cloud resources. Firebase Authentication and some security, delivery, support, or provider operations may be processed outside that regional care-data plane, including in the United States, subject to the transfer safeguards described below. Sync uses encrypted network transport and provider encryption at rest, but it is not end-to-end encrypted: authorized Napverse backend operations and the cloud provider can technically process plaintext records.

Notifications for sharing and sync use content-free event identifiers. They do not include baby names, notes, medicine details, activity timestamps, attachment links, or invitation tokens. We do not intentionally place care-record contents or invitation links in analytics, crash breadcrumbs, operational logs, or ordinary support requests.

App usage analytics

Napverse uses Amplitude and Google Analytics for Firebase to understand feature use and improve the app. Custom events can describe app launches, screens and features used, coarse interactions, onboarding progress, subscription-flow interactions, and product, entitlement, renewal, trial, price, result, or content-free error-state information. Care interactions are reduced before they reach a provider to a coarse record kind such as activity, Memory, or Time Capsule and a generic action such as create, update, or delete.

Analytics SDKs can automatically add event timestamps, session information, app version, iOS version, device model or category, language or locale, network or carrier context, approximate region derived from an IP address, and provider-specific app-instance or device identifiers. Napverse does not intentionally add a baby name, birthday or derived age, activity subtype, accumulated sleep total, raw notes, media type or count, exact care timestamps, feeding side, medicine details, or feeding, temperature, or growth values to its custom analytics events or user properties.

Pseudonymous account and service identifiers

Napverse uses Firebase Anonymous Authentication to protect backend requests. Before the resulting Firebase user ID reaches Google Analytics for Firebase or Amplitude as an analytics identity, Napverse replaces it with a scoped, one-way opaque value. RevenueCat can receive the Firebase user ID and Amplitude user and device identifiers so subscription and analytics records remain consistent under the applicable provider controls.

Napverse also creates a first-party device identifier from Apple's identifier for vendor when available, or a random UUID otherwise. It stores that identifier on the device, includes it in authenticated backend requests, and uses it to seed a stable RevenueCat app user ID that is also kept in the iOS Keychain. These identifiers do not contain your name or Apple ID, but they can distinguish an installation, device, or anonymous account and associate activity over time. Pseudonymous identifiers are therefore not the same as anonymous data.

Crash, diagnostics, configuration, and security

Firebase Crashlytics may receive crash logs, stack traces, timestamps, app and iOS versions, device information, technical error details, and pseudonymous installation identifiers. Firebase Remote Config and Napverse backend services may process technical request information to deliver configuration, diagnose failures, prevent abuse, and protect the service.

Attribution

Napverse uses Apple AdServices, RevenueCat attribution features, and Meta App Events to measure whether an App Store campaign led to an install, app activation, or subscription. This can include an attribution token, campaign, ad group, keyword and ad identifiers, conversion type, click date, country or region, app and device information, and SKAdNetwork conversion information. Napverse disables collection of Apple's advertising identifier by the Meta SDK in the current configuration. We do not knowingly send baby names, raw routine entries, notes, or media to advertising platforms.

Optional personalized schedules

When you request a personalized or adaptive sleep schedule, Napverse sends the relevant baby identifier, age or age range, timezone, schedule context, and a selected history of exact sleep start and end times and durations to Napverse's Google Cloud backend. The backend uses OpenAI to help generate the requested schedule. Napverse requests that OpenAI not store the response for application-state purposes; OpenAI may retain limited data temporarily for abuse monitoring under its applicable service policies.

Support and cancellation feedback

If you contact support or send cancellation feedback, Napverse receives your message, the optional email address you provide, pseudonymous user and device identifiers, technical context, and any screenshot, video, document, audio, or diagnostic attachment you choose to submit. Support records are stored in private Google Cloud storage and Firestore. The support message, optional email, and private attachment metadata may be routed to LLAPPS LTD through Slack.

4. Sync availability and subscriptions

Sharing and cloud synchronization for a baby require the owner's active Napverse Plus entitlement. A caregiver receives only baby-scoped access and does not receive a personal or account-wide subscription. If the owner's entitlement ends, existing authorized cloud data is retained and remains readable, caregiver writes are blocked, and the owner's local changes wait on the device until service resumes. A subscription lapse does not delete cloud data and does not block privacy and safety actions such as leaving, revoking access, disabling an attachment setting, or deleting a baby or account.

5. Purchases and subscriptions

Apple processes App Store payments. Napverse and RevenueCat may receive an app user ID, Apple receipt and transaction information, product identifiers, entitlement and renewal status, trial or offer information, purchase timestamps, last-seen time, attribution data, and technical app or device information needed to unlock and restore Napverse Plus. Napverse and RevenueCat do not receive your full payment-card details from Apple.

6. Website data and cookies

napverse.app does not set cookies, use local or session storage, run web analytics or advertising pixels, or embed third-party media. The hosting and security infrastructure can still process ordinary request logs such as IP address, user agent, requested path, timestamp, and response status to deliver and protect the website. Because the website uses no optional cookies, no consent choice is required. We display an informational no-cookies notice for transparency; dismissing it does not store a preference.

7. Why we process information

• To provide tracking, optional backup and synchronization, caregiver sharing, summaries, reminders, subscriptions, purchase restoration, support, and features you request.
• To generate personalized schedules and keep server-backed recommendations aligned with recent activity.
• To understand feature adoption, app performance, and campaign effectiveness.
• To diagnose crashes, fix bugs, secure requests, prevent fraud or abuse, and enforce our terms.
• To meet accounting, tax, consumer-protection, and other legal obligations.

8. Legal bases

Depending on the processing and the law that applies, LLAPPS LTD relies on:

• Performance of a contract: to provide requested app, synchronization, sharing, subscription, personalization, and support functions.
• Legitimate interests: to keep Napverse secure and reliable, understand product performance, prevent abuse, and improve the service where those interests are not overridden by your rights.
• Consent: when iOS requests permission for notifications, microphone, camera, photos, or other device access. Non-essential analytics or attribution may also require separate consent; where it does, that processing must remain off until you choose it and must provide an effective withdrawal control. Withdrawing consent does not affect earlier lawful processing.
• Legal obligation: for records or disclosures required by law.

9. Providers and recipients

Limited information may be processed by the following providers for the stated purpose:

• Apple: App Store distribution and billing, notifications, device features, AdServices attribution, SKAdNetwork, ratings, and reviews.
• Google Firebase and Google Cloud: authentication, optional European-region care-data sync and attachment storage, caregiver authorization, content-free notifications, Analytics, Crashlytics, Remote Config, backend APIs, logs, website hosting, and private support storage.
• Amplitude: product-usage analytics and pseudonymous user or device measurement.
• RevenueCat: subscription, entitlement, receipt, identity, and attribution management.
• OpenAI: model processing for personalized schedules requested through Napverse's backend.
• Meta: automatic app events and campaign or install attribution, with advertising-identifier collection disabled in the current app configuration.
• Slack: restricted internal routing of support messages and private attachment metadata.

We do not sell personal information. A provider may process information under its own terms when it acts as an independent controller, such as Apple for App Store transactions.

When a provider processes personal data on our behalf, we require it to use the data only for the agreed service purposes, apply protections consistent with this policy and applicable law, and assist with security and data-subject obligations as required by our agreement.

10. Retention

• On-device data: remains until you edit or delete it, remove the app and its local data, or erase the relevant iPhone backup. Keychain identifiers can persist after reinstall.
• Synced baby and creator-private data: shared profile, activities, Memories, and finalized Memory attachments remain with the baby subject to edits and baby lifecycle; creator-private Time Capsules remain while Sync and the relevant account or membership are active. Ending Napverse Plus pauses synchronization but does not delete retained cloud data.
• Invitations and access requests: an open invitation or pending owner-approval request has no automatic product expiry and remains until it is claimed, withdrawn, rejected, revoked, or removed through baby or account deletion. Minimal terminal operation records are deleted on a limited schedule.
• Baby deletion: access stops immediately and the owner can undo deletion for seven days. If it is not undone before purge begins, the baby profile, shared activity and Memories history, memberships, each participant's creator-private Time Capsules, and synced attachments are permanently deleted from active systems.
• Leaving or losing caregiver access: server access stops immediately and the departing caregiver's private Time Capsules, Time Capsule attachments, and unfinished uploads for that baby are scheduled for deletion without Undo. Shared activities, Memories, and finalized Memory attachments remain with non-identifying former-caregiver attribution. A device that stays offline cannot be remotely erased until it reconnects.
• Account deletion: access is fenced immediately and there is no Undo. An owner's cloud babies, shared Memories, and all participants' associated private scopes are scheduled for deletion. A caregiver's memberships and private Time Capsule scopes are deleted while shared activities, Memories, and finalized Memory attachments remain under former-caregiver attribution. Records and files already present on the initiating iPhone can be retained there only as a new, independent local-only copy. Napverse does not download missing cloud history or files to expand that copy.
• Operational records: content-free security and audit metadata is retained for up to 180 days by default, subject to legal and security review. Minimal terminal operation receipts are normally scheduled for deletion after seven days; certain version or tombstone records may be retained longer to prevent an offline device from restoring deleted data.
• Provider backups and legal holds: deletion from active systems does not promise immediate physical erasure from every provider backup. Backup copies and records required for security, fraud prevention, disputes, or law follow the provider and legal retention that applies.
• Analytics and attribution: retained under the applicable provider and project settings for as long as needed to compare product and campaign trends, then deleted or aggregated. We review retention against those purposes and applicable law.
• Anonymous authentication and linked service identifiers: may remain in Firebase, Amplitude, RevenueCat, and related service records until a verified deletion request is completed or the applicable provider or project retention process removes them. Removing the app alone does not delete these provider records; Keychain identifiers can survive reinstall.
• Crash, security, and backend logs: retained for the provider-configured diagnostic or security period, then deleted or aggregated unless a longer period is needed to investigate abuse, an incident, or a legal claim.
• OpenAI processing: requests are sent with storage disabled for application state; limited abuse-monitoring data may be retained by OpenAI for up to 30 days unless law or a security investigation requires longer.
• Support records: retained while a request is handled and for a limited period afterward to investigate recurring issues, protect the service, and maintain necessary business or legal records, then deleted or anonymized.
• Purchase records: retained as needed to provide and restore entitlements and meet accounting, tax, consumer, fraud-prevention, and legal obligations.

11. Your choices and rights

• You can keep core tracking local-only, choose which babies use Sync, independently control Memory and Time Capsule attachment uploads, edit or delete entries, and control notifications and device permissions in iPhone Settings.
• Where available in the app, you can request a portable export of data you are currently authorized to read. It excludes other creators' private content, hidden activity categories, credentials, invitation secrets, internal routing, and other users' security records.
• You can leave a shared baby, remove a caregiver if you are the owner, schedule or undo baby deletion during its seven-day recovery period, and delete your Napverse cloud account after identity verification. Account deletion is different from signing out and does not cancel an App Store subscription.
• You can manage or cancel a subscription through Apple. Deleting Napverse does not cancel an active subscription.
• You can object to product analytics or request deletion of identifiable provider records by emailing support@napverse.app. Because records use pseudonymous identifiers, we may need an identifier or diagnostic information from the app to locate them.
• Deleting the app stops future collection from that installation but does not by itself erase information already sent to providers or cancel an App Store subscription.

Subject to applicable law, you may request access, correction, deletion, restriction, or portability of personal data, object to certain processing, and withdraw consent. We may need to verify your request and may retain limited information where law permits or requires it.

If you are in the European Economic Area, you may also lodge a complaint with your local supervisory authority or Bulgaria's Commission for Personal Data Protection (CPDP).

12. Children's privacy

Napverse is intended for parents, guardians, and caregivers, not for children to use independently. A user who enters information about a child must be authorized to do so. We do not use child routine information for targeted advertising. Contact us if you believe information was provided without appropriate authority.

13. Security

We use reasonable technical and organizational measures intended to protect information, including authenticated and integrity-checked backend requests, encrypted network transport, provider encryption at rest, least-privilege access, deny-by-default authorization rules, restricted service access, and private support storage. Napverse Sync is not end-to-end encrypted. No system can guarantee absolute security. Please avoid including unnecessary personal or medical details in free-text support messages.

14. International processing

LLAPPS LTD is established in Bulgaria. Napverse's care-data plane is designed to use named European-region Firebase and Google Cloud resources. Firebase Authentication and providers supporting security, notifications, support, analytics, subscriptions, and personalized schedules may process information in the European Economic Area, the United States, or other countries. Where required, transfers rely on adequacy decisions, standard contractual clauses, or another lawful transfer mechanism.

15. Recommendations and automated processing

Napverse can calculate predictions and use model-assisted processing to generate sleep schedules. These outputs are informational planning aids. They do not make decisions that produce legal or similarly significant effects, and they are not medical advice.

16. Changes to this policy

We may update this policy as Napverse or its providers change. We will post the current version at napverse.app/privacy, update the date above, and provide additional notice where required by law.