This Privacy Policy explains how Maria Varvaroi (trading as Next Nap, “we,” “us”) collects, uses, and protects information when you use the Next Nap iOS app, Live Activities, website, and related services (the “Service”).
By using Next Nap, you agree to this Policy. If you do not agree, do not use the Service.
1. Who we are / contact
- Controller: Maria Varvaroi
- Privacy / data requests: support.nextnap@gmail.com
- Support: support.nextnap@gmail.com
- Website: https://nextnap.app/privacy
2. Who the app is for
Next Nap is built for parents and caregivers. It is not directed at children. We do not knowingly collect personal information directly from children under 16 (or the age required in your country). Baby information is entered by adults about children in their care.
3. What we collect
Depending on how you use Next Nap, we may process:
A. Account / household information
- Apple ID / iCloud identity used for CloudKit sync and Family/household sharing (when you enable sync)
- Optional contact details you send us (e.g. support email)
- Household / co-parent invitation and membership information needed to share a baby’s timeline
B. Baby and care logs you enter (core product data)
Examples: sleep and nap intervals, wake times, schedule projections, feeds, diaper changes, vitamin D / walks / “Other” logs, child profile details you add (e.g. first name, birth date / age for norms), photos you attach to a crest or profile if that feature is enabled, and similar caregiver notes. §4 explains where these logs stay and when they reach us.
C. Device, diagnostics, and usage
- Device type, OS version, app version
- Sync and diagnostic logs, kept on your device. We only see them if you send them to us
- Crash reports and performance data such as launch time and hangs, only if you choose to share analytics with app developers in iOS Settings (delivered by Apple)
- Approximate technical signals needed for push notifications and Live Activities
- We do not need precise GPS for core tracking
D. Purchases
- Purchase and subscription status via Apple (we do not receive your full payment card details)
- RevenueCat, Inc. manages subscriptions for us. It receives an app user ID, your purchase history, a device identifier (IDFV), and events from the subscription screen, whether or not you allow tracking. It does not receive payment card details
E. Website
- Standard server logs; cookies or analytics only if you enable them on the site (none listed yet)
F. Ad measurement (Meta, only if you allow tracking)
The App Store version of Next Nap includes the Meta (Facebook) SDK so we can measure which ads lead people to the app. iOS asks for your permission right after your first trial or purchase. The SDK starts only if you tap “Allow”. Meta then receives:
- Your device’s advertising identifier (IDFA) and Meta’s anonymous ID
- The event for your first trial or purchase, with the price and currency of a paid plan
- Any app events, such as the app opening, and any SDK crash data that the Meta SDK logs automatically
- Device details sent with those events, such as device model, iOS version, language, and time zone
After you allow tracking, RevenueCat also receives the advertising identifier, Meta’s anonymous ID, and your IP address. RevenueCat can then send Meta later purchase events, such as a trial that becomes a paid plan. Renewals are not sent.
If you deny tracking: tap “Ask App Not to Track” when iOS asks. The SDK does not start, we share nothing with Meta, and the app works fully. You can also turn tracking off any time in Settings > Privacy & Security > Tracking. The SDK then no longer starts, and RevenueCat stops sending Meta events once you next open the app.
Nothing about your babies is shared with Meta or any advertiser. Your care logs, names, photos, and schedules are never sent to them.
G. App Store privacy label
The App Store label for Next Nap lists the data types below. These types are used for tracking, which means ad measurement with Meta after you allow it:
- Device ID - the advertising identifier and Meta’s anonymous ID (§3F)
- Purchases - your trial and purchase events (§3F)
- Product Interaction - app events from the Meta SDK (§3F)
- Advertising Data - the data in §3F, which Meta uses to connect an ad to an install
These types are not used for tracking:
- User ID - RevenueCat’s app user ID, and the private ID of your Write to Maria conversation
- Crash - crash reports delivered by Apple (§3C) and any SDK crash data (§3F)
- Performance - performance data delivered by Apple (§3C)
- Customer Support - the messages you send us
- Health - the sleep, feed, and diaper logs you send through Write to Maria (§4)
- Sensitive Info - your babies’ birth dates, in the logs you send through Write to Maria (§4)
- Other Diagnostic Data - the app’s sync log and the technical details sent with your messages (§4)
- Other Data Types - other analytics data that Meta’s SDK says it may collect, not linked to you (§3F)
Device ID, Purchases, and Product Interaction also cover the data RevenueCat receives to run subscriptions (§3D). RevenueCat sends data to Meta only as §3F describes.
4. Health and sleep data
Your baby’s sleep logs and other care logs (§3B) stay on your device. If you sign in to iCloud, they also sync through your iCloud account to the caregivers you invite. We cannot read them on your device or in your iCloud. Without iCloud, your logs stay on your device and the app works the same.
A. If you send your logs through Write to Maria
We see these logs only if you send them to us. In the app, you can do that through Write to Maria. The “Include my log” switch is on by default, so check it before you send a message:
- With the switch on, we receive your logged sleep, feeds, and diapers, with their times and amounts. We also receive your babies’ birth dates and any wake-window settings, and the app’s sync log
- The log leaves out your babies’ names and everything else you log, such as notes, Moments, vitamin D, walks, moods, and milestones. It calls your babies “Baby 1”, “Baby 2”, and so on. We see a name only if you type it in your message. The log has no names, but birth dates, your time zone, and your message could still point to your family
- With the switch off, we receive no log and no birth dates
- Every message also includes your words and technical details: app version, iOS version, device model, your role in the household, the number of babies and their ages in weeks, your time zone, and a push token so we can notify you of a reply
B. How we use what you send
We use your messages and logs only for support, including finding the cause of a problem you report. We never use them for advertising or marketing. We never share them with Meta or any ad network. We never sell them.
Cloudflare stores your messages and logs. Telegram delivers your words and the technical details above, except the push token, to our team’s chat, where they stay until you delete them. Your log does not go through Telegram. Our team’s chat holds only a private link to it, which expires after 7 days. Grok Bot, an AI agent from xAI that runs on Cursor’s cloud, reads your message and any attached log to draft a reply, and our team’s chat shows its summary and draft. We use these providers only to answer you. A person reads every message and decides what is sent to you.
We delete attached log files automatically after 90 days. Grok Bot’s short summary and draft reply can stay with your message. We keep your messages until you delete them or ask us to.
C. How to delete what you sent
- To delete everything in the app, open Settings > Danger zone and tap “Delete everything & start over”. If someone invited you to their household, tap “Leave household & delete my copy”. Either one deletes your Write to Maria conversation and its logs from our server. Either one also erases your app data on this phone, and “Delete everything & start over” also removes the household from iCloud
- Replies we wrote can stay in our team’s chat. If the app cannot finish the deletion, it offers “Delete on this device only”. That option can leave your conversation on our server, so try again online or email us
- To keep your logs in the app, email support.nextnap@gmail.com, or ask in Write to Maria with the switch off. Ask us to delete what you sent, and tell us roughly when you wrote so we can find it
5. How we use data
We use data to:
- Provide logging, schedules, insights, reminders, Live Activities, and multi-caregiver sync
- Operate, secure, debug, and improve the Service
- Respond to support requests
- Meet legal obligations (e.g. accounting, fraud, regulatory requests)
- Process subscriptions through Apple and RevenueCat
- Measure which ads bring people to the app (Meta, only after you allow tracking, see §3F)
We do not sell personal information.
We do not use baby care logs for advertising or marketing. We use the logs you send us only for support (§4).
We do not train public AI models on your family logs.
6. Sharing
We may share data with:
- Apple - App Store, CloudKit / iCloud, push, In-App Purchases, as needed to run the Service
- RevenueCat, Inc. - subscription management; receives the data in §3D, not payment card details. If you allow tracking, it also receives the identifiers in §3F and can send Meta later purchase events
- Meta Platforms, Inc. (Meta SDK) - ad measurement, only after you allow tracking; receives the data in §3F. If you deny tracking, we share nothing with Meta
- Cloudflare, Inc. - stores your Write to Maria messages and logs (§4), and hosts our website
- Telegram - delivers your Write to Maria messages to our team’s chat (§4)
- xAI and Cursor (Grok Bot) - read your Write to Maria messages and logs to draft replies (§4)
- Co-parents / caregivers you invite - they see shared household baby data you choose to sync
- Authorities when required by law
- Successors in a merger or sale, with notice where required
We may share aggregated or anonymized statistics that cannot reasonably identify you or your child.
7. International transfers
If data is processed outside your country (including via Apple or other processors), we use appropriate safeguards required by applicable law (e.g. Standard Contractual Clauses where relevant).
8. Retention
- On-device data remains until you delete it or remove the app (subject to device backups)
- Synced CloudKit / household data is retained while the household is active and as needed to provide sync
- Write to Maria log files are deleted after 90 days, and messages stay until you delete them or ask us to (§4)
- After account / household deletion, we delete or anonymize personal data we control within a reasonable period, except where law requires longer retention (e.g. transaction records)
9. Your rights (incl. GDPR)
Depending on where you live, you may have rights to access, correct, delete, restrict, object, or port your personal data, and to withdraw consent where processing is consent-based.
- In-app: use Settings deletion / data controls where available
- Email: support.nextnap@gmail.com
- You may lodge a complaint with the data protection supervisory authority in the country where you live
10. Account and data deletion
If Next Nap supports account or household creation / sync identities, you can initiate deletion in the app (Apple requirement). Completing deletion removes the account/household association and personal data we are not legally required to keep. Device backups and Apple-controlled systems may take additional time to clear. §4 explains how to delete what you sent through Write to Maria. In-app deletion does not reach data that RevenueCat or Meta already received. To request deletion of that data, email support.nextnap@gmail.com.
11. Children’s privacy
Next Nap is not directed at children (§2). Parents and caregivers enter the baby’s data and control what they enter. Where the GDPR applies, a parent or guardian has the right to access the personal data we hold about their baby and to ask us to delete it. To make either request, email support.nextnap@gmail.com. Contact us to request deletion of child-related personal data you believe was provided without appropriate consent.
12. Security
We use reasonable technical and organizational measures (device encryption, transport encryption, CloudKit access controls, least-privilege practices). No method is 100% secure.
13. Third-party links
Links to other sites are not under our control; their policies apply.
14. Changes
We may update this Policy. The “Last updated” date will change; material changes may also be noted in-app or on the website. Continued use after the effective date means you accept the updated Policy where permitted by law.
15. Contact
support.nextnap@gmail.com · Next Nap · Maria Varvaroi