RelayBack to home

Legal / Relay

Privacy policy

What information Relay handles, why we use it, and the choices available to you.

Draft updated

Draft for review. This document is not yet effective. Relay’s legal owner, contact details, and operating practices must be confirmed before publication.

1. About this policy

This policy describes how Relay handles personal information when you visit our website or use our web and desktop apps. It covers information handled by Relay. Services you choose to use with Relay have their own privacy policies.

2. Information we collect

When you create an account with email and password, we process your email address and store a hashed password. If you choose Google or GitHub sign-in, we receive an account identifier and the profile details the provider supplies, such as your name, email address, and profile image. We do not receive your Google or GitHub password.

We store account and session records to keep you signed in. Our hosting and infrastructure providers may process technical information, such as IP addresses, browser details, request times, and error logs, when you connect to the service. If you contact us, we receive the information you choose to include in your message.

3. How we use information

We use information to create and manage accounts, authenticate sign-ins, provide the service, respond to requests, diagnose problems, prevent misuse, and meet legal obligations. Where applicable law requires a legal basis, we rely on providing the service you request, our legitimate interests in maintaining a secure and reliable service, legal obligations, or your consent when required.

4. Cookies and local storage

Relay uses local storage in the product app and desktop app to retain sign-in credentials for your session. Clearing this storage can sign you out. External sign-in providers may use cookies on their own sites; their policies explain those uses.

5. When information is shared

We use service providers to operate Relay, including Vercel for website hosting and Convex for account data and authentication. If you choose Google or GitHub sign-in, that provider processes your sign-in under its own terms and privacy policy.

Information may also be disclosed when required by law, to protect people or the service from harm, or as part of a merger or transfer of the business, subject to applicable privacy requirements. Providers may process information in countries other than your own. Where required, transfers must use safeguards recognized by applicable law.

6. Retention and security

We retain information for as long as needed to provide your account and the service, address security issues, resolve disputes, and meet legal obligations. Retention depends on the type of information and why it is needed; backup and log records may remain for a limited period after active records are removed. No method of storage or transmission is completely secure.

7. Your rights and choices

Depending on where you live, you may have rights to access, correct, delete, or obtain a copy of your information, or to object to or restrict certain processing. Where processing relies on consent, you may withdraw that consent. You may also have the right to complain to your local data protection authority.

You can sign out and manage Relay’s access through your Google or GitHub account settings. Revoking provider access does not itself delete your Relay account. We may need to verify your identity before handling a privacy request.

8. Updates and contact

We will post changes to this policy here and update its date. For material changes, we will provide additional notice when required. Please also read our Terms of service.

Relay’s legal owner and a contact address for privacy requests will be added before this policy takes effect.