Privacy

How Relay handles information.

This notice summarizes information processed by the Relay application and inquiry forms. Read it together with your written service terms.

Information processed

Information you provide or create.

Account email addresses and password hashes used for access.
Per-account appearance preferences, including display mode and accent color.
Workspace names, team invitations, process steps, templates, implementation tasks, and statuses.
Information customers submit through a private setup link, according to the fields the workspace requests.
Inquiry form name, phone number, company, email, and message. Company and email are included in the stored inquiry message.
Technical request data processed by the hosting environment to operate and protect the service.

Use and sharing

Used to operate Relay and respond to you.

Relay uses account and workspace information to provide sign-in and implementation workflows.
Password recovery uses an email delivery provider to send a one-time recovery link. Recovery tokens are stored as hashes and expire after 30 minutes.
Inquiry submissions are stored in the Relay database. When configured, inquiry details are also sent to the service operator’s messaging destination for follow-up.
After the user consents in the chat panel, Ray sends the question and recent messages in that account’s conversation to the configured external AI service to generate an answer. The service may process this information according to its own terms. Conversation history (up to 50 messages) and the consent record are stored per user account in the Relay database until that user clears the history; clearing also withdraws consent. Relay does not send workspace records or customer implementation data as assistant context.
Relay does not ask customers to submit passwords, payment card data, or other secrets through setup forms.

Storage and access

Service configuration matters.

The application stores workspace and inquiry data in a PostgreSQL database configured by the service operator. The hosting provider, storage region, retention schedule, and access controls depend on the production deployment and are not determined by the application code. The service operator should confirm those details in the written service terms.

Your requests

Manage or delete your account.

Signed-in users can clear their Ray conversation from the chat panel or delete their account in Settings after confirming their password. Deleting the only member of a workspace also deletes that workspace and its customer records. A member leaving a shared workspace does not delete shared records; an owner must transfer ownership to a remaining member. Deletion removes account data from the live database. Protected backups must expire within 30 days; the operator must confirm the hosting provider’s retention and restore procedures before production use. Use the Contact page for other access, correction, or deletion requests and privacy concerns.

Cookies and security

Session access is protected.

The product uses an HTTP-only session cookie with a 14-day expiry; production cookies are marked Secure and SameSite=Strict. Passwords are stored as scrypt hashes. These controls do not remove the need to protect account credentials and customer links.

Questions

Contact Relay.

For privacy questions or requests, use the Contact page. The service operator and applicable privacy requirements should be identified in the written service terms.