Privacy
cowpath keeps your playbooks, not your chats. This page says what we store, where it lives and how long we keep it.
Updated 17 October 2026
The short version
- cowpath never receives your chats or transcripts. Your own agent reads them, on your machine and your plan.
- Without an account, your processes, runs and playbooks stay on your computer.
- With an account, your workspace is stored in Frankfurt, Germany, and only its members can see it.
- We count how cowpath is used, never what you work on. One setting turns that off.
- We don't sell your data, show ads or train AI on your work.
Without an account
Everything lives in ~/.cowpath on your computer: your processes, runs, playbook versions and a log of what cowpath did. When a session ends, the agent CLI that ran it (claude -p or codex exec) reads the transcript on your machine and keeps only the run: what you asked, your corrections and the final version.
Two things leave your computer:
- Once a day, the CLI asks npm for its latest version. The request carries nothing about you.
- Usage counts, described below.
With an account
Signing in, with cowpath login or in the browser, stores your work in your workspace so your team can use it. This is what we keep, and for how long.
| What | Why | Kept until |
|---|---|---|
| Your email and name | WhyTo sign you in and show who wrote what | Kept untilYour account is deleted |
| Workspaces, members and invites | WhyTo share your processes with your team | Kept untilYou delete the workspace |
| Processes, runs and playbook versions | WhyThey are the product: each run and version records who, which agent, client and model | Kept untilYou delete them or the workspace |
| Sign-in tokens for the CLI and connectors | WhyTo keep them signed in | Kept untilYou sign out or revoke them |
| Share links | WhyTo let someone copy a process | Kept untilYou revoke the link |
Only members of a workspace can read it. Deleting a workspace deletes everything in it. Through the connector, your agent sends cowpath only what the tools ask for; the full chat is never stored.
Usage data
The CLI, the app and this site send usage counts so we can see how cowpath is used: which commands and tools run, how many runs finish, how often a playbook is rewritten. Each event carries a random install id. Signed in, it carries your account id, and your account carries your email.
Never sent: your prompts, transcripts, tool arguments, playbook text, run content, process names or file paths. The docs list every field.
COWPATH_TELEMETRY=0 or DO_NOT_TRACK=1 turns it off in the CLI. cowpath status shows whether it is on. This site counts visits without cookies.
Services we use
cowpath runs on a few services. Each one only sees what it needs for its job.
| Service | What for | Where |
|---|---|---|
| Supabase | What forDatabase, sign-in and sign-in emails | WhereFrankfurt, Germany |
| Vercel | What forHosting this site, the app and the connector | WhereFrankfurt, Germany; static pages are cached worldwide |
| PostHog | What forUsage counts | WhereFrankfurt, Germany |
| npm | What forThe CLI's daily version check | WhereUnited States |
Your agent is yours. What you send Claude, ChatGPT or Codex goes to Anthropic or OpenAI under your own account and their terms, as it did before cowpath.
Your data, your call
- Take it with you.
cowpath exportwrites every playbook as Markdown; the app exports a workspace too. - Delete it. Delete a workspace in its settings, and everything in it goes.
cowpath uninstall --purgeremoves everything on your computer. - Stop the counting. Set
COWPATH_TELEMETRY=0.
Under the GDPR you may also ask for a copy of your data, have it corrected or deleted, object to how it is used, and complain to a data protection authority.
Changes
When this page changes, the date at the top changes with it. The terms cover the rest.