Data Privacy
Sleev runs on your machine. The local gateway handles optimizations, session state, and provider calls on your machine. When you’re signed in, Sleev receives limited non-content usage, account, billing, service health, and license metadata for dashboards, support, and license checks.
Sleev does not receive your prompts, code, files, LLM responses, or provider keys during normal operation. With an offline license, request tracking stays local and Sleev does not collect usage data during day-to-day gateway use.
What stays on your machine
- User prompts and assistant responses
- Code, files, and tool output
- Provider API keys
- Session history, including optimization byproducts of Sleev’s pipeline
The one exception: if you manually share a diagnostic bundle from the CLI, it uploads recent redacted gateway activity. Private data is removed or protected before the bundle is saved and shared.
Licensed offline use
Accounts approved for offline licensing can use offline licensing for machines that need to run Sleev without regular online account checks. During licensed offline use, Sleev does not receive tracking data, request metrics, usage events, or usage patterns.
Online access is still needed to install or update Sleev, create or renew a license, and reach whatever model provider your harness uses.
Zero collection
Enterprise users can run Sleev with zero telemetry by using offline licenses. In this mode, the gateway verifies its signed offline license locally and Sleev does not receive telemetry, tracking data, request metrics, usage events, usage patterns, prompts, code, files, model responses, provider keys, or local session contents from licensed day-to-day gateway use.
Creating, renewing, supporting, or updating an offline license may still require account, billing, support, and license-administration data. Your configured model provider still receives the requests your harness sends through the local gateway.
For more info, see the Privacy Policy.