Your family data is not our business model.

This privacy policy covers both dadyolked.com and the DadYolked iOS app (available on the App Store). DadYolked is built to be local-first and private by design.

Last updated: August 2, 2026

v1.1 updates: Dynamic background-refreshed notifications, fully functional Siri and App Intents that adapt to pregnancy or post-birth mode, improved birth preparation checklist, and stronger deep-link support for widgets and Live Activities. All new features continue to keep your family data local-first on your device with the same privacy commitments.

The short version: DadYolked is local-first. Parenting data stays on your device unless you explicitly export it, share it through Apple’s CloudKit shared-care flow, or enable an Apple system integration. Assistant Q&A history is stored in protected local app storage and can be cleared or included in an export. We use Firebase Crashlytics to find and fix crashes. We do not sell your data, run ads, or share your information with data brokers.

1. Who we are

DadYolked is developed and maintained by George Zikry. If you have questions about this policy or how your data is handled, email support@dadyolked.com.

2. Data you add to DadYolked Local first

You may choose to add pregnancy details, dad and child profiles, feeding logs, sleep logs, diaper logs, medicine logs, contraction sessions, kick counts, milestones, journal entries, reminders, appointments, photos, and dad wellness check-ins.

DadYolked uses this data only to power the app features you request. Family logs, journals, timers, and baby-care records are stored on your device by default using Apple-protected app storage.

ProfilesOptional names, due dates, birth dates, and app mode.

Care logsFeeding, sleep, diaper, medicine, kick, contraction, and timer history.

Journal & momentsText entries and optional photos you choose to attach.

Appointments & remindersDates, notes, checklist states, and local notification preferences.

3. Storage and shared care through Apple CloudKit

DadYolked does not operate a general-purpose parenting-data server. If you choose to invite a caregiver, DadYolked uses Apple CloudKit and Apple’s CKShare system to synchronize the specific shared-care workspace you select. The Apple share—not an invitation URL, SMS message, caregiver label, or code—is the authorization boundary.

A recipient must review and accept Apple’s share invitation before access is granted. Shared records may include the care logs and profile information you deliberately place in that workspace. Private journal bodies, private mood notes, and other non-shared records remain outside the shared projection unless you explicitly share them through an app flow. Apple’s handling of iCloud data is governed by Apple’s Privacy Policy.

4. Photos

Photos are selected through Apple’s system photo picker and are used only for in-app memories, milestones, profiles, or journal features you choose. We do not use photos for advertising or brokered data sale.

5. HealthKit, Calendar, Speech, Location, and optional Apple features

Apple Health / HealthKit

If you grant Health access, DadYolked may read sleep or step data for features such as personalization or dad recovery context. DadYolked does not sell HealthKit data and does not use it for advertising.

Apple Calendar

If you grant Calendar access, DadYolked uses it only for the feature you enabled, such as adding appointments or reading care-related events for personalization.

Speech Recognition and microphone

If you use voice features, your speech is processed by Apple’s speech-recognition technology. Depending on your device and system support, audio may be processed on-device or by Apple servers. DadYolked does not receive or store your audio recordings.

Location and MapKit

If you use hospital or address search, DadYolked may request approximate location solely to bias results toward nearby facilities. Search queries and location context are handled through Apple MapKit. DadYolked does not store or sell your location.

On-device suggestions

On supported devices, Apple on-device intelligence may help refine coaching text. When on-device models are not available, DadYolked uses built-in local guidance. Parenting logs are not sent to DadYolked servers for this feature.

You can revoke permissions at any time in iOS Settings.

6. Crash reports and diagnostics Firebase Crashlytics

DadYolked uses Firebase Crashlytics, provided by Google, to collect crash reports when the app unexpectedly closes. This helps us identify and fix bugs.

Crash reports may include stack traces, device model, iOS version, app version, crash state, a randomly generated Crashlytics installation identifier, short one-way hashes of optional names, and limited app state such as whether the profile is in Expecting or New Dad mode.

This data is processed by Google under Firebase’s Privacy Policy and Google’s Privacy Policy. Crash data is used for app reliability, not advertising.

7. Notifications, Live Activities, and widgets

DadYolked schedules local notifications for reminders such as daily tips, kick counts, feeding windows, nap timers, appointments, medicine, and mood check-ins. These are scheduled on your device using iOS notification APIs.

Contraction, nap, and feeding timers may use Live Activities, Dynamic Island, widgets, and watch complications. These features are designed to operate locally and display the information you choose to track.

8. No ads, no tracking, no data brokers

No advertising SDKs.
No data broker integrations.
No sale, rental, or trade of personal data.
No third-party tracking for advertising.

9. Assistant Q&A and on-device intelligence

Assistant questions and answers are stored locally in protected app storage to provide bounded history and follow-up context. You can clear history for one child or all children. Generic Assistant requests receive minimal active-child context; private journal bodies, mood notes, and free-text medical/allergen details are not automatically included.

On supported devices, Apple on-device intelligence may refine responses. When unavailable, DadYolked uses deterministic local fallbacks. DadYolked does not send parenting logs to an unapproved external AI service. Assistant-generated text is informational and cannot silently perform privileged app actions.

10. Third-party processors

Google / Firebase: crash reporting through Crashlytics.
Apple iCloud / CloudKit: optional private sync and system storage services.
Apple MapKit: hospital and address search suggestions when used.
Apple Speech Recognition: voice transcription when used.
Apple HealthKit and Calendar: optional system integrations when permission is granted.

11. Export and deletion

You can export supported data from inside the app, including Assistant Q&A history in the JSON backup. You can clear Assistant history by child or globally. The app’s delete-all-data flow removes SwiftData records and protected Assistant history; shared CloudKit records and shares may require separate Apple/iCloud actions and are subject to Apple’s retention and deletion behavior.

For deletion requests or privacy questions, contact support@dadyolked.com. Crash reports are associated with a random installation identifier rather than an Apple ID or email, so individual crash records may not always be retrievable, but we will make a good-faith effort to help.

12. Children’s privacy

DadYolked is designed for expectant and new fathers, parents, and caregivers. It is not directed to children under 13, and children should not create or manage app data.

13. Changes to this policy

If we make material changes to this Privacy Policy, we will update the “Last updated” date above and, where appropriate, notify users through the app or App Store release notes.

14. Contact

Questions, concerns, or deletion requests? Email support@dadyolked.com.