Privacy Policy
Daylogger for iOS, iPadOS, and macOS
Daylogger is built to work without collecting your data. This policy explains, in plain terms, what data the app touches, where it goes, and what the developer can and cannot see.
The short version
- Your entries, tasks, and calendar data are stored on your device and, if you turn on CloudSync, in your own private iCloud database.
- The developer cannot read, access, or download your data. There is no company server that stores your content.
- Daylogger does not use analytics, advertising, or tracking SDKs of any kind.
- A small relay service is used only to deliver Live Activity updates (Lock Screen timers) between your own devices. It never sees your data see “The Live Activity Relay” below.
Data storage on your device
All of your Daylogger content (logs, tasks, timers, and settings) is stored locally in the app's private storage on your device. This data is sandboxed by iOS/macOS and is not accessible to the developer, to other apps, or to any third party.
CloudSync (iCloud)
- If you enable CloudSync, your data is synchronized between your own devices using Apple's CloudKit, in the private database associated with your iCloud account.
- This data is end-to-end encrypted in transit and at rest under Apple's standard CloudKit protections.
- It lives in your personal iCloud storage, counts against your iCloud quota, and is governed by Apple's own privacy policy.
- The developer has no access to this database. Apple's CloudKit private database is, by design, readable only by the account that owns it.
- Turning CloudSync off stops new data from syncing; data already on a device stays on that device.
CloudSync is a bridge to Apple's infrastructure, not a developer-run backend. If you're evaluating this policy, the relevant question is Apple's private-CloudKit-database guarantees, not anything hosted by the developer.
The Live Activity Relay
Daylogger can show a Live Activity on the Lock Screen, for example, a running timer, and keep it in sync across your devices (starting a timer on your Mac can raise the same Live Activity on your iPhone). Apple's push service, APNs, requires a small always-on relay to deliver that push, since your Mac cannot push directly to your iPhone. That relay is a minimal Cloudflare Worker the developer operates for this one purpose.
What passes through the relay
- A device push token (assigned by Apple) for each of your devices that can display Live Activities.
- A hashed identifier derived from a secret your devices share privately through your own iCloud account. Not the secret itself, and not anything tied to your Apple ID or identity.
- The minimal Live Activity content needed to render the update (e.g. a timer's name and start time) for the moment it takes to deliver the push.
What does not pass through the relay
- Your logged entries, tasks, notes, or any other app content not currently shown on an active Live Activity.
- Your name, email, Apple ID, IP address history, or any other identifying information.
- The plaintext group secret itself — only a one-way hash of it is ever stored.
This relay exists solely to route a push notification between your own devices. It is not used to collect, profile, or retain information about you, and it is not shared with, or accessible to, anyone but the developer for operating the relay itself.
Third parties
Daylogger does not integrate any advertising network, analytics SDK, or crash-reporting service that phones home to a third party.
The only outside infrastructure involved is Apple (CloudKit, APNs, App Store) and, only for Live Activity delivery, the developer's own Cloudflare Worker described above.
Children's privacy
Daylogger is not directed at children and does not knowingly collect information from anyone. Because the app collects nothing, there is no data to distinguish by age.
Contact
Questions about this policy or how your data is handled: support@daylogger.app
Daylogger is a personal, independently developed project — please see the Support page for what to expect from a response.