# RemoteCommander — Privacy Policy Effective: 2026-09-28 Updated: 2026-10-27 (Google and Siglet sign-in clarification) Publisher: Vu Van Minh Quang (individual) — contact: vu.minh.quang@outlook.com ## 1. Summary RemoteCommander has two parts: - the **program on your computer** (`remote-commander-mcp`), which does the work: it reads and writes files, runs commands and keeps notes, on your computer; - the **relay** at `rc.rentaicoder.com`, a service the publisher operates on Cloudflare, which connects AI assistants such as ChatGPT to your computer. The relay carries requests and results between the assistant and your computer. It never stores or logs their content: no files, commands, outputs or chats. It keeps what it needs to know who you are, which computers are yours, and whether the service works. If you connect an assistant to the program directly, without the relay, the publisher receives nothing. ## 2. Your account You can sign in with Google or Siglet SSO when enabled. For direct Google sign-in, the relay requests only `openid email`. For Siglet, it requests `identity:basic` through Siglet's OAuth service. The relay never receives your provider password. It keeps: - a RemoteCommander account identifier and stable provider identifiers needed to recognize or link verified sign-in identities; - your verified e-mail address, when supplied by a provider, for display only (not as proof that two accounts belong to the same person); - the time the account was created. ## 3. What the relay keeps about your computers and connections - **Computers**: an identifier the program generates, the name and platform it reports (for example `MYBOX`, `windows`), when it joined your account, when it was last seen, and whether you revoked it. - **Connection credentials**: hashes of the credentials your computers and your AI assistants use; the credentials themselves are never stored. Registered assistant clients (name and redirect addresses). - **Usage counts per computer**, reported by the program at most once a day: numbers of chats, tool calls and result cards shown and opened. No content. - **Security events**: a computer joined, was denied or revoked; you signed in, signed up or linked an account. Time, account and computer identifiers only. - **Sign-up statistics**: daily totals of steps of the connection page (shown, signed in, connected), with no identifier of any person. - **While a computer is connected**: the names of the memory threads it reports and how many open tasks each has, so the assistant can say which computer holds which work. Held in memory only, gone when it disconnects. ## 4. What passes through without being kept Tool requests and results (file paths and contents, commands, output) travel through the relay encrypted in transit, are held in memory only as long as the call lasts, and are never written to storage or logs. The relay reads only the kind of request, the tool name and which computer it is for. ## 5. Logs For each tool call and connection the relay writes one operational line: time, event kind, account and computer identifiers, tool name and outcome. Never arguments or content. These lines are sampled and kept by Cloudflare for up to 3 days. ## 6. Cookies The relay's pages set two cookies, both strictly necessary, both first-party and HttpOnly: - `__Host-rc_owner`: keeps you signed in, for 30 days; - `__Host-rc_login`: holds a sign-in in progress, for 10 minutes. No analytics, advertising or tracking cookies, and the pages load nothing from other sites. ## 7. Service providers - **Cloudflare** hosts the relay and its storage, and processes IP addresses and request metadata to deliver and protect it (for example rate limiting). - **Google** provides direct sign-in. - **Siglet** provides SSO sign-in when enabled and may offer its own upstream authentication methods. Nothing is sold or shared for advertising. ## 8. What the program stores on your computer In its state directory (default `~/.remote-commander`), under your control: - `device.json` and `relay.json` (the relay credential), which identify the computer to the relay; - `grants.json`: the approval scopes you chose to "always allow"; - `oauth.json`: assistants connected to the program directly, and hashes of their refresh tokens; - `usage.json`: the usage counts it reports to the relay; - `memory/`: notes the assistant chose to keep through the `memory` tool (they may include content it read from your files), a one-line record of each command run and file change, and your standing approval decisions. ## 9. Data in your AI assistant Results returned to an assistant are handled from then on by its operator (for example OpenAI or Anthropic) under its own privacy policy, which may include keeping them in chat history or memory. ## 10. How long - Account, computers, usage counts and security events: while the account exists. - Assistant credentials: until they expire (30 days without use) or you revoke the computer or the connection. - Sign-in in progress: 10 minutes. Logs: up to 3 days. ## 11. Your control - See and revoke your computers at `https://rc.rentaicoder.com`; "Revoke all" disconnects every one of them. - Disconnect the app in your assistant's settings. - To get a copy of what the relay holds about you, or to delete your account and everything linked to it, write to the contact below from the e-mail of the account. Deletion is done within 30 days. - On your computer, stop the program or delete its state directory. ## 12. Children RemoteCommander is a developer tool and is not directed at children under 16. ## 13. Changes This policy may be updated; the effective date above changes with each revision. ## 14. Contact Privacy questions and requests: vu.minh.quang@outlook.com