This policy explains what Sleev receives, what stays on your machine, and how we use data.
1. Local by design
Sleev runs through a local process on your machine: “the gateway”. It stores operational data in a database and files on your machine. You control those files.
The gateway handles user prompts, assistant responses, code, files, tool output, provider API keys, session history, and optimization byproducts on your machine during normal operation.
2. Data Sleev receives
Sleev receives the data needed to operate the service:
- Account data, such as your email, name, account identifier, and sign-in provider details.
- Gateway connection data, such as installation identifiers, token records, labels, status, and timestamps.
- Usage and debug metrics about gateway operation, performance, errors, and savings measurements.
- Diagnostic log uploads, if you choose to share them from the TUI or CLI. Sleev-managed gateways redact prompt, response, and tool content from diagnostic logs by default. Uploaded bundles include operational metadata and are not intended to contain conversation content. Unexpected failures or nonstandard logging may expose sensitive details. Interactive uploads show a warning and require confirmation; passing
--yesto a noninteractive CLI upload explicitly confirms the upload.
Enterprise users using offline licenses can run Sleev under the zero collection policy below, with no telemetry sent to Sleev during licensed day-to-day gateway use.
3. Data Sleev does not receive
During normal operation, Sleev does not receive or store your prompts, completions, source code, workspace files, provider API keys, local gateway database, local session contents, or optimization byproducts.
The exception is voluntary diagnostic logs. If you share them from the TUI or CLI after confirming the upload, Sleev receives the redacted logs and operational metadata in the bundle for support and debugging. The bundle is not intended to contain conversation content. Unexpected failures or nonstandard logging may expose sensitive details.
4. Zero Collection Policy
Approved Enterprise accounts can use offline licenses to run Sleev with no telemetry sent to Sleev during licensed day-to-day gateway use. In that mode, the gateway verifies its signed license locally and local UI metrics remain local.
Creating, renewing, supporting, or updating an offline license may still require account, billing, support, and license-administration data. See Terms, EULA, and Offline Licensing for related terms and setup-specific details.
5. How we use data
We use the data we receive to authenticate accounts, connect gateways, show usage, debug problems, investigate diagnostic logs you choose to share, prevent abuse, maintain security, improve reliability, and communicate with you about Sleev.
Where privacy law requires a legal basis, we rely on the need to provide the service, our legitimate interests in operating and securing Sleev, and legal obligations where they apply.
6. Providers and vendors
Your configured LLM provider receives the model requests sent from the local gateway. That provider handles those requests under its own terms and privacy policy.
We use service providers for functions such as authentication, hosting, databases, storage, infrastructure, and security. They may process the data needed to provide those services for Sleev. We may also disclose information if required by law, to protect Sleev or others, or as part of a business transaction.
7. Retention and deletion
We keep account, gateway connection, usage metrics, debug metrics, and operational records for as long as needed to improve and provide Sleev, secure the service, comply with law, resolve disputes, and enforce agreements. Voluntary diagnostic uploads are used for support, debugging, security, and service reliability and are retained for no longer than seven days.
Deleting your account immediately revokes Sleev tokens and local installation credentials and makes the account inaccessible. Resumable cleanup then removes voluntary diagnostic uploads and sign-in-provider identities, deletes or anonymizes hosted account identifiers, cancels pending legal-notice emails, and removes recipient email addresses from legal-notice audit records. It does not delete files stored locally on your machine.
Historical usage metrics, debug metrics, backups, security records, or non-personal legal-notice audit records may be retained when necessary for the reasons above.
8. Your rights and contact
Depending on where you live, you may have the right to access, correct, delete, export, object to, or restrict the use of personal data we hold about you. You may also have the right to complain to your local privacy authority.
For privacy questions or requests, email us at support@sleev.ai.