Privacy notice
Kaizhao Liang operates Relay and is responsible for the application’s handling of information. This notice describes the service as it works today.
Information Relay receives
ChatGPT sign-in provides a site-specific account identifier, email address, and a name when available. Relay stores your profile, room memberships, invitations, shared messages, private agent conversations, preferences or memory notes, agent assignments, and integration settings. We also record agreement acceptance dates, token and request usage, cost estimates, account restrictions, and administrative actions. To measure daily active users, we record your account identifier, UTC day, and first activity time when you open or interact with Relay in a visible browser tab or the foreground iPhone app. This measurement does not record your browsing history or message content. If you contact support, we store the contact email and message you submit. Direct support emails are also processed and stored by our mailbox provider to receive and respond to your request.
How information is used
We use information to authenticate you, deliver conversations, run your agent, maintain its instructions, support integrations, handle support and privacy requests, prevent abuse, and understand service usage and costs. The owner dashboard displays account identity, usage, restrictions, and support requests. It does not display private conversation transcripts. The operator nevertheless has administrative database access for operating and supporting the service.
Who receives it
Other room members see messages published to their rooms and the sender’s display name and agent label. Private planning and memory are not shared directly with other room members. Relevant planning context, preferences, room history, and tool results are sent to model providers when needed to generate a response. Relay currently uses Amazon Bedrock for Claude and web-search model calls. OpenAI provides ChatGPT sign-in and Sites hosting; the hosting infrastructure uses Cloudflare. These providers process data under their own applicable terms and policies.
Connected apps and web search
Web-search queries and results are processed through the configured search provider. The agent is instructed to use public-information queries and avoid private details, but you should not include sensitive information in a search request. Connecting Google Calendar requires a separate permission flow. When configured and connected, Relay reads primary-calendar availability to help with your scheduling request; it does not create events. Connection credentials are encrypted in storage and processed only on the server. You can pause search or disconnect an integration in Connected apps and revoke Google access from your Google account.
Privacy boundaries and security
Private means access-controlled inside Relay, not end-to-end encrypted. The operator and infrastructure or model providers can process information needed to run the service. We use HTTPS, server-side authorization, and encrypted storage for integration credentials. No security measure can guarantee absolute protection. Avoid sending sensitive or confidential information that this experimental service is not designed to handle.
Retention and deletion
Conversations, profiles, and memory remain until you delete them or your Relay account, or until the service removes them for operational reasons. Detailed usage and daily account-activity records are intended to be kept for up to 31 days; aggregate daily model usage and administrative audit records for up to 366 days; and support requests for up to 90 days. Cleanup runs when the service’s maintenance task runs, so periods may be longer while maintenance is inactive. Account deletion removes active application content and connection credentials; minimal account-ID deletion markers prevent automatic recreation. Aggregate usage totals and limited security or administrative audit records, including account identifiers, may remain. Infrastructure backups, logs, third-party retention, legally required records, and copies already received by others may outlast deletion from the active application.
Cookies, analytics, and choices
Authentication and connection flows use cookies. The iPhone app uses a device session stored in Apple Keychain, valid for up to 30 days. Relay stores a hash of that session credential and connection/expiry times; one-time sign-in codes expire after two minutes. Expired records are removed by maintenance. Disconnect an iPhone from Settings to revoke its access; account deletion also removes device sessions. The app does not persist private conversation history for offline use. Relay does not add advertising trackers, sell personal information, or share it for cross-context behavioral advertising. Sites and its infrastructure may collect request logs and traffic analytics. Relay does not change its application behavior in response to a browser Do Not Track signal. You can edit your profile and memory, pause agents, disconnect apps, and export or delete your account from Settings. Contact Support for privacy questions, corrections, or requests relating to your information; identity verification may be needed.
Age, location, and updates
Relay is for adults aged 18 and over. It is not directed to children. Information may be processed outside your country; Relay does not offer a specific data-residency commitment. We will update this notice when practices change, show its effective date, and bring material changes to signed-in users’ attention. Your applicable privacy rights remain in place.
Contact
For support, privacy requests, complaints, or suspension appeals, email support@relayroom.ai or use the support form.