Privacy Policy

This policy explains how Relay handles personal information when you use our AI workflow automation service at relay.shaad.site. For privacy questions or requests, contact groveworkspace@gmail.com.

When you register, we collect your name, email address, and authentication information. Password-based accounts store a password hash. Google sign-in uses your Google account identifier, email address, and profile information to authenticate and maintain your Relay account. Signing in with Google is separate from authorizing Gmail sending.

Relay uses session cookies to keep you signed in and browser storage for preferences such as your theme. Authentication records support email verification, password recovery, and session management. Information you send in support requests is used to respond to you.

We store workspace details, membership information, workflow definitions, triggers, schedules, settings, and connection references so you can build and operate automations. Workspace data is available through the service to members with the relevant access.

Workflow execution records can include inputs, outputs, status, timestamps, errors, and step history. Depending on your configuration, these records may contain personal information, email recipients and message content, AI prompts and responses, or data returned by external services. We use these records to run workflows, display history, investigate failures, and support the service. Only include information you are authorized to process.

When you connect a third-party service, Relay stores connection details and the credentials needed to carry out your configured actions, such as API keys or OAuth refresh tokens. The Gmail connection stores your Google email address and an encrypted refresh token. It obtains access tokens from Google when needed to send messages. Connections belong to a workspace and may be used by workflows in that workspace; connect only accounts you are authorized to make available for that purpose.

Relay requests https://www.googleapis.com/auth/gmail.send to send email on your behalf, together with OpenID and email identity permissions to identify the connected account. Gmail access is used exclusively for user-authorized email sending, including automatic runs of workflows you configure and enable.

Relay sends the recipient address, subject, and message body supplied by your workflow to the Gmail API. Google returns delivery request metadata, such as message and thread identifiers, which may appear in execution results. Relay does not read Gmail messages, retrieve inbox contents, or request inbox-reading permission.

You control whether to connect Gmail, which workflows use it, and what those workflows send. Review recipients, content, and triggers before enabling automation. You can stop using the connection, disconnect it in Relay, or revoke access through Google as described below.

Relay’s use of information received from Google APIs is subject to the Google API Services User Data Policy, including its Limited Use requirements.

Google user data is used to provide the user-facing authentication and email-sending features you authorize. It is not sold, used for advertising, or used to train general-purpose AI models. Transfers are limited to providing these features, security purposes, applicable legal requirements, or a business transfer with user consent where required by that policy.

Human access to Google user data is limited to your affirmative consent for specific data, necessary security investigations, legal obligations, or aggregated and anonymized internal operations permitted by Google’s policy. These restrictions also apply to data derived from Google user data.

When you configure an AI step, Relay sends the prompts, inputs, and selected context needed for that step to the AI provider you select. Other action steps send the configured data to the connected service or API endpoint. Responses may be stored in workflow execution history and passed to later steps.

Those providers process information under their own terms and privacy policies. Review their data handling and your provider account settings before sending sensitive information. Relay’s Gmail integration does not fetch inbox messages for AI processing. Email content that you supply or generate through an AI workflow is processed according to that workflow’s configuration.

When you upload knowledge-base documents, Relay stores the files and document metadata, extracts text, divides it into chunks, and stores text and numerical embeddings for retrieval-augmented generation (RAG). Document storage uses Supabase Storage. Relay sends document text and retrieval queries to OpenAI to generate embeddings; this processing is separate from the AI provider selected for a workflow.

Relevant retrieved passages may be sent to your selected AI provider as context and included in workflow results. Upload only documents you have permission to use and share with these services. Use the available document and knowledge-base deletion controls to remove content you no longer need.

Relay stores account, workspace, configuration, and execution records in service databases and uploaded files in object storage. Infrastructure and service providers process data as needed to host the service, authenticate users, process documents, and execute the actions you request. Data may be processed in locations where these providers operate.

The application uses password hashing, authentication checks, workspace-scoped access checks, and encryption of stored Gmail refresh tokens. These measures reduce risk but do not guarantee that data will never be accessed, lost, or disclosed without authorization. Keep account access and API credentials secure.

Information may also be disclosed when necessary to comply with applicable legal obligations, address abuse, or protect users and the service, subject to the Google user data restrictions above.

Account, workflow, and execution data can remain stored while used to provide the service and its history features. Retention depends on the data involved, operational needs, and applicable legal obligations. This policy does not promise a fixed retention period or immediate removal from every system or backup.

Disconnect Gmail from the Connections screen to delete the saved Relay connection and its stored credential. This does not itself revoke the authorization at Google. To revoke that authorization, remove Relay from your Google Account connections. Disconnection does not recall emails already sent, delete recipients’ copies, or automatically remove past workflow execution records.

For account deletion or removal of associated personal information, email groveworkspace@gmail.com. We may need to verify your identity and clarify the scope of your request, including shared workspace records. Records subject to legal or legitimate security needs and data held independently by third-party providers may require separate handling.

Depending on applicable law, you may have rights to access, correct, delete, or obtain a copy of personal information, object to or restrict processing, withdraw consent, or raise a concern with a privacy authority. Contact groveworkspace@gmail.com to make a request or ask about available controls. Withdrawing access to a connected service may prevent workflows that depend on it from running.

We may update this policy as Relay changes. The date above identifies the latest revision. Material changes to Google data use require appropriate notice and renewed consent before data is used for a new purpose. For questions about this policy, contact groveworkspace@gmail.com. Our Terms of Service describe the conditions for using Relay.