privacy
photos, videos, and your finished dayloops stay on your phone. dayloop does not upload them.
some day structure syncs to dayloop servers so the app can back up and restore the shape of your day. this page explains what stays local, what syncs, and how to reach us.
what stays on your phone
the media you capture in dayloop stays on your device:
- photos
- videos
- your finished dayloops
dayloop may ask for access to your camera, microphone, and photo library when you use those features. that access is for capturing media, reading media you choose, and saving videos to your camera roll.
what syncs
dayloop syncs day structure to our servers for backup and sync:
- tasks
- day plans
- moment metadata, like titles and times
- names you type as person tags
media is not included in those sync payloads. dayloop sends filenames and durations for moments, not the photos or videos themselves.
if you import calendar events
if you import calendar events, those event details sync too: titles, times, locations, meeting links, participant names and email addresses, and other event details like the calendar's name.
this can include other people's info.
how dayloop recognizes your install
dayloop has no accounts. it does not ask for your name or email when you start using the app.
when you first use dayloop, the app creates a random identifier that can persist. usage and synced day structure are not tied to an account, because dayloop has no accounts.
if you want server-side data deleted, email support@dayloop.org.
analytics and feedback
dayloop records product interaction events: kinds of taps and actions that help us understand what works and what needs attention. those events go to our own backend and then to PostHog, which processes analytics for us.
usage events can include your device model, iOS version, and app version. dayloop does not include a third-party tracking sdk, an ad sdk, or cross-app tracking. we do not sell your data.
if you send feedback, we receive your message plus your device model, iOS version, app version, locale, and timezone. a log excerpt is included only if you choose to send one.
this website sets no cookies and uses no browser trackers. when you use an App Store redirect link, /api/go can record a click event with ref and src values to our analytics when analytics are configured.
reminders and permissions
if you turn on reminders, dayloop stores a push token and notification preferences so reminders can work.
dayloop asks for permissions only when you use a feature that needs them. you can change permissions later in iOS settings.
- camera, for capturing photos and videos
- microphone, for videos with sound
- photo library, for reading media you choose and saving videos to your camera roll
- calendar, for importing your calendar events
- speech recognition, for voice input; this may use Apple's speech service
- notifications, for reminders
retention and deletion
usage events are kept as long as needed to improve dayloop.
synced day structure is kept while your install is active. on-device content stays on your phone until you delete it. deleting the app removes dayloop's on-device content.
to ask us to delete server-side data, email support@dayloop.org.
children
dayloop is not directed at children under 13.
changes
if this policy changes, we will update this page and the date below.
contact
questions and deletion requests go to support@dayloop.org.
last updated: june 11, 2026