Privacy and security, in plain words.

What stays on your Mac

• The Lokstack server listens on 127.0.0.1 only and cannot be reached from the network.
• Every change request needs a custom header and a localhost host, which blocks other websites and DNS-rebinding attacks.
• There is no account, no analytics and no telemetry.
• Secrets in .env files (passwords, secrets, keys, tokens and URL passwords) are masked.
• Your settings live in ~/.lokstack on your Mac.

When Lokstack uses the network

• When you search for packages (npm, Packagist, PyPI) or install them.
• When you install with Homebrew or pull Docker images.
• When you sign in to GitHub from the app (the sign-in happens on github.com in your browser, and the result is kept in your macOS keychain) and when you push or pull.
• When you activate a Pro key: it is checked with our licence provider, then every 7 days. The free plan and the trial never leave your Mac.

Safe by default

• Destructive actions confirm first.
• Deleting a container keeps its volumes. “Forget” never touches project files.
• Package names and container settings are validated before they reach a package manager or Docker.

How the app protects itself

• Local only. The app’s own server listens on 127.0.0.1 and answers only its own window: every request needs a token made fresh at each launch, and requests from other hosts, other origins or other websites are refused.
• Named addresses stay on your Mac. myapp.localhost is served on the loopback address only, never on your Wi-Fi address, and it can never reach Lokstack’s own API.
• Updates are verified. A new version installs only if it is signed by our Apple Developer team and notarized by Apple. A download signed by anyone else is refused, even if it carries the Lokstack name.
• Repositories cannot reach outside themselves. File views and the conflict resolver follow symbolic links only inside the project, so a cloned repository cannot read or write your other files. Branch, remote and package names from a repository are shown as text, never run as code.
• Email and files are sandboxed. HTML emails from your mail catcher render in a sandbox with scripts off; files from your buckets download as data, never as pages.
• Agents work in lanes. An AI agent gets its own branch, port and database copy. Nothing merges into your main branch, and nothing touches your main database, until you choose in Lokstack. The MCP tools that agents use go through the same local token.
• No telemetry. The app sends nothing about you. Error reports go out only when you press Send, and are redacted first.

This is what the current version does; it was checked in a security review before release and is re-checked with every build. Found something? Write to support@lokstack.app and we answer fast.

This website

Questions