Privacy

What we collect, and why.

KT Console helps a company hand over an employee's work when they leave or change roles. This page describes what the service actually collects today, where it is kept, who processes it and how to remove it. Last updated 3 November 2026.

Your account

  • Your name, work email address and your company's name and email domain.
  • Your role in KT Console (Owner or Admin).
  • Sign-in sessions, kept as a hashed token in a secure cookie; they expire after 30 days.
  • An audit log of actions in your company's account: who signed in, started a capture, shared a document, changed a setting or moved files, and when.
  • What you tell us during setup, such as company size and your job role.

A personal workspace ("For myself")

  • Your name and email address (a personal address such as Gmail is fine), and what you tell us during setup.
  • The KT notes you write. They are private to you: nobody else can open them in KT Console. They are stored in the database described below and deleted with your account.
  • A personal workspace has no team features and reads nothing from your accounts. Connecting your own accounts is not available yet; until it is, My week shows sample data.

A capture, started by an Owner or Admin

Nothing about an employee is read until an Owner or Admin of their company starts a capture for that person. A capture covers a set window (90 days by default) and reads:

  • Gmail (read only): threads the person wrote in during the window, with subject, participants, dates and short excerpts of their last messages. Calendar invitations and automated mail are skipped.
  • Google Drive: the names, types, links, dates and sharing settings of documents they own that changed in the window. File contents are not copied.
  • Slack, if connected: their messages that the connecting Owner can see (short excerpts with channel and link) and the channels they created. Slack does not let us read private messages the connecting Owner is not part of.
  • Basecamp, if connected: to-dos assigned to them, to-dos they completed and their comments in the window.

Because a handover has to say what work is in progress, a capture includes short excerpts of message text, not only counts. Activity views (below) are different: they use counts only.

Activity views, if an Owner turns them on

Activity views are off until an Owner of your company turns them on. While they are on, KT Console counts, once a day, for each person in your company's directory (or Slack workspace):

  • How many emails they sent each day (Gmail). Only the date of each sent message is read.
  • How many documents they own changed each day (Google Drive). Only the date of the last change is read.
  • How many Slack messages they sent each day, as far as the connecting Owner's account can see. Only each message's time is read.
  • How many Basecamp to-dos they completed each day, as far as the connecting Owner's account can see. Only who completed each to-do, and when, is read.

No message text, subjects, to-do titles, file names or recipients are stored. People are stored as a one-way code made from their address, not the address itself. Team charts only show numbers made from three or more people, and nobody is ranked. Each person can see their own counts, and only they can: Owners and Admins cannot open someone else's. Counts are deleted after your retention period, and all of them are deleted when an Owner turns activity views off.

How the handover is written

The captured data is sent to Anthropic's API, which writes the six sections of the handover and a list of open tasks. Under Anthropic's commercial terms, data sent through the API is not used to train their models. Our instructions tell the model to treat the captured data as data, to leave out passwords and other credentials, and to leave out personal, medical, HR and pay matters. The finished handover is saved as a Google Doc in your company's Google Drive when Google is connected, and is also shown in KT Console.

Where data is stored

  • The database is PostgreSQL hosted by Neon on Amazon Web Services in the United States (us-east-2, Ohio).
  • The application runs on Vercel, in its US East region (Washington, D.C.).
  • Connection keys for Slack and Basecamp are encrypted (AES-256-GCM) with a key that only the server holds.
  • Handover documents created in Google Docs live in your company's own Google Drive, under your control.

Who processes it

  • Vercel (hosting), Neon (database) and Anthropic (writing handovers).
  • Google, Slack and Basecamp, only to read what a capture needs from accounts your company connected.
  • We do not sell personal data or share it with advertisers.

How long it is kept

  • Captured data and handover drafts: deleted after your company's retention period, 90 days by default. An Owner can set anything from 7 days to 2 years.
  • Activity counts: deleted after the same retention period, or all at once when an Owner turns activity views off.
  • Sign-in codes: deleted within a day. Expired sessions: deleted automatically.
  • The audit log and your account: kept while your company uses KT Console.

Your choices: delete and export

  • Owners can disconnect Google, Slack or Basecamp at any time in Settings, and shorten the retention period.
  • Handover documents in Google Docs can be exported, moved or deleted in Google Drive like any other file.
  • To export your company's data or delete your account and everything stored for it, email hello@ktcapture.com. We do this by hand for now and confirm by email when it is done.
  • Employees who want to know what was captured about them can ask their company, or contact us at the same address.

Contact

Questions about privacy: hello@ktcapture.com.