Skip to content

The distress password

The distress password is an optional second password. If you type it instead of your real one, on the sign-in screen or the app lock, AuraLeaf wipes itself from the device you’re on.

Anyone watching just sees AuraLeaf start fresh, as if it was newly installed.

Someone makes you open AuraLeaf in front of them: at a border, by an abusive partner, or in a theft. You want what’s on the device gone, without a visible fight.

  • Someone copied the device’s storage before the wipe.
  • There is already malware on the device.
  • Someone knows you set a distress password and makes you type the real one.

It’s a last resort, not a replacement for a locked phone.

  • Everything AuraLeaf has on that device: messages, files, keys, and the sign-ins for every account and server on it.
  • The keys are destroyed first, so even if the wipe is interrupted, what’s left can’t be read.
  • Any call ends quietly, and the device signs out. To your server this looks like an ordinary sign-out. Nothing marks it as a distress wipe, and nothing is logged.
  • Your account. Sign in again later with your real password, and you get back what the server holds for you: your encrypted settings, your key backup, and messages others can still read.
  • Files you saved yourself, like downloads and exports.
  • Messages that only existed on that device are gone for good.

Go to Settings › Account › Distress password.

  • The distress password must be different from your real password.
  • You can choose to also sign out all your other devices when it’s used.
  • Nobody can tell from the device or the server whether you’ve set one. Every account carries a decoy, so a real one looks the same.
  • Prompts that double-check your password with the server (like deleting your account) don’t accept the distress password. Use the sign-in screen or the app lock.
  • In a browser: AuraLeaf clears everything it stored, but the browser’s own history and saved passwords are out of its reach. If there’s no network at that moment, the sign-in cookie can stay in the browser.

The full technical description is in DISTRESS-PASSWORD.md in the public app code.