Privacy.

The short version

• Local desktop use does not require a Lomi account. Account-backed features such as Remote are optional.
• Workspace files, preferences and chat history stay on your device unless you choose to send or share them.
• AI providers and CLI agents you configure receive the prompts, context and files you send through them. Their own privacy policies apply.
• Lomi checks GitHub for app updates. The website loads YouTube only after you allow external media, and sends a newsletter signup only when you submit the form.

What Lomi stores on your device

• Preferences, workspace layout and session state so you can resume your work.
• Chat history and other local app data used by the workspace.
• API keys and remembered account sessions in your operating system's credential store when available. If it cannot save an account session, Lomi can keep it in memory until you quit.
• Your project files in the locations you chose. Lomi does not upload them as part of local desktop use.

Local CLI agents and plugins may keep their own files or history. Their behavior is controlled by those tools and their providers.

What the desktop app sends over the network

Lomi connects to services when a feature needs them. Some checks, such as the automatic update check, can happen without a separate click each time.

• AI chat: prompts, selected context and attachments go from your device to the provider configured for that connection. With a local model, requests go to the local endpoint you configured. Lomi does not proxy chat requests.
• CLI agents: agents you run in a terminal may contact their own services and send data according to their settings and policies.
• App updates: Lomi checks GitHub Releases after a workspace starts and when you request a manual check. It downloads an update only after you choose to install it.
• Git: fetch, push and other network operations use the remotes and credentials configured for your project.
• Browser previews: a preview connects to the URL you open. A local development server stays on your network; an internet URL connects your browser to that site.

Optional account and Remote features

Local work does not need an account. If you choose an account-backed Lomi feature, sign-in uses GitHub. Lomi's account service receives the profile details needed to create your account, such as your GitHub username, name and email, along with session and security information. GitHub processes the sign-in under its own privacy policy.

If you connect to Lomi Remote or share a workspace, the account and Remote services process the information needed to authorize access and provide that feature, including workspace and terminal state you choose to share. Anything shown in a terminal may contain project or personal information, so review it before sharing. Account deletion removes your profile, provider tokens and linked access; security audit events may remain without being associated with your account.

What the lomi.dev website stores and sends

• Privacy choice: the site stores your optional-media choice in this browser's local storage for up to 180 days. It is not an HTTP cookie and is not sent to our server.
• YouTube: embedded videos stay off unless you allow external media. If allowed, your browser connects to YouTube, which may receive browser and device information.
• Downloads: the download page requests public release information from GitHub.
• Newsletter: when you submit the signup form, the email address you provide is sent to the configured newsletter service. The service processes the request and may receive standard connection information.
• Website hosting: the host serving lomi.dev may process standard request data such as IP address, browser user agent and requested path to deliver and protect the site.

We do not add separate analytics, advertising cookies or third-party tracking scripts to the website. YouTube may serve ads in its player. Fonts, icons and page images are served with the site. External links take you to services with their own privacy practices. You can review cookie and media settings or change your choice using Cookie settings in the footer.

Third-party providers

When you send a prompt or run an agent, the provider you chose receives and processes that data. Providers may retain it under their own terms. Lomi cannot see or control their retention. For data that must stay on your device, use a local model and avoid tools that send project content to external services.

Changes

If this policy changes, we will update the date at the top of this page. Material changes may also appear in the release notes.

Contact

Privacy questions: admin@lomi.dev. Source code: github.com/lomi-dev/lomi.