What Lodestar collects
What the agent sends to the console, what it never collects, and where it is kept.
When a device enrols
The device sends its hostname, serial number, model, operating system and version, the agent version, and a hardware identifier.
In each report
- The users on the device, by their home folder names.
- The agent and catalogue versions.
- Each AI tool found: what kind it is, its name, version, location on disk, the user it belongs to, and when it was last active. For an extension, also the browser or editor and the profile it was found in. A browser profile name can be a person's name.
- Extra detail by kind: an app's bundle ID or publisher, an extension's ID, where a command-line tool links to, the names of up to eight local models and their total size, or the name of an MCP server and the command or host it uses. For Claude Code, also the name of the project folder an MCP server is set up for.
- If account plans are on: the plan and the email domain an AI tool is signed in with.
- The agent's last update: the version, whether it started, installed or failed, any error, and when.
Network use
Only connections to known AI services are kept. Everything else is dropped on the device.
| Platform | How | What is kept |
|---|---|---|
| Mac | A network extension that only observes. It reads the service's host name and nothing after it. | The app, its path and bundle ID, the AI service's host, first and last seen, and how many connections. |
| Windows | The DNS lookups Windows makes. | The program and its path, the AI service's host, first and last seen, and how many lookups. |
What Lodestar never collects
- The content of any file, message, prompt or web page.
- Browser history, or keystrokes.
- Full email addresses, passwords, tokens or API keys.
- The arguments, environment variables or headers of MCP servers.
- Connections to anything that is not a known AI service.
Lodestar never blocks traffic.
How often
A device reports once a day, and straight away when it enrols. While it is online, it keeps a request open to the console, so commands such as audits reach it within seconds.
How long it is kept
What is in use now is always kept. Removed tools, older network use and device timelines are kept for each client's history period, 90 days by default.
Where it is kept
The console and its database run in Germany, on a dedicated server Panoptic rents from OVHcloud near Frankfurt. The full list of sub-processors and retention periods is in the privacy notice.