Privacy and your data

Kept is built on a simple rule: one choice never quietly authorizes another. Granting calendar access is not a Google connection. Allowing Cloud AI is not permission to share health measurements. Connecting an agent is not permission for it to delete your notes or tasks; the most it can do is archive a goal or a habit, or edit inside a note it may write to. This page says where each kind of information lives.

On your device

Each device keeps an account-scoped cache so Kept opens instantly and works offline: your tasks, notes, habits, goals, events, meals, and plan, plus a durable queue of changes waiting to sync, widget snapshots, and scheduled reminders.

Note recovery also keeps account-scoped drafts on this device: daily writing waiting for its saved day, rejected task descriptions and note titles, and earlier rich-text versions and original typed pages that need review. The recovery record itself is not a diagnostic breadcrumb or an extra model-provider submission. Choosing Cloud AI does not turn recovery storage into a separate permission to share it.

Ordinary sign-out detaches these drafts from the active app without deleting them. Another account cannot open them. Kept checks current sharing access before showing shared recovery again; confirmed access loss removes that recovery from view and starts local removal, while a temporary network failure does not discard it. Explicit discard waits for each local journal's durable clear. Confirmed account-deletion cleanup on iPhone and Mac removes retained drafts and their recovery metadata from that device. If local removal cannot be verified, Kept keeps the account fenced and retries cleanup when the app opens. An uncertain deletion request preserves retained editing drafts until its outcome is known. A content-free deletion recovery receipt stays until cleanup succeeds; content-free deletion-safety markers can remain to stop removed drafts from being recreated. See Your account.

Two things are read on the device and never copied into your account as raw data: Apple Calendar events you did not create in Kept, and Apple Health measurements. Health becomes daily summaries and habit check-ins; Apple events inform your free windows and the assistant's sense of when you are busy.

Widgets, controls, and Shortcuts read a minimized snapshot. They carry no keys of any kind.

In your account

Your tasks, notes, habits and check-ins, goals, events you create, connected Google calendars and their events, meals, workouts, focus sessions, plans, memories, and settings sync through Kept's servers, hosted on Supabase. Every row is scoped to your account and protected by row-level security, so even a bug in a query cannot reach another person's data.

A Do conversation is saved in your account too: your messages, Do's replies, and the working context Do needs to continue. Do uses your People list and the next 14 days of your Kept calendar as context for a request, only after you allow Cloud AI for Do, and sends the model only what that turn needs. In this version Apple Calendar events stay on your device and are not sent to Do. Ask Kept's thread is not stored this way. Conversations stay until you delete your account; there is no way to delete a single Do conversation in this release.

Each night Kept keeps a short record of the tasks you planned (what you finished, carried over or let go) and simple daily activity counts, so it can plan your next day better. Activity counts are kept for 90 days and plan outcomes for 400 days; older records are deleted automatically, even if you stop using Kept. They are removed if you turn off Cloud AI or switch to on-device only, and when you delete your account. Turning off Nightly reflection alone keeps this record, because Today uses it.

With a model provider

Nothing reaches OpenAI or Anthropic until you choose Allow Cloud AI. When you do, specific features send specific things, all through Kept's server as you. Cloud AI, explained lists every feature and what it sends. Turning Cloud AI off stops all of it. For Do, that means new requests stop reaching a model while your saved conversations stay in your account. Turning Cloud AI off also turns off Cloud AI for Do, and turning Cloud AI back on does not turn Do back on. To use Do again, choose Settings → Privacy → Cloud AI for Do → Turn on on iPhone.

Cloud AI and Cloud AI for Do are separate permissions on your account. Allowing Cloud AI in setup does not allow Do. When Cloud AI is off, Do's introduction asks for it first, so choosing Try Do and then Allow Cloud AI turns on both. Turning Do off leaves Cloud AI on. Withdrawal and on-device-only settings still stop Cloud AI.

Daily journal pages are notes and may be included in Cloud AI context, including older pages. Pausing a module does not delete its saved notes or exclude them from Cloud AI. While Body is paused, Ask Kept does not read or write Body records. Previously saved memories and briefings may still mention Body information. Turn Cloud AI off to stop new sends; use Memories and Forget to remove saved memories.

