Data Privacy

Sleev has two operating modes: the managed cloud service and the local npx sleev package. They make different privacy tradeoffs so you can choose the setup that fits your workflow.

Cloud

In the managed cloud service, Sleev sits between your coding tool and your model provider. We store as little as necessary to run the product: account records, sleeve-token metadata, usage/accounting metadata, and the partial conversation state needed to compress and continue sessions.

That conversation state is treated as operational data. We do not ask for or store your provider API keys; those stay in your local harness or provider config and are sent with each request only as needed by the proxy.

Local

With the local npx sleev package, LLM traffic, conversation content, and compression state stay on your machine. The optimization work happens locally instead of through the managed Sleev proxy.

Sleev may still receive the minimal service data needed for analytics, authentication, and basic accounting, all of your private data stays private.