

1Know where it lives
Your todos, habits, money, journal and everything else are stored in your Dawnlet account, in a database where every row records the account it belongs to. The database itself only ever shows a signed-in account its own rows, so one account can never read or change another's, and someone who isn't signed in gets nothing at all. That check doesn't depend on the app getting it right: it's enforced where the data is.
You sign in with Apple, and nothing else. Two pieces of identity are kept, no more:
- Your email, as Apple provides it. If you chose Hide My Email, it's a private relay address and Dawnlet never sees past it.
- Your name, only if you shared it when you first signed in, saved with your account so it survives a reinstall.
Neither is used to identify you, and neither is used for email or marketing.
Your account is tied to the Apple ID you signed in with. Lose access to that Apple ID and you lose access to your Dawnlet data, as the terms explain.
2Use it on every device
There's one copy of your data, in your account, and every device reads that same copy. Sign in on your iPhone and iPad with the same Apple ID and you're looking at the same day.
- Changes save straight to your account. Your other devices pick them up when they next refresh: when you come back to the app, when you pull down to refresh, and whenever you go back to Agenda more than a minute after it last loaded.
- The Apple Watch signs in on its own and talks to your account directly, so it doesn't need the phone nearby. A timer you change on the Watch tells the phone straight away.
- Signing out on the phone signs the Watch out too, even if it's switched off at the time: its sign-in stops working, and it clears itself.
Just switched devices? Pull down to refresh and you'll see what you did on the other one, with no waiting for the app to notice.
3Know what works offline
Your account is the one place your data lives, so Dawnlet never keeps a second copy to merge later. What it keeps on your device is a protected copy of what you last loaded, plus a queue of the changes you make while you're away, and that is enough to carry on:
Dawnlet keeps working offline. Almost anything you add, tick off, change or delete is saved on your device and sent, in the order you made it, once you're back online - the offline pill counts what's waiting. What the offline copy holds is kept only on this device, can't be read while the device is locked, and is left out of backups. Signing out removes it.
| With no connection | |
|---|---|
| Opening the app | Works. Agenda, habits, todos, events, the Time tab, gratitudes, meals, books, movies, places and Lens show what was loaded last, with your own week start and layout. |
| Notifications | Work. Notifications are scheduled on your phone up to two weeks ahead, so they arrive with no connection and the app closed. |
| Widgets and Spotlight | Work, from what the app last saved on the device. |
| Ticking off, skipping, counts and mood | Work, and sync later - from the app, Siri, the controls and Apple Watch. |
| Adding | Works for todos, habits, events, gratitudes, meals, journal entries, one-off transactions, places, books, movies and time logged by hand, and for anything you share to Dawnlet. |
| Editing, moving and deleting | Works for those items too. An edit is applied only if nothing else changed the item since; otherwise yours waits under Couldn't Sync. |
| The timer | Works on iPhone and Apple Watch: start, switch, pause and stop, synced in order. |
| Still needs a connection | Repeating todos and events (making or changing a series), recurring transactions and budgets, categories, tags and activities, people you haven't added before, linking a habit to Apple Health, changing settings, and rereads, rewatches and revisits. |
Dawnlet's rules still apply while you're offline: a trip whose dates clash, or time that overlaps a session you've logged, is caught as you save. If something can't be saved once you're back - another device changed the same item first, say - Dawnlet tells you once and keeps it under Settings → Couldn't Sync, where you can copy it, discard it, or use Edit & Retry. Signing out with changes still waiting warns you first, because signing out discards them. What's kept on your device, and how it's protected, is in the privacy policy.
Heading somewhere with no signal? Open Dawnlet once before you go. Your day is then there to read on the way, and anything you add waits on your device until you're back online.
4Take it with you Plus
Settings → Data & export turns your data into files you can keep:
Categories and tags come out as their names rather than codes, and dates are written in your own time zone, so a late-evening journal entry stays on the day you wrote it. The Data & export row is visible on the free plan too, so you can see exactly what you'd get before you subscribe. Reports, which can also be saved as a PDF, are covered in Insights & badges.
5Clear out the examples
A new account starts with examples in nearly every module: categories and tags, a few habits and todos, events, places, books and movies, a month of spending, a meal, a gratitude and a welcome journal entry. They're there so the app isn't empty on day one, and they never count toward a badge.
When you're ready, choose Delete Sample Data in Settings, or tap Delete on the "Finish setting up Dawnlet" banner. It removes every example you haven't used, all at once:
- Your categories and tags stay, as a starting set to build on.
- Anything you've used is kept: an example you checked off, tracked time on or finished is yours now.
- The option disappears once there's nothing left to delete.
Keep the examples for your first few days and copy what works, then delete them in one go. Tapping Keep on the banner hides it, and the Settings option is still there whenever you're ready.
6Delete your account
Settings → Delete Account deletes your account and everything in it. Dawnlet asks you twice: once in the app, then with the Sign in with Apple sheet as a final confirmation. Deleting your account doesn't cancel a Dawnlet Plus subscription; the first prompt says so and links to Manage Subscription. After that it happens straight away, on the server:
- every row in every module goes with the account, nothing left behind;
- Dawnlet's access to your Apple ID is revoked, so signing up again later really does start from nothing;
- there's no grace period and no recovery.
Deleting can't be undone. If you might want your history later, export it first (Play 4). The Delete Account prompt has an Export My Data First button that opens a CSV or JSON export of everything, free on every plan, and brings you back to the prompt.
Deleting your account, like deleting sample data, is free. Removing your own data is never behind a paywall.
7Nothing is watching
The app has no ads, no tracking and no analytics. Your notifications are planned on your phone, with no notification server. A few more choices keep your things off screens you didn't mean them for:
- Watch complications show counts, never titles.
- Lock Screen widgets show counts, never titles.
- Journal entries and transactions stay out of Spotlight until you switch them on.
- Handoff carries only which screen or item you had open, never its contents.
- Apple Health is read on your device only and never written to: for the habits you link, for Agenda's Health card, and with Plus for Patterns and Reports (sleep). Only a habit's check-in leaves your phone - never your steps, sleep or workouts.
The full detail is in the privacy policy, and the Everywhere playbook covers each of those surfaces.
§Under the hood
Dawnlet's database is Supabase Postgres, and every table follows the same template: each row records its account, row-level security is switched on, there's one rule each for reading, adding, changing and deleting, all limited to the signed-in account, and an explicit grant of those four to signed-in users. That last step looks redundant and isn't: the database checks the grant before the row rules get a chance to run, so without it every request simply fails.
- Badges are add-only. An earned badge can be read and added, never changed or removed, so no bug can take one back.
- Reads are complete. The database returns at most a thousand rows per request, so every list is read a page at a time until it's all there. A long history never quietly turns into part of one.
- Saves are whole. Anything that's really several changes, like replacing an item's tags, runs as one step inside the database that either completes or changes nothing. Money is sent as exact decimals, to the cent.
- Account deletion is one small server function. It needs a key that must never ship in an app. It checks your session and deletes that account, and takes no account ID as input, so it can't be pointed at anyone else's. Every row is linked to its account with cascade delete, so there's no cleanup list to fall out of date.
- The examples are seeded by the database the moment your account is created, with dates worked out so nobody is handed a todo that's already overdue.
Sources: Supabase's guide to row level security, PostgreSQL's GRANT, the grant checked before the row rules, and Supabase Edge Functions, where account deletion runs.