what your pet knows about you

almost nothing. each time Claude Code does something, the hook sends exactly this, and the server refuses anything else:

{ "v": 1, "type": "stop", "at": 1791234567890, "session": "3f9a1c0e7b2d" }

type

what happened: a prompt, a finished task, a request for your input, a session starting or ending.

at

when it happened.

session

a salted hash, so two Claude windows can be told apart. The salt never leaves your machine, so it can't be traced back.

never sent

your prompts, Claude's replies, code, file paths, folder or repo names, tool names, or anything Claude reads or writes.

if you share usage

off unless you run npx burrow-pets usage on. then each stop also carries two numbers, "usage": { "tokens": 1200, "cost": 0.42 }: the tokens Claude Code recorded since the last one, summed on your machine from its transcript, and the increase in Claude Code's own cost estimate. nothing else from the transcript leaves your machine.

what the server works out

everything in the garden comes from those fields: your pet's state, how long your agent waited on you today, the koban it earns (finished runs and quick answers), and your stats (turns, tasks, active time, reply times, by hour, for 7 days). anyone with your garden's link can see them. nothing else is collected to make that work.

this website

counts page views with Vercel Web Analytics, which uses no cookies and does not identify visitors. it never sees your pet or your agent.

see it yourself

run npx burrow-pets privacy to print the same list, or npx burrow-pets uninstall to remove the hooks and your local pet data.