Privacy

SLEDS meters the cost and limits of AI agent work. This page says exactly what each part reads, what leaves your machine, where it goes, and how long it stays. Plain words; no marketing.

Who runs this

SLEDS is operated by sleds.ai. Questions and deletion requests: privacy@sleds.ai.

The Chrome extension (SLEDS for Chrome)

The extension exists to show your own Claude usage limits per model in one place and, with your consent, report them to your team's SLEDS dashboard.

• What it reads: the usage panel of the claude.ai account signed in to that Chrome profile (per-model limit percentages, session and weekly limits, reset times, whether extra usage is on), plus which organization is active. It reads this in your browser using your existing session. It does not read your conversations, messages, files, or any other claude.ai page.
• What it sends, and only after you agree: those percentages, reset times, model names and the credits state, to the SLEDS proxy (proxy.sleds.ai) for the seat you connected with your seat token. Nothing is sent before the consent screen; the consent text on that screen is the complete list. It refuses to post when the browser's claude.ai account is not the email of the connected seat, and shows you why.
• What it never sends: cookies, session tokens, conversation content, page content, browsing history, or anything from other sites. It has no access to other sites.
• What it stores locally: your settings (proxy URL, seat token, notification choices) and a trailing 24 hours of readings, in the extension's own storage on your machine. Remove the extension and they are gone.
• Permissions: storage (settings), alarms (the poll), notifications (threshold and reset alerts you can turn off), clipboardWrite (the "Take it" button copies a command), host access to claude.ai (the read) and proxy.sleds.ai (the post).

The CLI, the proxy and the dashboard

• The CLI (sleds) runs on your machine. It reads Claude Code's status-line data (limit percentages, reset times, the session id, the working directory, the model) and posts the limit data to the proxy for your seat. When SLEDS is switched onto an org key, your requests go through the proxy; otherwise they do not touch it.
• The proxy forwards requests to the model provider and records usage: token counts, model, cost, timestamps, and at a wall the provider's error and a snapshot of the request so the session can be resumed or handed to a teammate. Snapshots expire; zero-data-retention orgs keep none.
• The dashboard shows this to members of your org and nobody else. Sign-in is a magic link to your work email.
• The connector (SLEDS in claude.ai) is authorized by a link mailed to your work email and gets the same access as your seat; tokens are stored hashed and can be revoked.

What we do with it

Run the product for your org: meters, estimates, walls, jobs, hand-offs, attestations. We do not sell it, share it with advertisers, or use it to train models. Email is sent through Resend; hosting is Convex, Fly.io and Vercel.

Retention and deletion

Usage rows stay as long as your org has an account. Request snapshots expire after their window. Revoking a seat ends its access; deleting an org removes its data. Write to privacy@sleds.ai for a deletion and we do it within 30 days.

Updated September 7, 2026.