What Sprag sends: open source, Pro and Enterprise
Plan by plan, what Sprag uploads to its server: nothing on the free CLI, daily numeric totals on Pro, and opt-in masked prompt capture on Enterprise.
This page covers only the data Sprag uploads to its server, plan by plan. Download-only lookups such as the new-version check upload nothing, so they are left out.
| Plan | Uploaded to the server |
|---|---|
| Open source (free CLI) | nothing |
| Pro | daily numeric totals from computers that joined a team |
| Enterprise | the Pro totals, plus prompts people typed, only for teams with capture on |
Open source
Nothing is uploaded and no account is needed. All analysis runs on the session logs already on your computer. Only when you run sprag feedback yourself are the message you typed, the version and the OS passed on.
Pro
Only computers that ran sprag team join or got SPRAG_TEAM_TOKEN from their organization upload. Before joining, nothing goes up, even under a contract.
Uploaded (one row per day)
- spend, savings and delegation cost (USD), and delegation counts
- spend and share per model family (names such as
opusandsonnet) - OS name and version, Sprag version, display name (a random ID such as
member-3f9a2c71by default) - delegation rule summary: numbers only, such as counts, failure rate and savings per category
Not uploaded: prompts, conversations, code, file paths, project names, rule text, API keys, hostnames
Organization owners and admins see only each member's daily totals.
Enterprise
The same totals as Pro. Only when an organization owner or admin turns prompt capture on for a team, these are added:
- the text of prompts typed in main sessions (up to 20,000 characters), the time, and the project folder name
- API keys, tokens, passwords, emails, phone numbers, Korean resident registration numbers and card numbers are masked as
[redacted]on your computer before upload - nothing written before capture was turned on is uploaded
- assistant replies, tool output and file contents are not uploaded
Prompts can be read only by that organization's owners and admins, and by Sprag operators handling support.
Check and turn off
sprag team status --show-payload: prints exactly what the next upload containsSPRAG_NO_TEAM_SYNC=1: stops every uploadsprag team leave: leaves the team
Data is stored over HTTPS in Supabase's Seoul region and deleted within 30 days after an organization closes. Questions go to support@sprag.io. Item-level detail is in the team guide.
More docs
- Codex: hooks, ratchet rules, model delegation, and a companion panel
- Claude Code statusline: cache hit rate, cache TTL countdown, 5-hour and 7-day rate limits
- Why realtime model routing can cost more in Claude Code
- Delegate repeat Claude Code work to Haiku and Sonnet subagents with route-scan
- Claude Code harness: ratchet rules, evidence-gated completion, Plan-Execute-Verify
- Convert pptx, xlsx, pdf, docx and fig to Markdown before Claude Code reads them
- Claude Code statusline behind LiteLLM and other gateways
- Install Sprag for Claude Code and Codex
- Sprag command reference
- Korean writing style gate for Claude Code output
- How to reduce Claude Code token usage
- Claude Code 5-hour and weekly usage limits, explained
- How to reduce Codex CLI token usage
- Sprag vs ccusage, claude-usage, and statusline tools