Privacy · Showcase edition
Privacy, in concrete terms.
The public SystemLens demo uses deterministic invented fixtures and does not collect from a live PC.
Quod does not currently operate the production backend, OAuth service, or public companion connection described by the architecture. Running the local fixture demo sends no machine telemetry to Quod or OpenAI.
Data processed
Depending on the requested tool, SystemLens can process an internal account subject; device UUID and label; OS and hardware summaries; fixed-volume storage; process names and resource totals; startup entries; driver metadata; sanitized grouped crash or Windows diagnostic-event evidence; service state; minimized network state; attached USB metadata; bounded installed-software metadata; and safe OS-reported sensor availability.
How collection works
Collection is on demand. The companion validates each request against a fixed allowlist, applies local sanitization, and returns a bounded structured result. It does not continuously index the computer or personal documents.
Reference architecture storage
The source demonstrates request-lifetime telemetry, short-lived encrypted snapshots, expiring single-use pairing codes, and one-way device-token verification for a potential hosted deployment. Those components are not currently operated as a public service. A future deployment would require an updated effective privacy notice and verified retention controls.
Explicitly excluded
SystemLens does not collect arbitrary file contents, documents, browser activity, passwords, tokens, command lines, process memory, keystrokes, clipboard data, camera or microphone input, unrestricted Registry data, or unrestricted Event Logs. User-profile paths and common secret patterns are sanitized locally before transmission.
Sharing and model use
The local demo does not call an OpenAI API. In the intended MCP architecture, ChatGPT would receive requested diagnostic evidence under the user’s applicable OpenAI terms and settings. SystemLens includes no advertising or third-party analytics.
Local removal
Delete the cloned repository and its generated build outputs to remove the local demo. A locally built companion can remove its DPAPI-protected credential with the documented unpair command.