Security
Your computer stays the boundary.
Local Computer is built so the website can help with identity and connection without becoming the place where your files, commands, or local task output are processed.
Local work stays local
The Local Computer Runtime runs on your device. Your project files, workspace paths, Git content, shell commands and output, background-job state, local OAuth tokens, and Runtime logs are not proxied through or stored by this website Worker.
Access is explicit
ChatGPT does not receive blanket access to your whole computer from this website. Local Computer exposes local tools and owner-approved folders through the installed product.
What that means in practice
- You choose which local folders to open for file work.
- The installed app manages the ChatGPT connection rather than asking you to expose port 7676 or configure Cloudflare manually.
- You can stop the local Runtime or disconnect the managed connection.
Account data is deliberately small
The current account/control-plane design stores bounded identity and device metadata rather than your work. GitHub is currently used to verify an opaque account identity for the Preview web account flow; GitHub access tokens, email addresses, and login names are not stored in the device registry.
Local Computer may store device identifiers, display names, platform and lifecycle timestamps, plus the minimum managed-network metadata needed for a device connection.
Preview signing status
The current Windows Preview installer is not yet signed by a Trusted Publisher. Windows may show SmartScreen or Unknown Publisher. Trusted Publisher signing remains a release gate before broad public distribution.