The app and this policy
This policy covers Daily Sleep, displayed as SleepApp on your device, including its iPhone/iPad app, Home Screen widget, Watch app and complication. BigBeeFit provides product and privacy support at nine@bigbeefit.com. The app developer is identified on its App Store listing.
This policy describes the app. Browsing this website is covered separately by the BigBeeFit website privacy policy, including its website analytics. Those website tools are not included in the SleepApp application.
Website privacy policyNo account. No developer data server.
The app does not require registration or sign-in. Sleep, heart rate, manual entries and corrections are processed on your device. We do not receive them on a developer server. The app has no third-party advertising, analytics or crash-reporting SDK and does not use your health information for tracking, advertising or AI processing.
Apple Health access is your choice
When you choose Connect Apple Health, or confirm a new manual entry with write-back enabled, the app may request access to read sleep and heart rate and to write sleep. Reading lets it show duration, stages, sources, overlapping heart rate and history. An empty result does not establish that read permission was granted.
Sleep is written only after you confirm a new record for a real past interval, with write-back enabled and Health permission available. Corrections, awake markings, hiding and undo for existing nights stay local and do not change other sources in Health. If local saving fails after a write, the app attempts to remove only the sample it just created.
You can change access in Apple Health or system Settings. You can use confirmed local manual entries with write-back turned off, even without Health data. Granting permission does not guarantee that your device contains sleep or heart-rate records.
Local storage and device access
The app keeps manual entries, local corrections and its last displayed sleep/heart-rate cache in local files. These files are excluded from device backups and use file protection that permits access after the first device unlock following a restart, including while the device later locks. Preference settings use system preference storage; the same file backup rule does not apply to them.
Source/device details from Health are used locally to distinguish records. They are not uploaded to us. The widget and Watch read Health independently after access is allowed; local-only iPhone corrections are not shared with them through an App Group or a developer sync service.
Local morning notifications
The morning reminder switch is on by default. Delivery also requires system notification permission and depends on Health updates and system scheduling. Notifications may contain sleep duration and bedtime/wake time, including on the Lock Screen according to your system settings. Turn the switch off to cancel the app's pending morning notification; you can also control previews or notifications in system Settings. These are local notifications, not server pushes.
Purchases and Apple services
Apple handles the annual auto-renewing subscription, payment, renewal and refund process. The app checks StoreKit entitlement status on the device to determine which features are available. It does not receive your payment-card details. Apple Health and App Store services operate under Apple's own terms and privacy practices.
Retention, deletion and support
Removing the app removes its local files. Samples already written to Apple Health remain there and must be managed in Apple Health. There is no app account to delete and no developer-hosted copy of your sleep history. Deleting the app does not cancel an Apple subscription.
If you email support, we receive the information you choose to send and use it to handle your request. Please do not send raw Health exports or Apple ID passwords. Redact health values in screenshots. Contact us to ask about or request deletion of support correspondence, subject to any applicable retention requirements.
Contact privacy supportPolicy changes
Changes to the app's data practices will be reflected on this page with an updated effective date. Contact us if you have questions about a change.