Security and Destinations

The Security area shows which protections are configured and which actions still require setup. Connected destinations show where supported cashouts can be sent. These are related surfaces, but changing a destination is a separate sensitive action.

Security checklist

• Email verified. Confirms control of the membership email.
• Passkey registered. Adds approval through a trusted device or security key.
• Authenticator 2FA enabled. Adds changing six-digit codes and backup-code recovery.
• Recovery material saved. Confirms that backup codes are stored somewhere private.

Connected destinations

HeartDash may display HandCash, Solana, or another supported destination when that option is available to your account. The dashboard shows the current connection state and any security requirement that must be completed before the destination can be added or changed.

Changing a destination

Review the destination carefully before approving a change. HeartDash may require a passkey, authenticator code, or another verification step. A newly added or changed destination may also be subject to additional review or a temporary protection period.

Unrecognized changes

Stop before sending or cashing out if a passkey, authenticator setup, or destination looks unfamiliar. Do not remove existing security methods in an attempt to fix the issue. Contact support with the masked destination, approximate time, and the alert or status shown in HeartDash.