DeepSafe
User Manual
Updates & Announcements
User Manual
Updates & Announcements
  1. Accounts & Teams
  • About DeepSafe
  • Quick Start
    • Core Concepts
    • Account Security Principles
    • Getting Started
  • Using DeepSafe
    • Accounts & Teams
      • Teams & Members
      • Decision Mode
      • Roles & Permissions
      • Account & Security Settings
    • Wallets & Transactions
      • Wallets & Assets
      • Key Shards
      • Sending Assets
      • Receiving Assets
      • Transaction Records
      • Gas Service
    • Security
      • Approval Workbench
      • Address Whitelist
      • Approval Nodes
      • Policy Engine
      • Audit Log
    • Developer
      • API Key Management
  1. Accounts & Teams

Account & Security Settings

Overview#

DeepSafe provides four account security settings covering three points in the workflow: sign-in, app access, and transaction confirmation. They are independent of each other, and we recommend enabling all of them.
All four are located in Security Center in the app.
414a98e33a47418f6be42ba0fa513f31.png

The four settings#

Google Authenticator verification adds two-factor protection at sign-in. Once bound, signing in requires both your account credentials and a verification code.
The Wallet Password unlocks the app and confirms transactions and approvals. It is stored only on your device and is never uploaded to a server.
App Lock, once enabled, requires your Wallet Password or your device's Face ID or fingerprint to open the app.
Biometric Payment, once enabled, lets you confirm payments and approvals with your device's Face ID or fingerprint instead of entering the Wallet Password each time.

Comparison#

ProtectsIf forgotten or lost
Google AuthenticatorSign-inContact DeepSafe through an official channel
Wallet PasswordApp unlock, transactions, approvalsStored on device only and cannot be retrieved; recover the wallet using your recovery phrase
App LockApp access when others handle your deviceUnlock with your Wallet Password or biometrics
Biometric PaymentHow payments and approvals are confirmedDisable it and use the Wallet Password instead
The most important point is that the Wallet Password cannot be retrieved. Because it exists only on your device, DeepSafe cannot reset it. If you forget it, you must recover your wallet using your recovery phrase — which is one of the reasons backing up that phrase is essential.

Sign-in and sessions#

App sign-in uses the credentials from registration, plus a verification code once Google Authenticator is bound.
Web Console sign-in requires scanning a QR code with the app; account credentials alone will not work. After scanning, you select the Team to enter — Teams that have not been activated in the app cannot be opened.
Signing out is at the bottom of the "Me" screen in the app. You will need to sign in again afterward; your local key shard is not lost when you sign out.

Things to note#

Do not install your authenticator app on the same device as DeepSafe. If that device is lost, both layers of protection fail at once.
Before enabling Biometric Payment, confirm that only your own biometric data is enrolled on the device. If someone else's fingerprint or face is stored there, the feature effectively hands them the ability to confirm payments and approvals.
Enable App Lock if your device could be handled by someone else — shared office equipment, devices sent for repair, or use in public places.
Modified at 2026-08-26 02:51:05
Previous
Roles & Permissions
Next
Wallets & Assets
Built with