Privacy Policy

Locus is local-first. Workspace files and saved sessions live on your Mac. Local Ollama inference runs there too. Hosted models, image generation, connected tools, browsing, and downloads contact the services you choose. App update checks contact GitHub and can be controlled in Settings. Locus does not require a SparkTales account or send analytics or telemetry to SparkTales.

• Conversations — append-only JSONL files under ~/.ollama-code/sessions. Titles, pins, and archive flags live in a sidecar manifest, so renaming a session never rewrites its transcript.
• Deleted sessions — clearing saved sessions moves them to ~/.ollama-code/session-trash/<timestamp>/ with a manifest of their metadata. They are recoverable until you delete them yourself.
• Workspace state — recent workspaces, per-workspace profiles (model, mode, browser home URL, draft, context-file references), drafts, and prompt history. File contents are re-read from disk when needed; profiles store references, not copies.
• Console input — what you type into a running console command is never written to disk.
• In the sandboxed Mac App Store build, the agent’s data lives inside the app container instead, and workspace access persists through security-scoped bookmarks.

API keys, MCP tokens, and proxy passwords are stored in ~/.locus/auth.json — a file with mode 0600 inside a 0700 directory, so no other user account on the Mac can read it. Keys reach the local agent in memory only: never in its config file, never in a session transcript, never returned by any API, and only ever sent to the provider they belong to. Removing an account deletes its key.

A proxy password is deliberately withheld from anything the model can run — shell commands, the console, git, and stdio MCP servers receive the proxy address with the credential stripped.

Only what you configure, to where you configured it:

• Hosted model accounts — when you add and select a Claude, Codex, Kimi, Kimi Code, or custom endpoint account, the messages, attached files and images, and context packs you send go to that provider, under your agreement with them. Until you add an account, nothing of the sort happens.
• Image generation and editing — after you choose an image API account and approve a call, the prompt and any source image for an edit go to that provider. The approval names the model, provider host, and destination. Generated files are saved in your workspace. Interactive answer widgets run in an offline view with a written summary.
• App and component updates — the direct-download app retrieves update metadata and signed downloads from GitHub. From 2.7 onward, app updates can check daily, download in the background, and install when you quit. Manage automatic checks and downloads in Settings → Updates. These requests do not include your conversations or workspace files.
• Model downloads — browsing the model library and downloading GGUF weights contacts Hugging Face.
• Extensions and MCP servers — installing from the marketplace clones its catalog; MCP servers you connect receive the tool calls the agent makes to them, and remote servers may hold an OAuth token for you.
• Ollama on another machine — if you point the agent at an Ollama host on your LAN, model traffic goes to that host.
• A proxy — if you configure one in Settings ▸ Network, the traffic above flows through it. Loopback and the Ollama host always connect directly.

The agent’s web-fetch requests identify Locus with a Locus/<version> identifier. Other connected services and the updater use their own request protocols.

The bundled agent listens on 127.0.0.1 only. It rejects requests carrying a browser Origin header, and the app protects each launch with a fresh capability token shared only with the agent process — so a web page you visit cannot drive file or shell tools through localhost.

In signed direct-download builds, you may opt in to letting the agent drive Mac apps. Screenshots it captures are window-scoped and exclude Locus itself. Before any screenshot is sent to a hosted provider, that provider is named and consented once per session. Read-only inspection is automatic; clicks, typing, keys, scrolling, and dragging follow the same permission mode as everything else, with non-bypassable safeguards for credential entry and high-consequence actions. The App Store build does not include this feature.

Clear Chat and Clear Saved Sessions remove conversations from the active list and keep them recoverable in the local trash; empty that folder to erase them. Removing a provider account deletes its key. Uninstalling the app removes the program; the data folders above remain under your home directory for you to keep or delete.

This website demonstrates Locus in your browser. Demo tasks, permissions, and model switches are illustrative and do not access your machine. The website does not set tracking cookies or send pageview analytics from its application code. The hosting provider may process ordinary request information, such as IP addresses and browser details, to deliver and protect the site. External links take you to services governed by their own privacy policies.

When you use the contact form, your name (if provided), email address, topic, and message are sent through Postmark to contact@locushost.co so we can respond. The form does not subscribe you to marketing emails. Email open and link tracking are disabled. Our hosting provider processes request information to limit abuse.

If this policy changes, the revised version is posted on this page with a new date. The promises that matter — local by default, hosted only when you choose — are enforced by the code, not just stated here.

For privacy questions or to report a security issue, email contact@locushost.co directly. Please report security issues privately.