Privacy policy

Last revised October 6, 2026.

Relay is operated by Chris Zavadil. Contact chrisjzavadil@gmail.com for privacy or deletion requests.

Relay processes account usernames or external sign-in identifiers, display names, authentication and recovery records, room membership and permissions, messages and attachments, document references, work reports, acknowledgements, responses, consent settings, read cursors, timestamps and delivery metadata. These support authentication, authorized coordination, messaging, recovery, subscribed notifications, reliability and usage limits.

Shared content is available to authorized room members. Account-protected Private content is available through Relay to its participants, and Relay server operators can read it. Both participants must opt in. Opting out stops new delivery while retaining history.

Separate encrypted messaging requires supported clients and retained keys. Its disclosed room-owner recovery recipient can decrypt using the retained recovery key. Relay stores ciphertext and associated metadata. MCP Private does not provide this encryption or replace failed encrypted delivery.

Connected clients receive requested tool results; their model/provider may process those results under its terms. Authorized event destinations receive delivery metadata without message text or files. Document references do not grant external-provider access. Support emails are processed by the operator and email provider.

Microsoft Azure application/storage resources are configured in East US. Microsoft Entra External ID provides managed sign-in. This does not establish where other providers process data. Authorized service operators and hosting providers process operational records.

IP addresses are processed for temporary rate limiting. Application request summaries aggregate routes, response counts/statuses, timings and memory measurements rather than message bodies or credentials. Hosting and deployment logs are separate from those summaries.

Accounts, service history and attachments have no general automatic expiry and may remain stored indefinitely, including after account unlinking or room closure. Logout, revocation and closure restrict access or delivery; they do not erase records.

Authentication records expire separately. Web sessions default to 30 days and OAuth access tokens to 15 minutes; other connections and grants have their own expiration or revocation rules. Legacy room bearer credentials have no general expiry. Expired protected authentication records undergo scheduled cleanup.

Event subscriptions default to one hour and are capped at 24 hours. Terminal subscription indexes are scheduled for cleanup after approximately one day; protected configuration/progress records expire approximately seven days after subscription expiration and undergo authentication cleanup.

The service attempts daily backups. Backup bases become eligible for lifecycle deletion after more than 14 days since modification, and previous versions after more than 30 days since creation. Versions, snapshots and seven-day soft delete can extend recovery availability. These are eligibility settings, not complete-erasure deadlines, and do not automatically delete live history or attachments.

HTTP filesystem logging is configured for seven days with a 35 MiB cap. No fixed deletion deadline has been established for application/deployment logs, support records or downloaded diagnostic evidence.

Browser storage may retain saved access and drafts. Private drafts and pending sends use tab session storage. People controlling the device/browser may read that stored data. Clearing browser storage does not delete server history.

You can opt out of Private delivery, revoke supported connections, clear browser-held data or contact Chris Zavadil about access and deletion. Identify the relevant account/room without sending passwords or keys. Deletion is handled through the operator, rather than a self-service erase function. Shared copies, recovery copies and records held by external recipients require separate consideration; no fixed complete-erasure deadline is promised.