Relay by Excalibur Interactive

Privacy

Last updated August 25, 2026

Information Relay processes

Relay processes account, workspace, contact, lead, pipeline, email, billing, and public-profile information that users choose to store in the service. When a company connects a third-party service, Relay receives only the information and permissions needed to provide the requested integration.

Google and Gmail data

When a user connects Gmail, Relay requests the Google account email address and permission to send email on that user's behalf. Relay does not request permission to read, modify, or delete the user's Gmail inbox. Relay stores encrypted OAuth access and refresh tokens, the connected email address, and delivery identifiers needed to keep the connection active and send messages initiated by the user or by workflows the user configures.

Relay uses Google user data only to provide and secure the connected Gmail feature. Relay does not sell Google user data, use it for advertising, or allow humans to read it except when necessary for security, legal compliance, or support requested by the user.

Relay's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Meta data

When a company connects Meta, Relay receives the Facebook Pages and lead forms the authorized user makes available, plus leads submitted through forms that the company activates in Relay.

How information is used

Information is used to operate Relay, route leads to the company's selected user and pipeline, run connected workflows, secure the service, process billing, and provide support. Relay does not use one company's connected-service data for another company.

Service providers and retention

Relay uses infrastructure, database, storage, payment, and communications providers to host data and deliver the service. These providers process information only to perform services for Relay. Information is retained while a workspace uses Relay and as needed for security, legal, billing, and operational records. OAuth tokens are removed from Relay when the connected Gmail account is disconnected, subject to limited backup and security retention.

Security

Relay uses administrative, technical, and organizational safeguards designed to protect information, including server-side access controls and encryption of connected Gmail tokens. No method of storage or transmission can be guaranteed to be completely secure.

Choices and contact

A company Owner or Admin can disconnect Gmail or Meta from Relay and request deletion of integration data. Users can also revoke Relay's Google access from their Google Account permissions. For privacy questions or deletion requests, email jkhoury@excaliburinteractive.io. See the data-deletion instructions for the request process and the Terms of Service for service terms.