Relai Privacy Policy (English translation)
The Korean version (https://relai.ruiboss.com/privacy/) is the governing version. This is a translation.
Effective date: 2026-10-25
Ruiboss (the "Operator") processes personal information as described below when providing Relai (the Mac app and the relay server the Operator runs, the "Service"), in accordance with the Personal Information Protection Act of Korea.
This policy applies when you sign up on the Operator's relay server (relai-api.ruiboss.com). Features that run only on your Mac (the same-Mac local relay, conversation history, Claude login profiles) do not send that information to the Operator, and the Operator does not process it.
1. Purposes
The Operator processes personal information only for these purposes:
- Sign-up and verification: sending a code by email to confirm sign-up and new devices.
- Identifying people and devices within an organization and team, and showing them to colleagues in the same organization.
- Relaying messages: holding a message while the recipient's devices are offline, then delivering it.
- Abuse prevention: limiting how many sign-up emails and invite checks can be requested.
- Operations: detecting failures, responding to security incidents, and backup and recovery.
2. Information we process
| Category | Items | How collected |
|---|---|---|
| Required (sign-up) | Email address, user ID, display name, organization and teams, the policy version agreed to and when | Entered in the app |
| Invitation | Who invited you (a relation between user IDs in the same organization, shown only to the inviter and to you) | Recorded automatically when you join with an invite code |
| Required (devices) | Device ID, device public keys (signing and encryption), registration and revocation times | Generated by the app |
| Messages | Sender and recipient addresses, send time, delivery status, encrypted body | Generated during use |
| Published sessions | Name, title and folder name (last path component only) of agent sessions you choose to publish | When you publish |
| Connection | IP address | On connection |
- Message bodies are end-to-end encrypted, from the sending device to the recipient's device keys. The Operator cannot read them.
- IP addresses are kept in server memory only, for rate limiting. They are never written to the database or logs.
- The Operator never collects, transmits or stores credentials for your agent accounts, such as Claude login tokens.
- Your email address is visible to colleagues in the same organization.
3. Retention
| Information | Retention |
|---|---|
| Verification code | 10 minutes. Deleted when entered correctly or after 5 wrong attempts. Only a hash is stored |
| Sign-up token | 30 minutes, deleted on first use (hash only) |
| Sign-up email request log (email, time) | 24 hours (rate limiting) |
| Invite code (hash, plus the invitee's email if one was set) | Until used, or 7 days |
| Account information (email, user ID, display name, organization, teams, inviter, consent record) and device public keys | While you belong to the organization |
| After you leave or are removed from the organization | Your email address, display name, teams, inviter, device encryption keys and consent record are destroyed at that moment. Only your user ID, an HMAC of your email (an irreversible value made with the Operator's secret key), and device IDs with their signing public keys and revocation times are kept while the Service operates: the ID so no one else can take it, the HMAC so you get the same ID back if invited again, and the device IDs and signing keys so an offline device can be verified and told it was removed when it reconnects. Removing your account from one device ("remove account from this device") keeps you in the organization and is not covered here |
| Message body | Deleted as soon as it has been delivered to all of the recipient's devices, or at the sender's deadline (at most 7 days) if that comes first |
| Message header (addresses, time, status) | Deleted at the sender's deadline (at most 7 days) |
| Published session information | Deleted when you unpublish, or when you have no devices left |
| Server logs (user and device IDs only; no email, IP or message bodies) | Up to 2 weeks |
| Backups | Latest 7 on the server (daily); 30 days off-site |
4. Provision to third parties
The Operator does not provide your personal information to third parties. The exceptions are where the law specifically requires it, or where an investigative authority requests it through legal procedure.
5. Processors
| Processor | Task |
|---|---|
| Plus Five Five, Inc. (Resend) | Sending verification code emails |
| Cloudflare, Inc. | Relaying connections to the server (Cloudflare Tunnel) and storing off-site backups (R2) |
6. Transfers abroad
| Recipient | Country | Items | When and how | Purpose | Retention |
|---|---|---|---|---|---|
| Plus Five Five, Inc. (Resend, [email protected]) | United States | Email address, verification code | On each code request, over HTTPS | Sending the code | Per Resend's policy (https://resend.com/legal/privacy-policy) |
| Cloudflare, Inc. ([email protected], DPO [email protected]) | United States (via global data centers) | All traffic to and from the server (IP address, connection metadata, frames including encrypted messages) | On each use, over the network | Relaying connections | Per Cloudflare's policy (https://www.cloudflare.com/privacypolicy/) |
| Cloudflare, Inc. (R2) | Asia-Pacific (R2 location APAC) | Backups of all server-stored information in section 2 | Daily, over HTTPS | Disaster recovery | 30 days |
You agree to these transfers when you agree to this policy at sign-up. If you do not agree, you cannot use the Operator's relay server, but the local features on your Mac remain available.
7. Destruction
- Information is destroyed without delay once its retention period ends or its purpose is fulfilled. Most of section 3 is deleted automatically by the server.
- Electronic records are deleted from the database so that they cannot be restored.
- Information deleted from the server may remain in backups for up to 30 days, until those backups expire.
8. Your rights
- You may ask at any time to access, correct, delete, or stop the processing of your personal information.
- You can change your display name and teams in the app.
- Leaving the organization (in app settings) revokes all of your devices and destroys message bodies waiting for you, along with the information described in section 3.
- You may also ask to delete the user ID, email HMAC, device IDs and signing keys that remain after you leave. After that, you cannot return under the same ID even if invited again.
- For anything else, email the contact in section 10. The Operator will act without delay (within 10 days) and tell you the result.
9. Security measures
- Message bodies between user devices are end-to-end encrypted. Not even the server operator can read them.
- All traffic to the server is encrypted with TLS.
- Verification codes, sign-up tokens, invite codes and organization setup codes are stored only as hashes.
- The server opens no public ports and accepts connections only through a Cloudflare Tunnel on the same machine.
- The server process runs under a dedicated, least-privilege account.
- Server logs never record email addresses, IP addresses, codes or message bodies.
- Sign-up and sending attempts are rate limited.
- Operator accounts use two-factor authentication.
- Off-site backups are separately encrypted by the Operator before upload, and the decryption key is not stored off-site. Backups on the server are readable only by the server's dedicated account.
10. Privacy officer and contact
- Business: Ruiboss
- Privacy officer: Lee Ruo (Representative, Ruiboss)
- Contact: [email protected]
11. Changes
- Changes are announced on this page 7 days before they take effect, or 30 days before for changes unfavorable to you.
- When the policy version changes, you will be asked to agree again when you sign up or add a new device.
- Server location: Republic of Korea (a server managed by the Operator).