Security
Updated November 7, 2026
Remote access to your computer
The REM:Code agent runs coding tools and their commands with the permissions of your computer account. Connect only computers you control or are authorized to use. Approval prompts depend on the selected coding tool and session settings; auto-approval can allow actions without a prompt.
The relay can read traffic
Your computer opens an outbound tunnel. Both connections to the relay use TLS, but the relay terminates them and can read forwarded messages, files, and responses. Interactive traffic is not end-to-end encrypted. The relay does not maintain a conversation archive. It temporarily keeps pending messages and session summaries in memory for reconnection. Your devices and coding tools keep their own history and caches.
Account and operational data
We store account identifiers, sign-in sessions, token hashes, linked device and agent records, push destinations, approximate location, and technical telemetry. Device linking temporarily stores a secret and an issued token until collection or expiry. Operational logs can contain IP addresses, request metadata, and error details.
Optional features
- Voice: recordings pass through the relay to OpenAI for transcription. Temporary upload files are removed after processing.
- Notifications: delivery providers receive device tokens and payloads that may contain project names or request text.
- Shared builds: new shares keep the file on your computer. The relay stores encrypted metadata and a source reference, then streams downloads from your online agent. Anyone holding the link can download the build. Links expire within one hour and can be revoked. The relay can read the metadata and download traffic when the link is used.
Protect your signed-in devices and shared-build links. See the Privacy Policy for storage, retention, providers, and your choices. Report problems to hello@remcode.app.