Skip to content
Taskbook Sign in Get started

Privacy

Last updated 2 November 2026

Taskbook is a task manager that runs in your browser. You sign in so your tasks can follow you between devices, and every connection to another service beyond that is optional and switched on by you.

The short version. Your tasks live in your browser, with a copy in Taskbook’s database so your devices agree. Nothing is sold, shared or used for advertising, and there is no tracking or analytics of any kind.

What is stored, and where

WhatWhere it lives
Tasks, projects, labels, settings, Assist conversations and Assist’s memoryYour browser’s local storage, on your device
Your email addressSupabase (Taskbook’s database host), to identify your account
A copy of all of thatSupabase, readable only by your account
Google Calendar and Gmail access, if you connect themSupabase, readable only by Taskbook’s server
Tasks waiting in Incoming, and the ids of emails already readWith your tasks, in your browser and your account’s copy
API keys and links you paste in (Claude, Gemini, Todoist, Canvas)Your browser only. They are never uploaded, even when you’re signed in

You can sign in with Google, or with a one-time link sent to your email address. Either way Taskbook never sees or stores a password. Signing in with Google gives Taskbook the email address on that account and nothing else about it. Ticking “Also connect my Google Calendar” on the sign-in screen also grants the calendar permissions described below, which you can revoke at any time in your Google account or by disconnecting in Settings.

Google Calendar

If you connect Google Calendar, Taskbook asks for the narrowest permissions that do the job:

What goes to Google is the title of each task you schedule, its project name, the times of each block, and an internal id so Taskbook can recognise the event when you move it there. Nothing else is sent.

Taskbook’s server keeps Google’s permission for your account (a refresh token), so the calendar keeps working without asking you again. Only the server can read it. Disconnecting in Settings revokes the permission with Google and deletes it. The “Taskbook” calendar and its events stay in your Google Calendar until you delete them.

Taskbook’s use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Google Calendar and Gmail data is never used for advertising, never sold, never used to train any AI model, and is never read by a human except where you ask for support or the law requires it.

Gmail

If you connect Gmail, Taskbook asks Google for one permission, to read your email, and uses it for one thing: finding the things you need to do. Every few hours while Taskbook is open, or when you press Check now, it reads the messages from the last three days in your primary inbox that it hasn’t read before, at most fifteen at a time: each one’s sender, subject, date and the first 1,500 characters of its text. Those go to the assistant’s model (see below) with an instruction to pick out real tasks and to ignore anything an email asks it to do.

Taskbook keeps only what you see in Incoming: each suggested task, with the sender’s name, the subject and a link back to the email, plus the ids of the emails it has read so it never reads one twice. It does not keep the text of any email. It never sends, deletes, labels or changes your email, and nothing it finds becomes a task until you accept it.

Taskbook’s server keeps Google’s permission for Gmail separately from Calendar’s, so either can be disconnected alone. Disconnecting in Settings → Email deletes it. To remove Taskbook from your Google account entirely, use Google’s third-party connections page in your account settings. If you have added your own Gemini key on Google’s free tier, what the assistant reads can be used by Google to improve its products; Taskbook’s own model and paid keys don’t allow that.

Canvas

If you connect Canvas, Taskbook reads your assignments: their titles, descriptions, course names, due dates and links, and, if you use an access token, whether you have handed them in. Canvas doesn’t let a website on another address read it from your browser, so those requests pass through Taskbook’s server, which can only make read-only requests, forwards them and keeps nothing. Your feed link or access token stays in your browser. New assignments wait in Incoming until you accept them, and an accepted one keeps its description with your tasks; Taskbook never writes anything to Canvas.

Todoist

If you connect Todoist with a personal API token, tasks in the projects you tick are sent to your Todoist account, and changes you make there come back. The token stays in your browser.

The assistant

Much of the assistant never leaves your device: the plan review’s arithmetic, the fallacy detector and the whole scheduler are local code. The parts that need judgement (breaking work down, extra findings in a plan review, turning notes into tasks) send the task or project concerned, with its title, description, dates and estimates, to a language model. With Automatic review on (Settings → Assistant), Taskbook also checks projects that have a deadline once each session, which sends those projects too.

That goes through Taskbook’s own server to Google’s Gemini API on Taskbook’s account, with a daily allowance per account. Taskbook’s server keeps a count of how many calls you have made that day, and nothing else: your prompts are not stored or logged. You can instead choose On-device in Settings, so nothing is sent anywhere, or add your own Anthropic or Google key, in which case the text goes directly from your browser to that provider under your account and their terms.

When you chat with the assistant, each message goes with a compact copy of your open tasks (titles, projects, dates and priorities) so it can answer questions about them. Files you attach (PDFs, images, text) are sent with that one message for the model to read, and Taskbook keeps only their names, in the conversation. Changes the assistant proposes are checked and applied by the app on your device. Anything from an attached file, any deletion, and any batch of more than ten changes waits for you to approve it.

Assist’s memory. Assist keeps short notes about how you like to work: things you tell it to remember, habits it notices, your answers to its occasional questions, and what you said Taskbook is for and when you work when you first set it up. It also keeps how long finished tasks really took, when you answer its check-in. Every request to the model carries these notes and that timing summary, so its answers follow them. When you chat, each message also carries the changes you made to tasks Assist created and your recent requests from other conversations, which is what it learns habits from. It never learns from a turn with an attached file. You can see, edit and delete every note in Settings → Assistant, turn learning or the check-ins off there, or forget everything at once.

Free-tier Gemini usage can be used by Google to improve its products; paid Anthropic and Google API usage is not used to train models. Choose accordingly for sensitive work, or leave the assistant on-device.

Voice input

If you talk to Assist or speak a task into quick add, your browser’s own speech recognition turns the speech into text. Your browser sends the audio to its maker’s speech service for that (Google in Chrome, Microsoft in Edge, Apple in Safari), under that company’s terms. Taskbook never receives or stores the audio, only the text, which is then handled like anything you type. Nothing is recorded until you press the microphone, and listening stops when you press stop or Done, or close the panel.

Deleting your data

Other things worth saying plainly

Contact

Questions, or a deletion request: joshjamesburke@gmail.com