Privacy

Relay keeps short summaries that your AI assistants choose to save about your projects, so another assistant you connect can pick up where you left off.

Relay (relayz.ai) is run by Loom Labs LLC.

What is stored

• Summaries, decisions and next steps that an assistant sends explicitly through the Relay tools, plus files it or you attach to a topic. Relay never reads your chats; it only receives what an assistant passes to a tool call.
• With each save, a label for the assistant that saved it, such as ChatGPT, and the time.
• The email address you sign in with, or your Google account identifier, and which assistant apps you connected.
• If you share a topic, or one of your assistants asks to: the email addresses you share it with or that were asked for, each person's access and whether they accepted, which assistant asked, and a record of each sharing change. Revisions and files also record the email address of the person who saved them, where it is known.
• Pending profile and memory proposals, encrypted until you approve or reject them. Proposals expire after 30 minutes; expired content is cleared on your next account access.
• Technical records needed to run the service: request counts, retry receipts, sign-in sessions and hashed email counters that limit abuse. Hashed identifiers of deleted accounts remain to stop old credentials from reopening them.

Why Relay uses it

• To keep what your assistants save and pass it to the assistants you connect, so you can pick up where you left off.
• To sign you in, keep your account separate from other people’s and check which apps you approved.
• To share a topic with the people you choose, and to email them the invitation.
• To stop abuse, keep Relay running and help you when you ask. To limit requests, Relay uses your IP address in memory and doesn’t save it.

Who receives it

• The assistant apps you connect. What an assistant saves or reads through Relay goes to that app and the company that runs it, under that company’s own terms.
• The people you share a topic with, and the assistants they connect. They can see your email address and what you save in that topic.
• Clerk, which runs Relay’s sign-in.
• Railway, which hosts Relay and stores its data.
• Resend, which sends Relay’s invitation emails.
• Google, if you sign in with Google.
• Loom Labs LLC, for support and abuse handling.

Sign-in provider

Clerk processes your sign-in details, browser sessions and assistant authorization grants. Relay identifies your account by your Clerk user ID and checks your verified email when sharing topics. Your saved topics and files stay in Relay’s storage. Clerk also sees your IP address when you sign in.

Email provider

Resend sends Relay’s topic invitation emails. For each one it receives your email address, the address you share with and the email’s text, which links to Relay’s sign-in page.

Hosting provider

Our hosting provider, Railway, runs the service and keeps its own access logs, which include IP addresses.

Who can see it

You, through the assistants you connect, and the people you share a topic with. You share one topic at a time, with one email address. That person gets access only after accepting the invitation on this website, signed in with that email address, verified by a sign-in code or by Google. Relay emails each person you share with an invitation through its email provider, Resend. The email contains your email address, their address and a link to sign in, not the topic’s name or content. Daily limits on these emails, per sender and per recipient address, or a delivery problem can mean no email goes out; the invitation still appears in Notebook when that person signs in. Relay sends at most 10 invitation emails for you in 24 hours; once you have used them, you can’t share with anyone new until that limit resets. They and their connected assistants can then read the topic's kept history, including revisions from before you shared it, and its files. People who can edit can also save to it and attach files, which count against your account's storage. A connected assistant can also ask to share a topic you own with an email address. Nothing is shared or emailed until you confirm the request on that topic’s page; a request you don’t confirm within 7 days ends, and your assistants can make at most 10 requests in 24 hours.

People you share with can't see your other topics unless you share those too, your profile or memory topics (those can't be shared), or linked topics you haven't shared with them. Removing someone stops future access; it can't recall what their assistant already read. Everyone with access sees your email address as the owner and the email address recorded on each revision. A collaborator's email address stays on the revisions they saved, even after they delete their account.

Saved summaries are labelled untrusted reference data for the assistants that read them; on a shared topic the label also says other people wrote it. Loom Labs LLC can access stored data for support and abuse handling; when at-rest encryption is enabled the summaries are encrypted with a key held outside the database.

How long

Until you delete your account. Updating a topic keeps bounded revision history; overwriting a summary does not erase its earlier revisions. Once a retry receipt is 30 days old, your next save removes it. Hashed identifiers of deleted accounts are kept with no end date. Platform backups are deleted within 30 days.

Your controls

• Download your saved topics, kept history, links, file metadata and pending context proposals as JSON from your account page, including who you share topics with, the topics shared with you, and invitations to your email address that you haven't accepted (their names and owners, not their content).
• Delete your account there; after sign-in cleanup succeeds, Relay removes your summaries, files and connected-assistant records. If cleanup fails, access is blocked and the page asks you to contact Loom Labs LLC to finish deletion. Topics you shared stop being available to the people you shared them with, and your access to topics shared with you ends. Invitations to your verified email address that you haven't accepted or declined end too, so they don't reappear if you sign up again. What you saved or attached in someone else's topic stays there, with your email address. Delete your data shows each step, and what to do if you can’t sign in.
• Share a topic, change someone's access or remove them on that topic's page, and confirm or decline your assistants' share requests there. Leave a topic shared with you on its page.
• Review pending profile and memory changes or restore kept topic revisions. Disconnect an individual assistant in that app's connector settings. Signing out at /account ends only your browser session.

Saved content is what your assistants report. A save can be missed; Relay never claims to capture a whole conversation, and stored content is not used to train models.

The rules for using Relay are in the terms of use.

Questions, export or deletion help: support@relayz.ai.