Your sleep data is deeply personal. SleepDaddy is engineered from the ground up to inspect HealthKit sleep metrics directly on your iPhone with zero external servers, zero tracking, and strictly read-only access.
SleepDaddy requests permission to read HKCategoryTypeIdentifier.sleepAnalysis records from Apple HealthKit. Our app never asks for write permissions, cannot create sleep records, and cannot alter or delete your HealthKit samples.
Your original health data in Apple Health remains completely untouched, pristine, and managed solely by iOS.
User customizations — such as source filter selections (e.g., Apple Watch vs. Oura Ring), night boundary offsets (7 PM – 7 AM cutoff), and awake spike threshold toggles — are saved locally in UserDefaults via PreferencesStore.
No preferences or settings leave your device. There are no remote databases, cloud sync services, or external profile stores.
SleepDaddy contains zero analytics SDKs, zero crash reporting trackers (e.g., Firebase, Crashlytics), zero advertising frameworks, and zero network transmission code.
The app operates completely offline. We do not track how often you open the app, what sleep stages you achieve, or which devices you use.
All data analysis, stage boundary calculations, source filtering, and rendering are computed locally on your device's CPU and GPU.
No external APIs, cloud servers, or third-party web services are ever contacted during timeline inspection.
Because SleepDaddy collects no data, we have no personal data to access, delete, or export. If you have architectural questions about our open design or local HealthKit processing, feel free to reach out.
