Innings sign in

What is stored, and how to delete it

Last updated 25 September 2026. This is a small tool run by one person and shared with a handful of testers. It is written plainly because vagueness here would be the problem.

What is collected

Only what the tool exists to show you:

  • Your prompts and the agent's replies, verbatim, from sessions on machines where you installed the client.
  • Entries your agent writes — findings, decisions, changes, checks, and where things stand.
  • A hash of your repository's git remote, so tasks group by project. The repository name is sent only if you leave the label on, and you can clear it.
  • The name of the tool that wrote each row, such as claude-code, and the time it was written.
  • Your email address, from Google sign-in, to identify the account.

What is never collected

Your source code, file contents, tool results and command output are not sent. Anything matching a known secret pattern — tokens, keys, PEM blocks — is stripped on your machine before upload, and only the name of what was stripped travels with the turn, so you can see the scrubber working.

Where it lives

On servers in AWS in Mumbai (ap-south-1), in an encrypted database that is not reachable from the public internet. Backups are kept for seven days. It is not sold, not shared with anyone, and not used to train anything.

Deleting it

From Your data in the dashboard, either of these, immediately and without asking anyone:

  • Delete raw turns — removes every stored prompt and response, keeping the reasoning your agent wrote.
  • Delete everything — removes every task, entry, pinned decision and raw turn.

Both leave your account and your API tokens in place, so signing in and the CLI keep working — the log simply starts again from empty. To remove the account itself, revoke your tokens on that page and ask, and it will be deleted by hand.

Deletions take effect at once. Database backups age out within seven days.