Menu · Privacy and telemetry

Privacy and telemetry

The local audit log

paws keeps one log per user at ~/.paws/audit.log. It's JSON lines with mode 0600, rotated to audit.log.1 at 50 MB. It records each time a rule fired and its verdict, each tool call that ran as a short key such as git commit or edit src/**, skill loads and turn ends. list and ui read it. It stays on your machine unless you log in.

What leaves the machine

Only after you log in, and only this:

  • each time a rule fired: its skill, verdict, and whether Claude already had the skill;
  • the commands Claude ran, with secrets redacted and cut to 500 characters;
  • MCP calls as server, tool and kind, which is send, create, update or delete;
  • tool actions as a short key, such as gh pr create, edit migrations/** or DELETE;
  • file paths relative to the repo root, leaving out any path outside the repo;
  • the names of your installed skills and the paws rules in scope.

Never your prompts, Claude's replies, file contents, tool output, absolute paths or session ids. unbound-paws sync --dry-run prints the exact request body.

Redaction

paws redacts commands before writing them to the log and again before upload. The value becomes *** and the name in front of it stays. It covers:

  • secret-named flags and assignments, such as --password=, --token, --api-key, *_SECRET=, *_TOKEN=, password= and api_key=;
  • the password in a connection string, as in postgres://user:***@host;
  • Authorization: and x-api-key: header values, and Bearer tokens anywhere;
  • provider tokens: sk- for OpenAI and Anthropic, sk_live_ and sk_test_ for Stripe, ghp_ and github_pat_ for GitHub, glpat- for GitLab, xox?- for Slack, and AKIA AWS key ids;
  • bare JWTs, and -p<password> for mysql and mariadb.

It's a heuristic. A secret in a shape not listed here is written as it is.