Report a problem
Write to security@relaix.app with what you found and how to see it. Please keep it private until a fix is out; we'll say when we've read it, keep you posted, and credit you in the changelog if you'd like. Machine-readable: security.txt.
How the app treats access
Servers prove who they are
SSH host keys, and the certificates of RDP desktops, RD Gateways, FTPS servers and web pages, are shown the first time and checked every time after. A changed key stops the connection and says so; nothing is accepted quietly. IT can refuse unknown keys outright.
Secrets stay in the keychain
Passwords and key passphrases live in the system keychain or your password manager, never in Relaix's files or logs. An optional master password encrypts them (Argon2id, AES-256-GCM), and they can lock with the computer or after a while without use.
Remote content is untrusted
Text a server sends can't rename windows freely, put things on your clipboard, or open links without asking. Clipboard sharing with remote desktops is off until you turn it on. RDP runs in its own process, so a crash in it can't take your other sessions down.
Updates are signed
The update feed is signed and bound to its channel and date; a feed that was changed, is older than the last one, or is stale is refused, and each package is checked against it.
It calls nobody
No telemetry, no account, no online license check. The only connection Relaix makes on its own is the update check, which can be turned off.