Privacy

Last updated: 19 April 2026

Lattice is deliberately minimal about what it collects. This page explains what data the service stores, why, and where.

The one cookie we set

When you first load Lattice, the server issues an HttpOnly cookie named lattice_uid containing a random UUID. That identifier is used only to scope your read, saved, and subscribed-sources state to this browser. It is not linked to any personal information and cannot be used to identify you across devices or websites.

Clearing your browser cookies for readlattice.co removes your state completely. There is no account to delete.

What we don't do

• No analytics (no Google Analytics, Plausible, Mixpanel, etc.)
• No third-party tracking scripts or pixels
• No advertising
• No account, no email, no password
• No selling or sharing of any data with anyone

Server logs

The server records standard request logs (client IP address, request path, HTTP status, timestamp) and container telemetry via Azure Log Analytics for operational troubleshooting. These are retained for up to 30 days and are not correlated with the lattice_uid cookie.

Article content

When you open an article, Lattice fetches it from the original publisher over HTTPS and extracts the readable text via Mozilla Readability. The extracted content is cached on our server for seven days to reduce repeat requests. The original URL is always one click away via the "open in browser" button.

Feed requests

If you submit a feed via the "Request a feed" form, we store the URL and any name/category/note you provide, linked to your lattice_uid, so we can review it and show you its status. Feed requests are not shared publicly.

Where this runs

Lattice is self-hosted in Microsoft Azure (UK South region). The Postgres database holding state is a managed Azure service. We do not use third-party CDNs or fronting services that inspect traffic.

Contact

Questions: hello@dcwd.dev.