Privacy Policy

LivingRuntime Remote connects ChatGPT-compatible clients to machines and repositories that the user is authorized to control.

Data handled

The public relay may process OAuth account identity, OAuth client metadata, hashed token values, pairing/device metadata, and the bounded tool inputs and outputs needed to route a request to the paired Connector. The Connector may also maintain non-secret SSH host aliases, allowed roots, project aliases, allowlisted service names, and local audit records.

Credentials

LivingRuntime Remote does not store SSH passwords or SSH private keys on the public relay. SSH credentials remain in the user's existing SSH configuration on the Connector machine. OAuth passwords are stored only as salted scrypt hashes, and raw OAuth bearer, refresh, and device tokens are not stored in relay databases.

Sharing and retention

When Remote is used with ChatGPT or another compatible client, tool arguments and results travel through that client's MCP request path and the LivingRuntime Remote relay. Successful relay task results are consumed after delivery; stale task records are eligible for cleanup after 24 hours. OAuth account and paired-device records remain until revoked or removed. Local configuration and audit logs remain on the user's machines until deleted.

ChatGPT-side retention follows the user's OpenAI account or workspace settings. Do not place secrets in tool arguments or file contents that you do not want transmitted through the connected client and relay.