Privacy
26 October 2026This page describes what Omega Relay processes when you use it, who else processes it, how long it is kept and what you control.
Who operates it
Golain Systems Private Limited operates Omega Relay. For a copy of your account data, or to ask for deletion, email [email protected]. Help is at omegarelay.dev/support.
Account
You can register with a name, an email address, and a password. The password passes through Omega Relay to the identity service, Zitadel. Relay does not store the password. Relay stores your subject identifier, email, and display name, and an encrypted copy of the identity tokens for that browser session. Email verification, and a one-time code when the identity service asks for a second factor, are handled there. A password reset email is sent when an account exists for that address.
When Google sign-in is offered, you continue at Google and return here. Google’s sign-in can provide the email, name, and provider account id used to open or link the Relay account. Relay does not receive your Google password.
The browser session cookie lasts 12 hours. Signing out deletes that session row and asks the identity service to end its session. Other sessions and assistant connections are separate. Approving a computer or an assistant starts its own window, up to 30 days, that keeps that access working after you sign out here. A later sign-in or approval can start a new window; it does not extend a current one early.
The computer you connect
Connecting a computer creates or reuses a personal organization for you. Relay stores its identifier, the name you give the computer, and an optional fingerprint string when the installer sends one.
A device certificate and private key are created for the MQTT connection. Relay holds that bundle only until the installer collects it once, then clears it from the enrollment row. The computer keeps what it needs to stay enrolled.
The installer can also receive a status token for that computer, once, inside the same delivery. Relay stores a hash of the token, tied to your account and that computer. The token lets the app report the state of each capability and ask whether Relay currently sees the computer as connected and whether access is paused. It does not authorize any call, and it is not your assistant’s token. It expires. Signing in again in the browser does not mint a replacement. A copy of the token stays on the computer until a confirmed local disconnect clears the local install.
The desktop app reports, for each capability, whether it is ready, being set up, waiting for a step from you, off or unavailable, with small facts such as a version, the name of the Chrome profile you chose or the agent programs it found. Relay stores the latest report for each computer and shows it to you. A report carries no folder paths and no content.
Device capability metadata
The desktop app generates a capability-only inventory profile. It keeps capability names and registered module versions enabled so Relay can discover supported operations and deliver updates. Those reports include the computer and collection time. Optional software, hardware and policy collectors are disabled in that profile.
There is no optional inventory collector switch in the app today. Turning off the entire software inventory path would also prevent required capability discovery. The configured profile does not prove what a running agent has emitted, and it does not delete previously collected reports. Local permission changes, pause and disconnect are not requests to delete those records.
What a call carries
An assistant can use only the capabilities you allowed on the computer and granted to that assistant. When a granted call runs, its arguments are sent through Relay to that computer, which connects to Relay’s own servers in Frankfurt, Germany. The result comes back the same way to the assistant you connected. Relay does not store the arguments of the request. It keeps what the computer returned, which can include a file’s path or name, with the call’s record for up to 30 days, so the assistant that made the call can read it again, and then deletes it. On Pro, an organization can ask support for zero data retention: Relay then holds a result only until the assistant has received it, for an hour at most, and does not keep it with the call’s record. The sections below say what each capability sends and returns.
The assistant’s provider, such as ChatGPT, Claude or Grok, receives those results under its own terms. Disconnecting a computer or an assistant does not delete what that provider already stored.
Files
In the desktop app you choose what Files may reach: your Home folder, the entire disk, or folders you choose. That choice stays on the computer. Relay stores which of the three you chose, not the folder paths. An assistant you gave Files can ask which folders it may read.
A read sends a path or a search query and returns directory listings, search hits or the lines of a text file. An edit sends the new text or a diff for one file. A download sends an HTTPS address, a destination path and the expected checksum, and the computer fetches that address itself.
Terminal
Terminal is optional. The permission stays on your computer and is tied to its enrollment. Commands use your normal user permissions and can access files and the network beyond what you chose for Files.
Command text, working directories, terminal names and terminal input pass through Relay to your computer. Command output and captured terminal contents return the same way to the assistant’s provider. They can include private information.
The computer keeps a private local execution journal containing the signed request and its result, to refuse unsafe repeats. Terminal sessions can remain running after access is removed or Terminal is turned off. Removing access does not erase command history, journal records, terminal output, or anything the provider has already received.
Browser
Browser is optional. It uses the Omega Relay extension for Chrome in one profile you choose, and an assistant reaches only the tabs you share with it. Relay does not export cookies and does not copy the profile.
A call can return the address and title of each shared tab, an outline of a page’s text and controls, and a picture of the tab. Addresses to open, clicks, key presses and typed text pass through Relay to your computer. Pages open in your signed-in profile, so a result can include private information from sites where you are signed in.
Screen & control
Screen & control is optional and applies to the whole computer. It needs the macOS Screen Recording and Accessibility permissions.
A call can return the names and titles of open windows, an outline of what a window or the menus show, and a picture of a window or a display. Clicks, scrolling, key presses and typed text pass through Relay to your computer. An outline or a picture can include anything visible on the screen at that moment.
When a live view is on, video of the screen is sent through Relay’s own real-time service to your own signed-in page. It is not recorded, and the camera and microphone are not used.
Agents
Agents is optional. A call hands a prompt and a working folder to an agent program installed on your computer, such as Codex CLI, Cursor agent CLI, Claude Code CLI or Pi, and returns that program’s output. The program runs with your normal user permissions, with the account you signed it in to, under its own provider’s terms.
Capabilities you add
When you add a capability of your own to a computer, Relay stores its name, a fingerprint of its operations, and your decision to approve or reject it, including which assistant approved it when you let one do so. Calls to it carry the arguments and results its operations define.
Activity
For each call, Relay stores your subject identifier, the assistant connection, the computer, the operation’s name, its status, its request id, and the time. Relay does not store the arguments the assistant sent: the path, page address, command or typed text of the request. What the computer returned is kept with the record for up to 30 days and then deleted. It can include a file’s path or name, file content, command output, page content or a picture. With zero data retention it is not kept with the record. Activity shows these records as counts of actions.
Payments
Pro is paid through Razorpay. Relay keeps the subscription’s identifier, status, number of computers and the end of the paid period. Razorpay holds the payment details under its own terms. Golain Systems Private Limited, the seller, may appear on invoices. See cancellation and refunds.
Cookies and the security check
Cookies are used to keep you signed in, to bind an assistant’s approval screen to your browser, and, when you use Google sign-in, to match that return trip. They are HttpOnly, Secure, and SameSite=Lax. The site does not set an advertising cookie.
- __Host-relay-session is the signed-in session, for 12 hours.
- __Host-oauth-pending is set only while you approve an assistant, for 10 minutes.
- __Host-relay-google is set only while a Google sign-in is in progress, for 10 minutes.
- __Host-relay-pending is set only when Google sign-in still needs email verification or a second factor, for 10 minutes. It holds that step’s reference, not your password.
When the security check is enabled, registration, sign-in, and password recovery load Cloudflare Turnstile from challenges.cloudflare.com. The check result, the site hostname, the action name, and the connecting IP are sent to Cloudflare. The connecting IP is also used to rate-limit requests. Relay stores a hash for that limit.
Who processes it
Omega Relay runs on our own servers in Frankfurt, Germany, and on these services.
- Cloudflare serves the website and runs the Turnstile security check.
- Zitadel, which we host ourselves, holds accounts and passwords. Google takes part only when you use Google sign-in.
- Razorpay takes payments for Pro. It receives what checkout needs, such as your payment details and email. Relay stores the subscription’s status, the number of computers and the end of the paid period, not card details.
- PostHog gives us product analytics: user and organization ids, the choices you make and counts of calls. Never names, email addresses or anything a call carried.
- Mailtrap sends the emails: invitations, address confirmation and password reset.
- LiveKit, which we host ourselves, carries the live view of a screen.
- Uptrace, which we host ourselves, stores traces and metrics of how the service performs. They hold no call arguments or results.
The assistant provider you connect, such as ChatGPT, Claude or Grok, receives the results of the calls it makes. These services can process data in countries other than the one where you use the computer.
How long it is kept
- A browser session lasts 12 hours. An approval in progress lasts 10 minutes.
- An assistant’s access tokens last up to 10 minutes. Its connection lasts 30 days unless you remove it sooner. Refresh tokens rotate, and reuse of a refresh token or an authorization code ends that connection.
- Records of calls (computer, capability, operation, status and time), with what the computer returned for each, are kept 30 days. The audit log of account actions is kept 365 days. Weekly call counts per organization are kept 400 days. Payment event records are kept 90 days.
- With zero data retention, available on Pro on request, what the computer returned for a call is held only until the assistant has received it, in the call’s result or once when it checks for the result, and for an hour at most. It is not stored in the call’s record, in logs or in traces. The record of the call is kept as above.
- A call the computer has not acknowledged can stay queued for 24 hours and may still be delivered. Terminal, file edit, Browser, Screen & control and Agents calls carry a signed authorization that the computer refuses once it is 60 seconds old.
- What an assistant provider received is kept under that provider’s terms.
What pause, disconnect and remove change
Pausing blocks new calls from every assistant, or to one computer. Disconnecting an assistant from a computer, or removing the assistant, blocks its new calls. None of these cancels work that is already queued or running, and none erases history.
Removing a computer from your account deletes its assistant grants, its activity, its capability report and its setup history. Relay’s audit log keeps the operation’s name, status, request id and time of past calls. A removed computer’s certificate is revoked at once.
Disconnect this Mac in the desktop app, after you confirm it, stops the agent and clears local credentials and the local access choices, including a status token kept on that computer. Switch account runs that same local reset and then opens setup. Neither one removes the computer from your account or deletes Relay’s records. If a stop is uncertain, local data stays and the computer is not signed out.
Export and deletion
While signed in you can see your computers, the assistants connected to them, and activity. You can change or remove an assistant’s access, pause access, remove a computer, and sign out, with the limits above.
On the Account page, Download gives you one file with your account details, your organizations and computers, computers shared with you, your assistants, your activity and your calls from the last 30 days.
On the same page you can delete your account after signing in again. Your computers are removed and their certificates revoked at once. Their records are kept for 30 days, so support can restore them on request, and are then scrubbed. Your assistants and sessions end, organizations that only you belong to are deleted, your name leaves the audit log, and your account and identity are deleted at once. Weekly usage counts stay, with nothing about you. A result your assistant provider already stored stays under its own terms. For help, email [email protected] from the account address.