We are developers building tools for developers. We hate sneaky telemetry as much as you do. Here is exactly what the Community Edition collects, why it collects it, and how to opt out.
The Philosophy
The modern web is a nightmare of randomized CSS classes and broken DOMs. The LumaBrowser Template Builder solves this. To make this tool truly powerful, the Community Edition operates on a shared-knowledge model: your generated selectors help build a public repository of resilient templates that benefits the entire ecosystem. Anonymous usage analytics tell us which features matter most so we can focus development where it counts. We collect the minimum needed to improve the product and nothing more.
What We Collect
Community Edition only. Paid tiers collect nothing.
Anonymous Machine Identity
A hashed, anonymous machine identifier is generated locally to distinguish unique installs. No personally identifiable information (name, email, IP address) is attached. We pair this with your platform, architecture, and app version so we can track adoption across OS targets.
Application Lifecycle
We record when the application is launched. This helps us understand active usage patterns and session frequency.
Feature Usage
High-level events for core user actions: tab creation/closure/navigation, AI chat completions and streaming sessions, template generation, timed task scheduling and execution, network watcher configuration, webhook setup and testing, extension toggling, LLM provider configuration, and settings changes (API port, API/MCP enable state). No content, prompts, URLs, credentials, or response data is included in these events.
API Request Activity
For requests made to the local REST API (used by MCP clients and automation tools), we log the HTTP method and route path for non-GET requests. No request bodies, headers, or response data are transmitted.
Template Generation Data
When the Template Builder analyzes a page to generate CSS selectors, the target domain, URL path, and the resulting generalized selector map are sent to our shared template repository. We strip all user-specific context, input values, query parameters, and session tokens before transmission.
Crash & Error Reporting
Unhandled exceptions and native crashes are reported via Sentry to help us identify and fix bugs. Stack traces and error messages are included; no user content or browsing data is attached.
What We NEVER Collect
Your API Keys or Credentials
Your Anthropic, OpenAI, and other provider keys never leave your machine. They are stored securely in your local SQLite database.
Prompts, Conversations, or AI Responses
We track that a chat completion or streaming session occurred, but never the content of your prompts, system messages, or model responses.
URLs, Page Content, or Browsing History
We do not track the URLs you visit, the pages you browse, cookies, or local storage. Tab events include no URL or page data.
Local WebGPU Data
If you use the WebGPU extension for local model inference, zero prompt or response data is transmitted to us.
Intercepted Network Traffic
The Network Watcher processes everything locally. We do not see the payloads, headers, or webhooks you forward traffic to.
Personally Identifiable Information
No names, email addresses, IP addresses, or geolocation data are collected. The machine identifier is a one-way hash that cannot be reversed to identify you.
How to Opt Out
If you are working on highly sensitive proprietary applications, scraping internal corporate dashboards, or simply prefer absolute isolation, we are building the Pro Solo and Enterprise Fleet tiers.
Upgrading to a commercial license immediately severs all telemetry connections and keeps your generated templates strictly localized to your machine's SQLite database.
Want total privacy? Join the Pro waitlist.
Be the first to know when Pro Solo launches. Early adopters get locked-in pricing.
