// PRIVACY

Privacy

Last updated October 14, 2026

The short version

  • Steroid builds your project memory on your own device.
  • Storing and retrieving that memory happens entirely on your device, and Local mode needs no Steroid account.
  • When your coding agent asks for context, Steroid hands it the relevant pieces, right on your device.
  • Steroid does not collect your code, files, conversation text or project names.
  • By default the CLI sends aggregate usage counts tied to a random install ID, and you can turn that off. See Telemetry for every field.

Your project memory

Steroid builds a memory of the work you have done on each project with your coding agents — Claude Code, Cursor, Codex and GitHub Copilot CLI — and keeps it on your device. It stays up to date as you work. If an agent deletes an old session, Steroid forgets it too the next time its memory refreshes.

What your agent receives

When your coding agent asks for context, Steroid gives it only what is relevant to the question, and that hand-off happens on your device. Nothing is sent to Steroid. Your agent then uses that context like anything else in your conversation with it, under the terms of the agent and model provider you already use.

Network requests the CLI makes in Local mode

The CLI checks GitHub once a day for a newer release. That check contains no project data.

Unless you opt out, the CLI also sends aggregate usage counts to telemetry.steroidkit.com: for example whether a recall was answered, a coarse time bucket, or which setup or update step failed. They are tied to a random install ID that is not linked to any account, and they never contain your code, files, conversation text, recall questions or answers, project names or paths. The full list of fields, how long they are kept, and how to opt out (steroid telemetry disable or DO_NOT_TRACK=1) are on the Telemetry page.

This website

steroidkit.com counts page views and clicks on the install and other buttons, so we can see which parts of the site help people install. These counts carry no identifier: the site sets no cookies and stores no visitor ID or analytics data in your browser, so events from the same browser cannot be linked. Each event records the page's name, the domain of the page you came from, your browser and operating-system family and your country, and for install actions the operating-system tab, the install option and where it was opened. The site honors Do Not Track and Global Privacy Control. See Telemetry for every event. If you join a waitlist, request support for an IDE or send an enterprise inquiry, we store the details you enter so we can contact you about that request.

Connected mode

Connected mode — the MCP marketplace, Flows and the Vault — is not available yet. It will use Steroid servers. This page will describe exactly what Connected mode sends before it launches.

Contact

Questions about this page: [email protected].

Steroid Kit logo

Steroid_Kit

Local-first recall for coding agents.

RESOURCES

DOCSRELEASESGITHUB

© 2026 STEROID_LABS