Security and privacy
Kestrel keeps numbers and names, never the text of your work. This page says what is sent to the board, where it is stored, who can see it, and how to remove it.
On your computer
Kestrel reads the logs that Claude Code, Codex and Cowork keep on your computer. From them it takes counts, sizes and names: the tokens of each call, the model, the names of tools, the folder and the git branch. It never keeps the text of a prompt, an answer or a tool result. What it keeps is in the folder ~/.kestrel.
On its own, Kestrel sends nothing anywhere. Two things use the network, and only when you start them: linking the computer to the board, and a cloud check (kestrel cloud-check), which reads an AWS account, a Vercel project or a GitHub repository with the sign-in you already have.
What is sent to the board
When you link a computer with kestrel board login, Kestrel sends:
- Each model call: the time, the session, the agent (Claude Code, Codex or Cowork), the model and effort level, the token counts, and the cost at list prices.
- Where the work happened: the folder, the repository, the git branch and the ticket in the branch name. The folder starts with
~for your home folder, so your user name on the computer is not sent. - What entered the context: the names of the tools an agent used, each with a short code made from its input, and the size of what entered in characters. Neither holds any text of the session.
- Commits made during a session: the repository, the commit id and the time. The board uses them to link a session to a pull request.
- Security findings: the rule, the severity, the title, where (such as a file and line), the controls, and when it was first and last seen.
- The plan's limits of each account, the accounts' short keys and labels, Kestrel's settings, and its proposals.
- The computer: its name, its operating system and the version of Kestrel.
- Names of tasks and of what each subagent works on, while Kestrel's setting for names is on. It is on unless you turn it off with
kestrel hud names off; then they are no longer sent. These names are text written in the session, so keep patient data and other private data out of task names.
What is never sent
- The text of prompts, answers, tool results and files.
- What a security check matched: no key, no number, no command, no text of a session.
- Your email address. The board never asks GitHub for it.
- The path of your home folder: folders are sent starting with
~.
Where it is stored
The board's data is stored in the United States. The board runs on Vercel, and its data is kept in a Turso database on AWS in the region us-east-1.
- The token that links a computer is shown to that computer once. The board keeps only a hash of it (SHA-256), so a copy of the database cannot be used to send data as that computer.
- The sign-in cookie holds a random id. The board keeps only a hash of it.
- The board uses your GitHub sign-in once, to learn who you are and which teams you belong to. It does not keep the GitHub token.
Who can see it
The members of your team. A team is a GitHub organization where the board's GitHub App is installed, or your own GitHub account if you work alone. A member is a person who signs in with GitHub and is an active member of that organization. Outside collaborators and people with an invitation not yet accepted are not members.
The board asks GitHub again at least once an hour whether each signed-in person is still a member, and at once when GitHub reports that someone left the organization. A computer whose owner left the team can no longer send data to it.
Widal staff who run the board can reach the data only when they must, to run or fix the board.
- Every member sees the team's numbers, also the numbers of each person. The board lists people in alphabetical order and compares the team with its own past, not people with each other.
- The admins of the GitHub organization are the admins of the team.
- People outside the team cannot see the team's data.
What the board asks GitHub for
The board's GitHub App has read permissions only: metadata, contents, pull requests, checks and organization members. It cannot change anything in your repositories. The board keeps the pull requests' titles, authors, branch names, dates, sizes, reviews, check results and commit ids. It does not keep your code. When you sign in, it asks for your id, login and picture, never your email.
Remove a computer, or delete data
- Remove a computer: run
kestrel board logouton it, or press Revoke next to it on your account page. Its token stops working at once. An admin can remove any computer of the team on the board's Machines page. - Delete the team's data: an admin of the team deletes it on the board's Settings page. If the team asks us at hello@widal.com, Widal deletes the team's data within 30 days.
- Delete your account: on your account page. Your profile, your sign-ins and your computers are deleted. The data your computers sent stays with the team, no longer linked to your account, until the team deletes it.
What Kestrel's checks are
Kestrel checks technical controls and flags risks. It does not make a company compliant or certify it. A finding names the controls it touches in the frameworks you turn on, such as HIPAA, SOC 2, HITRUST, 21 CFR Part 11, PCI DSS and the OWASP Top 10 for Agentic Applications. Use the findings as input for your own review.
How the board is protected
- Every page loads only the board's own files, and people's profile pictures from GitHub (avatars.githubusercontent.com). No outside scripts, fonts or styles, and no analytics or tracking cookies.
- Every form that changes something carries a token that only your own session knows.
- Cookies are sent over HTTPS only and cannot be read by scripts.
- Every query for team data names the team of the person or computer that asks.
To report a security problem, write to hello@widal.com.