Skip to main content

​
Do I need an account?

Choose Login in the header to sign up or sign in. It becomes Account after sign-in. There is no password recovery flow.

​
Connect your signed-in devices

Online devices signed into the same account discover and connect to each other privately. With one other visible device, a chat opens automatically; with several, choose one from Devices. Each browser profile keeps its own device identity. Signing in does not merge identities or share device keys. Concurrent tabs in one profile share an identity; the newest tab takes the connection. Account-only connections require both devices to be online. For offline delivery, pair devices by code or QR first. Blocking and verified-only settings still apply.

​
Save or load settings

  1. Open Account and choose Save settings.
  2. Sign in on the other browser and choose Load settings.
This syncs theme, incoming-file policy, verified-only mode, and the relay preference. Loading reloads the app and clears its in-memory conversations. If another device changed the saved settings, load the newer version before saving again. Messages, files, private keys, pairings, trust records, and advertising consent are not synced.

​
Sign out or delete an account

Sign out clears that browser’s chats, received files, and drafts. It disconnects the browser from its peers and rooms. Signing back in does not restore account-chat history from other devices. To delete an account, open Account → Delete account and confirm your password. This removes saved preferences and signs out connected devices. Files saved outside Evakage and other people’s copies remain.

​
For server operators

Docker enables accounts by default and keeps the database in the account-data volume. Accounts and saved settings survive container replacement; login sessions do not. For local Node development, set ACCOUNTS_DB=./data/accounts.sqlite. Set ACCOUNTS_DB= to disable accounts. The database contains usernames, salted password hashes, and selected settings. It contains no chat, files, or device private keys. Behind an HTTPS reverse proxy, set TRUST_PROXY=1 and preserve the public host header. See configuration and backups.