Privacy

What it stores

• Your account. Your email address, and a display name taken from it. Sign-in is handled by Neon's managed authentication service; your password is never visible to this application.
• Everything you type into it. Captures, tasks, notes, outcomes, the people you owe things to, and the notes you leave when you close a day.
• How you asked it to model you. Timezone, working hours, buffers, energy windows, work-in-progress limit.
• Calendar data, only if you connect a calendar. In context mode it keeps a copy of your event instances for a rolling window — about a week back, two months forward — including their titles and times. In availability mode it keeps only the intervals in which you are busy, and no event title is ever received or stored. You choose the mode when you connect, and you can disconnect at any time.
• What you actually did. Focus sessions, completions and deferrals, plan repairs, and a log of the decisions you made in the app. This is what lets it learn how long your work really takes instead of trusting your estimates.
• Browser tab time — only if you install the extension and switch it on. It is off by default. When on, it records the domain of your active tab and how many seconds it held focus — whenever Chrome is the front application and you are not idle, not only while a focus timer is running. That is the change: a picture of where your time goes is worth nothing if it covers only the hours you were already measuring. Never a URL, never a page title, never page content, never anything from a private window. Switch it off and recording stops; the domains already recorded stay, because this history is append-only.
• Application time — only if you install the desktop app and switch it on there. It is off by default and per-machine. When on, it records which application held the foreground and for how long, and stops counting once you have been idle for two minutes. Never a window title, never anything you typed or read. If you also switch on Record site names too in its tray menu, a browser's address bar is read and reduced, on your machine, to the site's domain alone — never the page, a search you were typing, a title, a port or an internal name; anything that is not plainly a public site is not recorded at all. Where the extension is recording the same browser, its report of the tab is used and the desktop app's reading is set aside, so nothing is counted twice.
• AI usage records. Which model ran, roughly how many tokens, and what it cost — so the bill is never invisible.
• The waitlist, if you joined it. The address you typed on the front door and when — nothing else. It leaves the list when that address first signs in, when the account that address belongs to is deleted, and sooner if you write and ask.

There are no advertising trackers, no analytics scripts, and no third-party cookies. The only cookie is the one that keeps you signed in.

Who else processes it

• Neon — hosts the database your rows live in, and runs the sign-in service.
• Vercel — hosts and serves the application.
• Google — only if you connect a Google Calendar.
• Anthropic — receives the specific text a feature needs and nothing more. The one line you captured, with the names of your active outcomes and a few of your own task titles as examples of how you file work. A meeting transcript you paste to be read for commitments — read once and not stored, beyond the sentence each candidate is quoted from. The note you write when closing the day, which is read for commitments as it is saved and kept on the day's record as your own words. The facts behind a morning briefing: the day's sittings and meetings (their titles too, when your calendar is connected in context mode), yesterday's numbers and the note you closed with, and the thing you chose to protect. And the weekly numbers and your closing notes behind a reflection, with your outcomes' names. Under Anthropic's API terms that content is not used to train models. Your browsing domains are never sent to any model at all — that exclusion is written into the code, not just onto this page.

Nothing is sold, and nothing is shared with anyone else for any reason other than a legal obligation.

Google user data, specifically

Intenday asks to read your calendars so it can work out the capacity you actually have, and to manage calendars it creates so it can put its own plan somewhere you can see it. It uses that data for one purpose: computing and showing your plan inside the app. In context mode, that includes handing the day's meeting titles to the model that writes the morning briefing, as listed above; in availability mode no title is read at all.

It never modifies or deletes your own events. The only calendar it writes to is the “Intenday” calendar it creates in your account — a limit enforced by the permission it asks for, not merely by its own good behaviour. Disconnecting your Google account deletes the stored calendar copy and the access tokens, which are encrypted at rest for as long as they exist.

Intenday's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is never used for advertising, never sold, and never used to train, fine-tune, or improve any AI model.

Keeping it, and getting rid of it

Your data is kept while your account exists, because the whole point of the app is that last month informs this week. Disconnecting Google removes the calendar copy immediately.

Settings has a delete button, and it is not a request queue: pressing it erases everything listed above straight away — every task, plan, calendar copy, focus session and learned statistic, and the profile itself. It also takes back what this app put INTO your Google account — the events it wrote into the calendar it created, and that calendar — before the connection is revoked, in that order, because a revoked grant can never be reached again. One thing it cannot yet reach is the sign-in record — the address and password hash held by the authentication service — which is removed by hand within 30 days. That gap is real and this page will not paper over it.

You can also have it all done for you, or ask for a copy of what is stored about you, by writing to kevin@simplifywithai.io from the address you signed up with.

Security

Traffic is encrypted in transit. Third-party access tokens are sealed with AES-256-GCM and bound to your account, so a stolen ciphertext cannot be replayed against another. Every database statement the server issues about an account names the account it is for, and an automated check fails the build if one ever forgets to; the one table that belongs to no account — the waitlist — is added to by the front door's form alone and read by nobody signed in.

Children, and changes

Intenday is a tool for working adults and is not directed at children under 16.

If this policy changes, the date at the top changes with it in the same release, and you will be told by email before a material change takes effect. Questions — or anything on this page that turns out not to match what the software does — go to kevin@simplifywithai.io.

See also the terms of use.