Security & data practices

Your code stays on your machine.

WOZCODE is a Claude Code plugin that runs in‑process on your computer. We are not in the API path between you and Anthropic. The four guarantees below are the whole story.

See the data flow Privacy policy
✓
No prompt data leaves your machine
Your Claude Code conversations stay between Claude Code and Anthropic. WOZCODE doesn't see them.
✓
No code leaves your machine
Source files, file contents, search results, edits, tool I/O — all stay local. We never receive any of it.
✓
We're not in the API loop with Anthropic
Claude Code's connection to Anthropic is direct. WOZCODE wraps the local tools Claude Code uses — not the API path.
✓
We only collect tool usage stats and auth checks
Tool call counts, token counts, and timings — tied to your account so we can show your savings dashboard — plus subscription verification on login. That's it.
Architecture

A plugin, not a proxy.

Your machine talks to Anthropic the same way it always has. WOZCODE wraps the tools Claude Code uses on your machine — not the API connection.

Your machine
Claude Code
Talks to Anthropic over its own HTTPS connection. Holds your API key locally.
in‑process
WOZCODE plugin
Replaces Search / Edit / Sql tools — a sub‑component of Claude Code, not a network hop.
Direct HTTPS
Off your machine
Anthropic API
Same endpoint, same auth, same TLS connection vanilla Claude Code uses.

WOZCODE never proxies your prompts or the model's responses — it just swaps the local tool implementations Claude Code uses on your machine. The HTTPS connection between Claude Code and Anthropic is the same one vanilla Claude Code uses.

Data we collect

Two short lists.

Exactly what reaches our servers — and exactly what doesn't.

What we send to our servers
Usage stats & auth, that's it.
  • Aggregated session stats — tool call counts, token counts (pulled from Anthropic's usage fields on your client), estimated cost, turn counts, elapsed time. Powers the /woz-savings dashboard.
  • Auth checks — verifying your subscription status when you log in.
  • Account info — name, email, subscription tier (when you sign up).
  • Operational metadata — plugin version, OS family, IP address (used for fraud / abuse detection and standard request logging).
What we never send
Your code, prompts, and keys.
  • Source code or file contents — not on read, not on edit, not anywhere.
  • File paths or directory structure from your repo.
  • Tool inputs & outputs — search queries, grep output, file diffs.
  • Your prompts or the model's responses.
  • Your Anthropic API key — it lives in Claude Code's local credential store; we never touch it.
Subprocessors

The vendors in our pipeline.

A short, honest list of every third party we hand any data to, and what they get.

Vendor Purpose What they receive
Anthropic Claude API — the model that runs your session. Whatever Claude Code already sends them. WOZCODE does not intermediate this connection — same direct HTTPS as vanilla.
Supabase Authenticated database for accounts, subscription state, and aggregated session stats. Account email, encrypted password (handled by Supabase Auth), and the aggregated usage stats listed above.
Stripe Subscription billing. Payment details (entered directly into Stripe — we never see card numbers), email, and subscription state.
Vercel Hosts the wozcode.com marketing site and edge analytics. Standard web request metadata for the marketing site only — never plugin traffic.
Safeguards

How we handle the data we do touch.

Encryption in transit
Every connection between your machine, our server, and our subprocessors is TLS 1.2+ over HTTPS. Telemetry uploads run over Supabase's authenticated REST endpoint.
Encryption at rest
Aggregated session stats and account data are stored on Supabase, which encrypts data at rest by default (AES‑256). Stripe holds payment data under PCI DSS.
Your Anthropic credentials
We never see your Anthropic API key or session token. Claude Code stores those locally in its own credential store (or your OS keychain). They don't leave your machine, and there is no flow where we'd request them.
Subscription & billing path
Anthropic billing is unchanged — you pay them directly via your Pro/Max plan or API key. WOZCODE's own subscription is handled separately by Stripe. No middleman for AI calls. Using WOZCODE doesn't violate Anthropic's terms because nothing about your existing relationship with Anthropic changes.
Account & data deletion
Self‑serve — delete your account anytime from the woz‑app. Your data is removed within the windows required by applicable law (GDPR, CCPA).
Compliance posture
SOC 2 is actively in progress. While certification work is underway, our architecture is designed so the bar matters less than usual — the only data leaving your machine is account info and tool‑usage telemetry, not source code or prompts. If you're working through enterprise security review, reach out and we'll happily walk through specifics.
Contact

Questions, audits, or incident reports.

For security questions, vulnerability disclosure, or enterprise security review:

founders@withwoz.com

For full legal terms, see our privacy policy and terms of service.

Run it on your own machine.

The fastest way to verify everything on this page is to install WOZCODE and watch your own outbound traffic.

Install WOZCODE How it works