Security and data
Meter sits between Claude Code and Anthropic, so every request and response passes through it. Here is what it does with them — and what it doesn’t.
What Meter sees
- To account for a call, Meter reads a bounded part of each response — up to 64 KB from the start and the end — for the token counts and tool calls.
- Accounting runs off the request path: the agent’s response never waits on it.
- The request body is parsed in full only when the team’s policy has repository or path rules. Budget-only policies never read it.
What Meter keeps
- For each call: who (developer, team and the group the developer was in), when, model and provider, tokens and cost, repository, status and duration, security flags.
- File paths and shell commands the agent passed to its tools: up to 32 per call, 300 characters each. Security flags work from these.
- Secrets in those commands — tokens in known formats, Authorization header values, passwords in URLs, flags and variables such as DB_PASSWORD — are masked in the gateway, before anything is written. This is pattern matching: a secret in an unfamiliar format can get through.
- Meter does not keep prompt text, response text or code.
Keys
- Your team’s Anthropic or Ollama key is encrypted in the database with AES-256-GCM and never sent back to the browser.
- The Meter keys developers put in their agents are stored only as a SHA-256 hash; a key is shown in full once, when it is created.
- Only the team’s key goes to Anthropic; a developer’s key never does.
- Error reports carry no request bodies, cookies, headers or keys.
Teams kept apart
- The team comes from your session or key — never from a header or parameter the client sent.
- Every analytics read is filtered to one team; live updates never cross teams.
- Owner, admin and member roles are checked on the server; revoked access is gone within about 10 seconds.
Signing in
- Passwords are stored only as a stretched hash (scrypt), at least 12 characters; the email address must be confirmed.
- Google and GitHub sign-in is protected by state, PKCE and token verification.
- Sign-in attempts are rate limited; a password reset link works once, for an hour, and ends every session.
How long data is kept
- Call records are deleted after 13 months.
- The event queue holds them for up to 7 days, so none is lost while storage is down.
- You can delete your own account: your calls stay in the team's history only under an anonymous id. An owner can delete the team and everything it holds.
Hosted service
- The API, gateway and databases run on Oracle Cloud, region eu-frankfurt-1 (Frankfurt, Germany); the dashboard and public pages are on Vercel.
- Every night the database of users, teams, keys and policies (Postgres), together with the encryption key, is copied, encrypted, to separate storage in the same region, away from the server. Call records are not part of this backup.
Not there yet
- SSO (SAML or OIDC).
- Certifications (SOC 2, ISO 27001).
Self-hosted
On contract, Meter deploys into your cluster with a Helm chart we provide. Your data then stays in your infrastructure, and nothing in it phones home. Write to us at support@metergateway.com.