Privacy

Last updated 2026-07-30. This covers the LucidPilot Chrome extension (free overlay + audit log, and the Pro control engine).

What stays on your device

Everything LucidPilot records lives in chrome.storage.local, on your machine, and is never sent to us or anyone else:

The session audit log: timestamp, action type (click/type/scroll/navigate), coordinates, page hostname, which agent (Claude, Hermes, etc.), and a short description of the element acted on (its tag and visible label). Capped at 500 entries; oldest entries drop off first.
Typed text and form values are never captured, only the fact that typing happened.
Page snapshots (accessibility-tree/DOM snapshots the control engine requests on your behalf) and any screenshots produced by your own actions or an agent's navigation, both stay local to the browser session and are not uploaded anywhere by the extension.
Network and console records, only if you use the Pro control engine and the driving agent (Claude Code, Hermes) requests them, are read from the page you're already on and returned to that agent's own tool. LucidPilot itself doesn't collect or store them separately.

What we don't do

No telemetry or analytics. LucidPilot doesn't phone home about your usage, browsing, or extension activity.
No cloud storage of your audit log, snapshots, or session data.
No sale or sharing of any captured data. There's nothing to sell, it never leaves your machine.

The one thing that does leave your device

Buying Pro. When you click "Get Pro" on this site, your email and the plan you picked are sent directly to our licensing service (api.lucidfabrics.com) to start a Stripe Checkout session, and Stripe handles payment. That's the entire scope of what leaves your device, and it only happens if you choose to purchase Pro. Your license key is emailed to you and verified locally by the extension; verification does not report your browsing back to us.

Marking sensitive domains

If you configure a sensitive-domain list (e.g. your bank), that list is stored locally in the extension and used only to decide when to show a red warning border. It is not transmitted anywhere.

Questions

Open an issue on the project repository, or reach out via the email used at checkout.