OPENGLASSUI / PRIVACY

OPEN SOURCE / PRIVACY

Your setup.
Your data.

OpenGlassUI is a self-hosted control surface for your coding agents. The companion has no built-in analytics or telemetry sent to an OpenGlassUI-operated service.

What that means

OpenGlassUI still stores data locally and communicates with the agent, devices and connection services you choose. Those components have their own behavior and privacy policies.

01 / LOCAL COMPANION

What stays on your machine

By default, OpenGlassUI stores configuration, approved projects, paired-device records, task prompts, agent output and conversation history in .openglass/. Your config.json is stored separately. Local task data is not encrypted at rest. The OPENGLASS_DATA_DIR variable can change the data location.

The paired device stores a bearer token and interface preferences in its browser storage. The companion stores a hash of the token, not the token itself. A paired device can access registered projects and tasks.

02 / YOUR CONNECTIONS

Where data can travel

  • Coding agents and model providers. OpenGlassUI sends tasks to the selected local agent. That agent may send prompts, project content and tool output to its configured provider, subject to its own settings and policies.
  • Glasses and Meta. The glasses web app communicates with your companion through the chosen HTTPS connection. Meta's device and companion software have their own data practices; OpenGlassUI does not control them.
  • Tunnel providers. Cloudflare, ngrok, Tailscale or another configured proxy carries connection traffic. Public providers expose the gateway over the internet; the provider may process connection metadata and, depending on its service, traffic.
  • Optional Web Push. If supported and explicitly enabled, push services receive encrypted generic events and connection metadata. Messages do not include task text. The tested glasses browser did not support the required Push and Notification APIs.
  • Installation and updates. Downloading the repository, npm dependencies or tunnel software contacts their respective hosts, including GitHub, npm or Homebrew when used.

03 / CONTROLS

Stay in control

Only approve projects and pair devices you trust. Revoke paired devices in the local dashboard. Treat pairing links and QR codes like passwords, and forward only the gateway port through a tunnel.

To remove local OpenGlassUI task data and paired-device records, stop the companion and remove its data directory after backing up anything you need. This deletes stored OpenGlassUI history and pairings; it does not delete histories held by your agents or their providers.

OpenGlassUI is an experimental single-user project, not a hardened multi-user service. See the security guidance and inspect the source.

04 / PUBLIC DEMO

About this website

The public demo runs with fictional data in your browser and has no connection to your local agents. Theme and interface preferences may be stored in browser storage. The site is hosted by GitHub Pages; GitHub may process ordinary hosting and network data under its own policies.

No third-party analytics integration is included in this site's source.