Sign-in security

Everything on this page lives in Settings → Sign-in security.

Password and Google

You can sign in with a password, with Google, or both. Change password needs your current one. Sign in with Google links a Google account to an existing password account; afterwards either method works. Linking is always an explicit action; Moola never joins accounts just because the email matches.

Two-factor authentication

Set up shows a QR code for an authenticator app and a set of backup codes. After that, each sign-in asks for a six-digit code. Keep the backup codes somewhere safe; each one works once.

The authenticator secret and backup codes are stored encrypted.

Passkeys

Add passkey registers a passkey with your device, browser, or password manager. On the sign-in page, Sign in with a passkey signs you in with no password at all. Moola stores only the public key; the private half never leaves your device.

You can add more than one passkey and remove any of them.

Why a second factor is required for banks

Linking a bank requires an authenticator app or a passkey on the account. The rule protects the data a link makes visible: once a bank is connected, anyone who can sign in can see every transaction. Set one up before you connect, and it stays required for as long as a bank is linked.

Sessions

Signing in creates a session on that device. Changing or resetting your password signs out every other device, and deleting your account ends every session. Connected assistants hold their own tokens; see Connect an assistant to revoke those.