privacy
herder collects no data.
herder is open-source software you run on your own machines. There is no herder account and no herder server: the apps and the terminal UI talk only to the daemons and the vault you run. This page says what leaves your machines, and when.
Last updated 29 October 2026. It covers the herder daemon and CLI, the Mac and iPhone apps, and this website.
What stays with you
- Sessions, transcripts, attachments and settings are kept by the herder daemon on the machine that runs them, and by the vault you link them to, if you run one. herder never sends them to us: we have nowhere to receive them.
- Secrets live in your vault, and go only to the machines you grant them to.
- Provider logins (Claude, Codex, Cursor, OpenCode and the rest) stay in each vendor's own CLI, under its config directory on your machine. herder never reads, stores, copies or relays them; it only runs the unmodified CLI.
- Passkeys are created and kept by your device's keychain or your password manager. A daemon stores only each passkey's public key, and checks sign-ins against it on the machine itself.
The one third party: published artifacts
An agent can publish an artifact of its work, such as a screenshot, recording, page or log, to show it in its thread. Unless the session's project marks its artifacts private, the daemon then uploads the file to krowk.com for a public link that opens anywhere.
- When: only when an agent publishes an artifact, never in the background.
- What is sent: the file itself, its file name, its media type, its size and its SHA-256 checksum. Nothing else from the session goes with it, and no herder or provider account.
- Who can see it: anyone who has the link. Links are made without a krowk account and expire after a day.
- Private projects: with private artifacts on, nothing is uploaded. The artifact is kept only with the session, on your daemon, and shown in the apps from there.
krowk receives your machine's IP address with the upload, as any web server does.
Other connections herder makes
- Updates: the daemon fetches herder releases from GitHub, and asks the npm registry for the latest version of the vendor CLIs it runs. These requests carry no data of yours.
- Integrations you turn on: if you connect a Slack or Telegram bot, or add MCP servers, herder talks to those services on your behalf, under their terms.
- The coding agents themselves talk to their vendors (Anthropic, OpenAI, Cursor and others) under those vendors' own privacy policies, exactly as they do without herder.
Analytics and crash reports
The herder apps, daemon and CLI contain no analytics, tracking or crash-reporting code. If you share analytics with app developers in your Apple device's settings, Apple may pass us anonymous crash reports for the apps; that is Apple's setting, and off unless you turn it on.
This website is hosted on GitHub Pages. The homepage uses PostHog, hosted in the EU, to count visits; it stores an anonymous identifier in your browser. Your theme choice is kept in your browser's local storage.
Questions
Ask on GitHub issues, or see support. The code is open: every claim on this page can be checked in the repository.