DayPace is built to track your workday without turning your work records into an advertising product. Your work and break entries are stored on your devices, and iCloud backup uses your private iCloud database when you enable it. DayPace uses limited product analytics to understand whether the app is useful, while keeping work records private by default.
Information DayPace Stores
DayPace stores the information needed to run the app:
- Work and break events, including start and end times, correction records, and whether the event came from iPhone or Apple Watch.
- App settings such as your daily target hours.
- Local sync metadata used to reconcile changes between your iPhone, Apple Watch, and iCloud backup.
- A subscription entitlement snapshot shared from the iPhone to the Apple Watch so the Watch can know whether DayPace Pro is active.
Where Information Is Stored
DayPace stores work records locally on your device. If iCloud backup is available and you use it, DayPace stores work event records in your private CloudKit database under your Apple account.
DayPace uses WatchConnectivity to transfer work records, daily target settings, and subscription status between your own iPhone and Apple Watch.
Purchases
DayPace Pro subscriptions are purchased through the App Store. DayPace uses RevenueCat to manage subscription status. RevenueCat may receive purchase identifiers, transaction information, app user identifiers, device information, and receipt data needed to validate purchases and keep your entitlement in sync.
DayPace does not send your work-hour events, timelines, schedules, break records, exported backups, or daily targets to RevenueCat.
Product Analytics
DayPace uses PostHog to understand basic product usage, such as whether onboarding is completed, whether a work or break action was started from iPhone or Apple Watch, whether the paywall was shown, and whether a purchase flow succeeded or failed.
PostHog may receive app, device, and network metadata needed to process analytics events.
DayPace may also show optional in-app feedback surveys through PostHog. Survey responses are sent only if you choose to submit them. If you choose to include your email address in a survey, DayPace will use it only to follow up about your feedback.
Analytics events use coarse properties, such as time-of-day buckets, duration buckets, and whether an action came from iPhone, Apple Watch, a complication, or a manual entry. DayPace does not send exact work start or end times, timeline histories, exported backups, employer names, project names, notes, location, contacts, calendar data, or private iCloud records to PostHog.
Information We Do Not Collect
DayPace does not currently use third-party advertising, does not sell personal data, and does not collect location, contacts, calendar events, photos, microphone data, or health data.
Support Requests
If you contact support, we will receive the information you choose to include, such as your message, screenshots, device details, or diagnostic context. Do not include sensitive work records in public GitHub issues.
Exporting and Deleting Data
The app includes Data & Backup controls for CSV export, JSON backup export, JSON backup import, and iCloud backup reset. You can delete local DayPace data by deleting the app from your devices. App Store subscriptions can be managed or canceled in your Apple account settings.
Children
DayPace is not directed to children and does not knowingly collect personal information from children.
Changes
This policy may be updated as DayPace changes. The updated version will be posted on this page with a new effective date.
Contact
For privacy questions, start from the DayPace support page.