Do reads your calendar through Kept, but in this release it does not connect to a Google account or any other outside account of its own.

Raw capture text is used to improve Kept only under a separate opt-in, Help improve Capture, which starts off.

What Kept measures

Kept records product events to keep the app working and to know what is failing: a screen was opened, a capture was committed, a sync was refused with a code. Events carry names and codes, never your content. When you complete a task, Kept also records where you completed it (for example, Today or a widget), where the task came from (for example, you, a capture, or a Kept suggestion), whether it was overdue, and how many days it was open. When you view Today, Kept records how many of your tasks are open. Kept also records your notification permission setting. Background launches do not count as dashboard sessions or returns. Each product event and each capture record also stores the ten-digit app build from the request, so Kept can tell which build you were using. That build is read from the request itself, never from text you type. Kept does not put your content or secrets in a URL, and does not use advertising SDKs or session replay.

On the Kept website, a download link can include a short campaign name, such as the place the link was posted, so Kept can tell which outreach led to the visit. That name is a channel label, never your name, your email, or anything you wrote.

Bug reports

A bug report carries your description, the screen you were on, your build and device, and a small pack of non-content facts that help reproduce the state: which modules are on, which rollout switches are on, how many changes were waiting to sync, time since the device restarted, and free storage. An optional activity trail, off by default, adds event names and timestamps. Never note bodies, capture text, tokens, health details, or meal contents. Screenshots are attachments you can remove before sending. See Report a bug.

Connected agents

An agent you connect over MCP acts as you, within the permissions you approved, and every call is audited. Agents never see a password or a session token, never receive Health history without a separate permission, and have no delete tools. See Permissions and safety.

Goal words and Health

Without Cloud AI, typed goal words stay on the device. Goal Builder's cloud mapping routes are off for this release, so those words are not sent to a model for mapping. Health measurements are never copied into goal progress entries. A connected agent cannot yet read a Goal Builder plan as Markdown, record a progress entry, complete a milestone, or confirm a staged plan.

Notifications

Kept notifies you about your own briefings, reminders, goals, and agent work, and never about anyone else's. A notification never carries a note body or a task's private details beyond its title. Settings shows whether the system currently allows Kept to notify you.

Take it back

• Disconnect a Google account, Apple Health, or an agent from Settings at any time.
• Withdraw Cloud AI and every cloud path stops, on every device, including Do. Do keeps the conversations you already have until you delete your account. To stop only Do, use Settings → Privacy → Cloud AI for Do → Turn off. Turning Cloud AI back on does not turn Do back on; use Cloud AI for Do → Turn on on iPhone.
• Disconnect a Google calendar to stop Do reading its events. Apple Calendar events stay on your device and are not sent to Do in this version.
• Sign out removes the account from the active app. Retained writing can stay in account-scoped local recovery storage; see Your account.
• Delete your account requests permanent removal of your personal account data. Confirmed cleanup removes retained on-device drafts and their recovery metadata, with failed local cleanup retried when the app opens as described above. Records that belong to an organization you worked in may be retained under its policies, and older Apple-created accounts confirm once more with Apple first. See Your account.

The full legal statements are at kept.do/privacy and kept.do/terms.

Aggregate retention diagnostics distinguish people who close their own to-dos after signup, overdue tasks written during setup or by the coach, and captures or completions outside setup. Historical task dates stay unchanged, and the diagnostics show their observation window and missing capture-door coverage.

Shared-note privacy and access changes

Invited notes keep their complete saved content, including attached source text and import details. A reference to a task, picture or child page does not grant access to that separate item. Published links use a narrower reading view. Removing a membership or revoking a link stops later reads and comment writes through that grant. A separate active published link can still grant access. Copies already received cannot be recalled. See Shared note privacy.

When shared-note privacy protection is enabled, private source text, import details and private picture or page references are retained for the owner separately from the shared writing. The owner can read the retained details; membership alone cannot read them. Removing the note removes those retained details too. Before protection is enabled, invited collaboration can still carry saved source details. See Shared note privacy.