Scope
Alex Kerss, an individual based in the United Kingdom, operates Relay Console. This policy applies to Relay Console applications, the Relay Console website, Relay accounts, synchronized workspaces, and Marketplace connections. A service that you connect to Relay Console also applies its own privacy policy and terms to its processing.
Data we receive
Account data can include your name, email address, profile image, session and device information, and records needed to secure your account. Workspace data can include agents, teams, messages, attachments, tasks, settings, approvals, connection metadata, and redacted activity records.
In Local Mac mode, Relay Console stores workspace data in its Application Support folder. macOS Keychain stores local credentials. A diagnostic report is sent to Relay Console only when you choose to export and share it.
Google Workspace data
When you connect a Google Workspace application, Relay Console receives the Google account identifiers and OAuth tokens needed for that connection. The permissions you approve can allow Relay Console to access Gmail messages and drafts; Drive files and metadata; Docs, Sheets, and Slides content; Calendar lists and events; Chat spaces and messages; Contacts and People records; and basic Google profile information. The Google consent screen shows the permissions requested for each connection.
Relay Console accesses Google data when you connect an application, select a capability, or ask an assigned agent to complete an operation. Depending on the capability you approve, an agent can search or read content, prepare summaries, create drafts, create or change files, manage calendar events, create Chat messages, or read and change contact records. Relay Console must ask for the applicable permission before it performs an action.
How we use data
Relay Console uses data to provide the feature you select, authenticate your connection, route your request to an assigned agent, show results, enforce approvals and capability limits, maintain redacted activity records, secure the service, and respond to support or legal requests. Relay Console does not use Google Workspace data for advertising, data brokerage, credit decisions, or sale to another party.
Relay Console does not use Google Workspace data to train or improve a generalized artificial-intelligence or machine-learning model. It sends content to your selected agent runtime or model provider only to complete the operation that you requested and approved.
Google API Limited Use
Relay Console's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Storage and security
A server-backed Marketplace connection stores its OAuth tokens in an encrypted credential record. Relay Console uses HTTPS for data sent over public networks and restricts credential access to the service path that performs the authorized operation. OAuth state is short-lived. Relay Console excludes raw credentials from normal application responses, logs, exports, and activity records.
Google content can pass through Relay Console infrastructure and the official Google API or Google-hosted MCP service during an operation. Relay Console stores Google content when you choose to keep it in a message, attachment, artifact, task, or other workspace record. It can also store bounded metadata needed for connection health, approvals, execution results, and security records.
Sharing and human access
Relay Console sends data to Google to access the connected service and to your selected agent runtime or model provider to complete your request. Infrastructure providers can process data for hosting, databases, caching, error monitoring, or transactional email. We use these providers only to supply and secure Relay Console. We can disclose data when the law requires it or when disclosure is necessary to protect users and the service.
Relay Console personnel do not read Google content unless you give specific permission for support, access is necessary to investigate a security or abuse incident, or the law requires access. Relay Console can use anonymized and aggregated service information for internal operations when it cannot identify a user.
Retention, disconnection, and deletion
Relay Console keeps account and workspace records while you use the applicable service or until you delete them. It keeps an active Google OAuth token until you disconnect the connection, revoke access, or the token expires without a valid replacement. Disconnecting denies further Relay Console use and deletes the active stored credential. Relay Console attempts provider revocation when the provider supports it. You can also revoke access from your Google Account connections page.
Revocation stops future access but does not delete content that you chose to store in Relay Console. Use an applicable delete control in Relay Console or request deletion through support. Relay Console can retain redacted security, approval, and audit records when needed to protect the service, resolve disputes, or meet legal duties. Backup copies remain until the applicable backup cycle replaces them. Relay Console does not use retained records for a new purpose.
Your choices
You can decline a Google permission, disconnect a Marketplace application, revoke access in Google, delete applicable workspace content, and request a copy or deletion of data held by Relay Console. A denied permission disables the related capability. Relay Console will ask for new consent before it uses Google data for a new purpose.
Policy changes
We will update the date on this page when this policy changes. We will provide notice and request consent before a material change introduces a new use of Google user data.
Contact
Send privacy questions and data requests to hello@relayconsole.work.