Privacy policy
Effective 29 October 2026
The short version
- Diurnal requires an account: Google, or email and password.
- Your tasks, their history, tags and settings sync between your devices.
- Your tasks are kept on your Mac or phone, so it works offline.
- Voice capture is on the Mac only. Apple’s speech engine turns it into text, never Diurnal’s servers.
- Google Calendar is optional and separate from signing in.
- Nothing is sold or used for advertising.
- Signing out empties that device.
Exact scopes and hosts: Data & permissions.
What is collected
- Account identity. Your name and email address, a scrambled copy of your password if you set one, and for Google sign-in your Google account’s identifier.
- Your content. The tasks you write and their notes, your tags, projects and settings, and each task’s history: what changed, when, and whether you or Diurnal made the change. Auto-clean runs on your devices, and a task it moves is recorded in that history like any other change.
- Feedback you send, with your email address so a reply can reach you. It is also emailed to the support inbox.
- Crash reports from the Mac and Android apps. When Diurnal crashes on a Mac, or the Android app recovers from an error, the technical details (and on a Mac the app’s last few steps before it), never the words you wrote, are sent once you are signed in and emailed to the support inbox.
- A device identifier. A random identifier for each install of the app, written on every change it syncs. It names no person and no phone.
- Server logs. Request timing and errors, the ordinary records of running a service. A log line can name your account’s identifier or your email address.
- If you connect a calendar: authorisation tokens, and the events for the days on screen.
Nothing is read from your phone’s contacts, location, photos or microphone. Each item above exists to deliver a feature you asked for. None of it builds a profile or serves advertising.
Calendar data
Used for one thing: showing your events beside your tasks, and creating one when you ask. It is not analysed, mined, used to train anything, or shared.
Diurnal requests the narrowest Google scopes that do that; the list and the reasoning are on Data & permissions.
Diurnal’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
AI apps you connect
You can connect an AI app, such as Claude, to your account through Diurnal’s MCP server. Nothing is shared until you sign in from that app and click Allow.
- What it can reach: your tasks, tags and projects, which it can read and change, and your Google Calendar events, which it can only read. Nothing else on your account.
- What Diurnal receives: the requests the app makes, such as a task to add or a day to list. Diurnal never sees your conversation with the app.
- What the app receives: the answers to those requests. From then on the app holds them under its own privacy policy.
- Its access: tokens that expire after an hour and renew for up to 30 days of use. Only a scrambled copy of each token is stored, which can’t be used to sign in, and expired tokens are deleted. Changes the app makes are marked as an AI assistant in a task’s history.
How each step works is in the connector docs.
How long it is kept
- Local data: until you sign out.
- Synced content: while your account exists.
- Calendar tokens: until you disconnect the account or revoke access at Google.
- Connected AI apps: their tokens until they expire or you disconnect the app; a record of which apps you connected, while your account exists.
- Feedback: while your account exists; the emailed copy until you ask for it to be deleted.
- Crash reports: 180 days, or until your account is deleted; the emailed copy until you ask for it to be deleted.
- Request counters that limit how often your account can make a request: each expires on its own, at the latest after 30 days.
- Server logs: a limited period, then discarded.
Product analytics
Diurnal records which features are used, so that the parts people rely on get better and the parts nobody opens can be removed. It is handled by Mixpanel, acting on instructions.
What that means precisely:
- Events name a feature, never its contents. A record says that a task was captured, a reminder fired, or the week board was opened. The words you type, your notes, your tags and your event titles are never part of it.
- It is tied to your account: its random identifier, your name and your email address go with each record, so a problem one person hits can be traced and answered.
- Deleting your account does not delete these records. Email support@diurnal.in from your account’s address and they are deleted too.
- This website counts page views and which buttons are pressed. A reader who has not signed in is not identified at all. The only cookie is the one that keeps you signed in after you sign in on this website.
- It can be switched off remotely without shipping a new version, which is how a problem gets stopped quickly rather than at the next release.
These come from the Mac app and this website. The Android app sends no product analytics.
There is no in-app setting to turn this off yet. That is a gap rather than a position, and it is being worked on.
How it is protected
Encrypted in transit. Calendar tokens encrypted at rest. Every request is scoped to its own account. On Android, your sign-in is encrypted with a key that never leaves the phone, and the app is never included in backups.
Your choices
- Skip the calendar. It is a separate step, and declining it costs nothing.
- Disconnect it in Calendars settings, or revoke it at Google.
- Disconnect an AI app in Settings on your Mac, under Account and Connected Apps. It loses access at its next request.
- Sign out to empty that device.
- Delete your account in the Android app, under Settings and Account, or by email from any device. How, what it removes and what it does not: Delete your account.
- Ask to see the data held for your account.
Contact
Questions or requests: email support@diurnal.in, naming the account. Diurnal is not directed at children. When this policy changes, the effective date above changes with it.