We never see your prompts.

Wick is built local-first. The meter, the estimates, and the counting all run on your own machine. This page explains exactly what Wick touches, what it stores, and the short list of things that ever leave your device.

Last updated July 11, 2026

The short version

Wick has no backend. There are no Wick servers that receive your usage or your conversations.
The extension reads your Claude usage from claude.ai's own API, in your browser, using your existing login session.
Everything Wick calculates is stored locally in chrome.storage.local and never transmitted.
The only time content leaves your device is when you press a handoff button - and then it goes straight to the destination you chose, never through us.
Payments run through Polar.sh. We never see or store your card details.

Who we are

Wick is an independent tool that meters your Claude usage across two surfaces: a Chrome extension for claude.ai and a local MCP server for Claude Desktop and Claude Code. Wick is not affiliated with, endorsed by, or connected to Anthropic.

This policy covers both the extension and the MCP server. Where a section applies to only one of them, it says so.

What the extension reads

To show your live usage, the extension calls claude.ai's own internal API - the same endpoints the claude.ai web app uses. These requests run from your browser and carry your existing claude.ai session cookie. Wick never sees your password and never receives a copy of these responses; they are read, turned into numbers, and discarded.

Endpoints the extension calls

GET /api/organizations

Resolves which organization your account uses, so usage can be requested for the right workspace.

GET /api/organizations/{id}/usage

Returns your 5-hour and 7-day utilization percentages and their reset times. This is what fills the gauges.

GET /api/organizations/{id}/chat_conversations/{id}

Read only when you trigger a handoff, to grab the current conversation so it can be carried to another model. Read on demand, never in the background.

Wick requests utilization numbers and reset timestamps. It does not read, index, or store the text of your conversations at any point during normal metering.

What Wick stores, and where

Everything Wick keeps lives on your device: browser extension storage for the extension, and a single JSON file in your home directory for the MCP server. There is no cloud copy.

Stored value	Where	Why
wick:lastUsage	chrome.storage.local	Cache the last usage snapshot so the popup works even when claude.ai is closed.
wick:orgId	chrome.storage.local	Remember your resolved organization id to avoid re-fetching it.
wick:history:*	chrome.storage.local	A short rolling record of recent usage deltas, used to estimate messages left.
wick:billing	chrome.storage.local	Your Pro license key and validation status, so Pro features unlock.
update flags	chrome.storage.local	Whether a newer version is available, for the update banner.
~/.wick/history.json	your home directory	MCP server only: a local log of token usage it has metered.

You can wipe all of it at any time: remove the extension (or clear its storage from chrome://extensions) and delete the ~/.wick folder. Nothing persists anywhere else.

What we never collect

The contents of your conversations with Claude, ChatGPT, Gemini, or Grok.
Your claude.ai password or login credentials.
Analytics, telemetry, behavioral tracking, or advertising identifiers.
Your IP address, device fingerprint, or location - Wick has no server to log them.
Any data sold or shared with third parties for marketing.

Cross-model handoff

Handoff is the one feature that moves conversation text off claude.ai - because that is the whole point of it. It only ever runs when you click a handoff button. Here is exactly what happens:

01You press Hand off to ChatGPT, Gemini, or Grok.
02Wick reads your current claude.ai conversation from the endpoint above, in your browser.
03It formats that text and opens the destination in a new tab, passing the context directly to that service.
04Wick keeps no copy. The text goes from claude.ai to the destination you chose - never to a Wick server, because there isn't one.

Once text reaches ChatGPT, Gemini, or Grok, it is governed by that service's own privacy policy. Only hand off conversations you are comfortable sharing with the destination.

The MCP server

Wick MCP is a local server you run on your own machine. It meters Claude Desktop and Claude Code by reading usage that already exists on your computer. It listens only on localhost and never opens an outbound connection to us.

Claude Desktop

Usage you report through the MCP tools is tallied locally and written to ~/.wick/history.json. Nothing is sent anywhere.

Claude Code

The server reads Claude Code's own local log files under ~/.claude/projects to count tokens. It reads them in place and never copies or uploads them.

The server exposes a small dashboard on localhost so you can see your totals. That dashboard is served from your own machine and is not reachable from the internet.

The email waitlist

If you enter your email to be notified when Wick reaches the Chrome Web Store, that single field is stored in our waitlist database (hosted on Supabase) and used for exactly one purpose: to send you one email when the extension is live.

We collect your email address and nothing else.
No newsletters, no drip campaigns, no resale.
Ask us at any time to delete your address and we will remove it.

Payments and licensing

Wick Pro is sold through Polar.sh, our merchant of record. When you buy Pro, your payment and billing details are handled entirely by Polar and their payment processor - Wick never sees or stores your card number.

To unlock Pro, the extension sends only your license key to Polar's validation endpoint to confirm it is active. The validated key is stored locally under wick:billing so you do not have to re-enter it.

Third-party services

claude.ai (Anthropic) - the usage data source, accessed with your own session. Governed by Anthropic's privacy policy.
Polar.sh - processes Pro payments and validates license keys.
Supabase - stores waitlist email submissions.
ChatGPT, Gemini, Grok - only receive data when you explicitly hand off a conversation to them.

Your control over your data

Because Wick stores everything locally, you are always in control of it directly - no account, no request form, no waiting on us.

Delete extension data: remove Wick or clear its storage from chrome://extensions.
Delete MCP data: delete the ~/.wick folder.
Stop all metering: disable or uninstall the extension and stop the MCP server.
Audit exactly what Wick does: the full source is public.

Read the source on GitHub →

Changes and contact

If this policy changes, we will update the date at the top of this page and, for material changes, note it in the extension. Continuing to use Wick after an update means you accept the revised policy.

Questions about privacy, or a request to delete data we hold? Email hello@usewick.online.