Skip to Content
Unrest LauncherPrivacy and security

Privacy and security

This page states what the launcher’s open beta does to protect an installation, and what it leaves out. It lists only what the launcher’s source and release process establish.

What the open beta omits

The open beta is a launcher-only build. These parts of the earlier private prototype are compiled out of it, so the code is not in the app you install:

  • Chat and its user interface.
  • Message history and the history search worker.
  • The encrypted vault and its passphrase handling.

The launcher package also does not contain Python, language models, archives, relay services, AgentLoop, RecompArch, GameGen, game ROMs or datasets. Products are separate downloads that you start yourself.

Two signing keys

The launcher trusts exactly two public keys. Both are built into the launcher when it is made. Neither can be changed by a web page, a setting or a download.

KeyProtects
Updater keyUpdates of the launcher itself.
Product keyThe product archives the launcher installs, such as GameGen.

The matching private keys are held only as secrets of the release process. A launcher built without a key does nothing in that area: with no updater key it never checks for updates, and with no product key it installs nothing.

Because the keys are built in, they cannot be replaced on an installed launcher. If a key ever had to change, you would install a new launcher.

What is checked before anything is installed

DownloadChecks
A product archiveHTTPS address in the Unrest releases repository; exact size; SHA-256 hash; Minisign signature. All before unpacking. Then the archive’s contents.
A launcher updateHTTPS address in the Unrest releases repository; Minisign signature; the version named inside the signature. All before the app is changed.

A hash is an integrity check, not proof of origin. The launcher always requires the signature as well. The details are on Install GameGen and Updates.

What the launcher’s window cannot do

The launcher’s interface asks the native part of the app to act by product name only: recomparch, agentloop, gamegen or awaken. It cannot supply a download address, a file path, a version, a key or program arguments. Download addresses, checks and install paths are owned by the native part.

Error text from the network is cleaned up before it is shown, so an error message does not carry raw server output.

Network use

WhenWhat the launcher contacts
30 seconds after start, then every six hoursThe beta channel file on the releases page, to look for a launcher update. Signed builds only.
When you choose Check for launcher updatesThe same file.
When you choose Install launcher updateThe update file of that version’s release.
When you choose Install or Update on a productThe product archive on the releases page. No credentials are sent.
When you use AccountThe Unrest account service, to sign you in.

The product artwork is bundled with the launcher, so showing the library needs no network request.

Your account

Signing in is separate from installing: the launcher installs and starts products by name and does not pass an account claim to the installer. The launcher keeps your account session in the operating system’s credential store, not in a plain file.

What is not protected yet

  • Operating-system signing. The Windows installer is not signed for Windows yet, so SmartScreen warns on first open. Whether the macOS apps are signed and notarized by Apple can differ between releases: see the download page for the current release. The launcher’s own signature checks are separate from this and are in place.
  • No uninstall or cleanup. Every installed version stays on disk.
  • No protection from another program running as you. The launcher’s file checks guard against a damaged or swapped download. They are not a defence against malicious software already running under your user account.
  • Not verified end to end. Installing GameGen and updating the launcher from a published release have not been run yet.

Next steps

Last updated on