NapBaby Privacy Policy

Status: approved_founder_self_attestation Consent version: napbaby-privacy-terms-v1 Effective date: 2026-11-02 Last updated: 2026-11-02

1. Controller Identity And Contact

NapBaby is operated by CONNECT BRANDS LLC, located at 2093A Philadelphia Pike, Suite 418, Claymont, DE 19703, United States. For privacy inquiries, data export requests, account deletion support or questions about this Privacy Policy, contact us at support@napbaby.app.

2. Product Scope And Educational Positioning

NapBaby provides educational baby sleep routine guidance, schedule organization and care logging tools for adult caregivers based on authorized NapBaby educational material. NapBaby is a wellness and routine organization utility; it is not a medical device, clinical monitor, emergency service or substitute for a pediatrician or qualified healthcare professional.

3. Eligibility And Children’s Privacy

NapBaby is intended exclusively for adults aged 18 years or older who declare at account creation (signup:adult-caregiver-v1) that they are the parent, legal guardian or authorized caregiver of the child whose routine is organized in the app. NapBaby is not directed to children and does not knowingly allow children to create accounts or submit personal data directly. Baby profile and care information is processed strictly at the instruction of the authenticated adult caregiver.

4. Data We Collect And Process

• Account and authentication data: email address, password hash, session identifiers, authentication lifecycle timestamps and email verification/password-reset state.
• Baby profile and routine data: baby name or nickname, birth date, optional adjusted birth date/due date, timezone, guidance mode, sleep/wake start and end timestamps, pause intervals, optional caregiver notes, routine phase calculations and micro-lesson progress.
• Lesson progress synchronization: lesson read status and checklist selections are synchronized per authenticated account. Offline changes are queued per account scope and reconciled deterministically when connectivity resumes.
• Local care diary (localCare): breastfeeding, bottle, pumping, diaper, solids, temperature, supplement and symptom entries are stored locally on the current device within the active account scope. They are included when exporting account data from that device and are erased from that device when the account is deleted in the app.
• Optional Luma AI assistant data (Apple Guideline 5.1.2(i)): Luma chat is disabled until the user grants explicit in-app consent on the Luma disclosure screen. After consent, chat messages, the active locale (pt-BR, en-US, es, fr, de, it or zh-CN), necessary baby/routine/recent-care context, approved educational excerpts and conversation history are transmitted to OpenAI (store=false) solely to generate and review the assistant reply. Account passwords and raw session tokens are never included in chat payloads.
• Session vs. optional cloud memory: by default, Luma conversation turns and chat consent remain only in app process memory (expiring after 30 minutes of inactivity or when the app process closes). If the user separately enables Cloud Conversation Memory in Luma settings, up to 20 recent user/assistant turns and routine preferences are stored in the user’s account for up to 30 days and can be cleared or disabled at any time.
• Safety lock records: when an urgent infant or maternal warning sign is reported in chat, an account- and baby-scoped safety lock (luma_safety_state) is recorded on the server to suspend routine coaching until an affirmative whole-statement clinical clearance is confirmed or the account is deleted.
• Subscription and billing data: RevenueCat app user ID mapping, store entitlement status (napbaby_premium), billing period and renewal/expiration state received from Apple App Store, Google Play and RevenueCat. NapBaby does not receive or store full credit card numbers.
• Push notifications: if enabled by the user, device push token, locale, timezone and quiet-hour preferences are processed through Expo and Apple Push Notification service (APNs) to deliver optional check-ins.
• Legal consent and operational diagnostics: accepted consent version (napbaby-privacy-terms-v1), timestamp, consent source, API latency/error metrics and security/rate-limit logs.

5. How We Use Data

We process personal data solely to:

1. Authenticate accounts, maintain session security and prevent abuse.
2. Calculate age-appropriate sleep windows, routine adjustments and history statistics across the 7 supported languages.
3. Synchronize sleep events, lesson progress and subscription entitlements across authorized sessions.
4. Provide opt-in Luma AI educational and operational assistance after explicit user consent.
5. Deliver transactional account emails (verification and password reset) and opt-in push reminders.
6. Process data export (GET /account/export) and account deletion (DELETE /account) requests.
7. Comply with applicable legal, tax, billing and security obligations.

No Sale of Data and No Third-Party Advertising: CONNECT BRANDS LLC does not sell, rent or trade personal or family data to third parties, does not display third-party advertising and does not track users across third-party apps or websites (no IDFA / App Tracking Transparency tracking).

6. Sharing And Subprocessors

We share data only with service providers acting as data processors under confidentiality and security obligations necessary to operate NapBaby:

• Cloud Hosting & Database Infrastructure: PostgreSQL database, Redis cache and encrypted off-host backup storage hosting the NapBaby API.
• OpenAI: processes opt-in Luma AI chat requests (store=false) only after explicit in-app user permission.
• RevenueCat, Apple App Store & Google Play: process subscription purchases, restores and entitlement synchronization.
• Expo & Apple Push Notification service (APNs): deliver opt-in push notifications and app updates/builds.
• Transactional Email Provider: delivers account verification and password-reset links.

Retention

• Active accounts: account, baby profile, sleep history and legal consent records are retained while the account remains active.
• Optional Luma cloud memory: retained for up to 30 days (maximum 20 messages) while enabled, or deleted immediately when disabled/cleared by the user.
• Authentication tokens: password-reset and email-verification tokens are short-lived and automatically purged by scheduled cleanup jobs.
• Account deletion: when a user initiates account deletion in the app (Settings → Account → Delete account) or via support@napbaby.app, active application records (user, baby profiles, sleep events, lesson progress, Luma memory and current-device local care stores) are deleted immediately from active production tables, except minimal records strictly required by law for billing, tax, fraud prevention or security compliance. Encrypted database backups are overwritten according to their rolling backup retention cycle.

8. Your Privacy Rights And Controls (LGPD, GDPR, CCPA & Global Standards)

Depending on your jurisdiction (including Brazil’s LGPD, the EU/UK GDPR and US state privacy laws), you have the right to:

• Access and Portability (Export): download a machine-readable JSON export of your account, baby profile, sleep logs, lesson progress and current-device local care records directly in the app (Settings → Account → Export data).
• Correction (Rectification): edit baby profile details, sleep events and care logs at any time in the app.
• Erasure (Account Deletion — Apple Guideline 5.1.1(v)): permanently delete your account and associated personal data directly inside the app (Settings → Account → Delete account) or by contacting support@napbaby.app.
• Consent Withdrawal: revoke Luma AI chat consent (by closing the session or disabling cloud memory), disable push notifications in app/device settings, or delete your account at any time.

9. Security

NapBaby protects data using HTTPS/TLS encryption in transit, hashed passwords, scoped session tokens, strict account-isolation checks on every API route, per-account rate limiting and restricted database/backup access.

10. Changes To This Policy

If we make material changes to how we collect, use, retain or share personal data, we will update this policy and increment the required LEGAL_CONSENT_VERSION so users can review and accept the updated terms before continuing to use gated features.