Policy

Privacy,
plainly stated.

This page covers the Lattice docs site, the CLI and daemon, and the browser extension as distributed by fordz0.

// Summary

Short version

Lattice is designed to keep browsing and publishing local-first. The docs site is a normal static website. The daemon and browser extension run on your machine and primarily talk to your local node and to the peer-to-peer network you choose to join.

We do not run a central Lattice account system, and we do not sell personal data.

// Website

What the docs site collects

lattice.benjf.dev is a static documentation site. Like most websites served over the public internet, basic hosting-layer request logs may exist, such as IP address, user agent, request path, and timestamp.

The docs site also makes a client-side request to GitHub's public releases API to look up the latest Firefox and Chromium extension assets when showing install links. That request goes directly from your browser to GitHub.

// Extension

What the browser extension does

The Lattice browser extension is used to detect .loom browsing, route supported requests through the local Lattice daemon and proxy, open setup/help pages, and query the latest extension release metadata on GitHub when you ask it to check for updates.

The extension does not provide advertising, analytics, or remote code execution. It does not download and execute arbitrary JavaScript from a remote server.

The extension may access:

  • tabs, so it can open setup pages and update the active-tab experience
  • web requests and proxy settings, so it can route .loom traffic through the local daemon
  • GitHub release metadata, so it can show whether a newer extension version exists
  • the local daemon endpoints on 127.0.0.1 / localhost, so it can download the local CA certificate and check daemon state
// Daemon

What the CLI and daemon do

lattice and lattice-daemon store local state on your machine, including node identity, local configuration, cached records, and published content you choose to serve. They connect to other peers on the Lattice network in order to resolve names and exchange content.

If you publish a site, name records, manifests, and the site content you choose to publish become available to other peers by design.

// Sharing

How information is shared

Lattice is a peer-to-peer system. When you use it, your node may exchange requests and content with other peers on the network. That means your IP address and requested content can be visible to peers you communicate with, just as they are in many peer-to-peer systems.

We do not operate a separate central database of your browsing or publishing activity.

// Retention

Data retention and control

Most Lattice state is controlled locally by you. You can inspect, back up, or delete your local data directory. On Linux this is typically ~/.lattice unless you override it. On newer macOS and Windows installs, Lattice uses platform-native app data directories by default.

Published network content may continue to exist on other peers after you stop serving it.

// Contact

Questions

If you have questions about this policy or want to report a privacy issue, use the project issues page:

github.com/fordz0/lattice/issues