Privacy

Privacy Policy

Effective September 16, 2026. This policy covers the hosted ReMCP service at remcp.site. Self-hosted deployments are controlled by their own operators.

Account data

Hosted sign-in is provided by Firebase Authentication using Google or GitHub. ReMCP may receive your authentication user id, email address, email-verification status and display name. These data are used to authenticate you and separate your devices and OAuth grants from other accounts.

Google and GitHub

ReMCP uses Google and GitHub only as sign-in providers through Firebase Authentication. The hosted ReMCP application does not use Google access to read Gmail, Drive, Calendar or Contacts, and it does not use GitHub provider tokens to read repositories or perform GitHub actions.

Device and OAuth metadata

ReMCP stores device identifiers, device names, basic platform metadata, one-way hashes of device credentials, pairing records, OAuth client metadata and one-way hashes of refresh credentials. Raw reusable device credentials are not stored in plaintext by the relay.

Files, commands and tool results

When you invoke an MCP tool, the request and result pass through the relay to the selected device. This can include paths, file contents, command output and process information you asked ReMCP to handle. ReMCP does not intentionally retain MCP tool payloads as product data.

Usage analytics

ReMCP stores tool names, timestamps, device identifiers, success or failure status, and execution duration for your workspace analytics. It does not store tool arguments, file paths, command text, or results in analytics. Records are retained for up to 90 days. Browser sessions expire after 5 days and are revoked when you sign out.

Device usage metrics

The ReMCP client and the local device runtime send this workspace usage metrics: tool names, durations, outcomes, coarse error classes, session counts, and device health samples (uptime, load, memory, and component versions). They never include file paths, file contents, command strings, tool arguments, or tool output — the event schema is a fixed allow-list that has no field for them.

There is no third-party telemetry processor and no separate telemetry endpoint. Metrics travel from the runtime to the agent over the local process boundary, and then over the same authenticated WebSocket the agent already uses, to this ReMCP deployment. There is no install-time ping and no remote feature flags.

Metrics are on by default and can be switched off on the device with remcp telemetry off, which covers both the client and the runtime; the runtime also honours REMCP_RUNTIME_DISABLE_TELEMETRY=1 and "telemetryEnabled": false in its configuration file. Device metrics are retained for up to 30 days.

Use and sharing

Data are used to provide authentication, pairing, OAuth authorization, request routing, abuse prevention, security and reliability. ReMCP does not sell personal information and does not serve advertising. Infrastructure and authentication providers process data only as needed to operate the service.

Retention and control

Pairing codes expire after 10 minutes by default. MCP access tokens expire after 1 hour by default. Refresh credentials expire after 30 days by default and rotate on use. Device records remain until revoked or removed. Hosted Nginx access and error logs rotate daily with 14 rotated copies. Application container logs are limited to three files of at most 50 MB each. You can revoke paired devices from the workspace.

Restricted data

Do not send passwords, MFA or OTP codes, API/private keys, payment-card data, protected health information or government identifiers through ReMCP tool calls.

Security and international processing

ReMCP uses TLS for network transport and one-way hashes for reusable server-side credentials. Internet infrastructure and authentication providers may process data in more than one country. See the Security page for the current model.

Children

ReMCP is a developer and systems-administration tool and is not directed to children under 13.

Changes and requests

Material changes are published at this URL with an updated effective date. Account-data or deletion requests can be made through the Support page.