Privacy Policy

Last updated: October 16, 2026

The CLI is local-first

The free LoopGuard CLI reads usage logs that Claude Code, Codex and Cursor already keep on your machine, and stores its own index, settings and trip log in ~/.loopguard. It sends nothing anywhere unless you run loopguard login and loopguard sync.

What loopguard sync uploads

Only aggregate numbers. You can see the exact payload with loopguard sync --dry-run.

• A hashed machine identifier (derived from the hostname, not reversible to it).
• Per agent, per hashed session ID, per day and per model name: input, output and cache token counts, estimated cost, event count, and whether figures were estimated.
• Trip events: time, agent, hashed session ID, trip type (session cap, daily cap, loop, cost spiral), whether the session was halted, the tool name (e.g. “Bash”), and the session and daily cost at that moment.

Never uploaded: prompts, model responses, source code, file paths or project names, tool inputs or command lines, raw session IDs, or API keys for AI providers. The server also discards any field outside this list.

Account data

Your email address; hashed sign-in tokens, session tokens and API keys; plan and Stripe customer/subscription IDs; alert settings (including Slack/Discord webhook URLs you add); and a remote-pause time if you set one.

Processors

• Railway — hosting and database.
• Stripe — payments. We never see or store your card number.
• Resend — sending sign-in and alert emails.
• Slack / Discord — only if you add a webhook, alerts are posted there.

We don't sell your data, run ads, or use your data to train models. No third-party analytics or tracking cookies; the only cookie is the sign-in session cookie.

Retention and deletion

Data is kept while your account is active. To delete your account and all synced data, email us; revoking an API key stops further uploads immediately.

Contact

Questions or deletion requests: reply to any LoopGuard email.