Security and Privacy
Essentials uses multiple layers of protection to keep your keys, identity, and funds safe. Some protections are automatic; others you can configure.
Master Password
When you create your first identity in Essentials, you set a master password. This password:
- Protects all stored wallet passwords and DID credentials on the device
- Is required to unlock the password database when it has been locked
- Is per-identity -- each DID session has its own sandboxed password storage
You can change your master password at any time from the security settings. If you change it, the entire password database is re-encrypted with the new password.
There is no way to recover a forgotten master password. If you lose it, you can still restore your wallet from your recovery phrase on a fresh install, but any locally stored credentials that were not backed up will be lost.
Biometric Unlock
Instead of typing your master password every time, you can enable biometric authentication:
- Fingerprint (Touch ID on iOS, fingerprint sensor on Android)
- Face recognition (Face ID on iOS, face unlock on Android)
When biometrics are enabled, Essentials uses them to unlock the password database and authorize transactions. The master password is encrypted and stored securely by the device's biometric hardware. If biometric authentication fails or is unavailable (for example, after too many failed attempts), Essentials falls back to the master password.
Root and Jailbreak Detection
When Essentials starts on a rooted Android device or a jailbroken iOS device, it displays a warning explaining that a modified device may expose your keys to other applications. You can acknowledge the warning and continue using the app, but the risk is yours to accept.
Screen Capture Blocking
Essentials can block screenshots and screen recordings to prevent sensitive information (such as your recovery phrase or private keys) from being captured. This setting is off by default and can be enabled in the privacy settings.
Screen capture blocking is available on Android only. iOS does not support app-level screenshot or screen recording prevention.
Transaction Review
Every transaction, message signing, or credential request goes through a confirmation screen before anything is signed. The dApp or internal flow is paused while you review the details. Nothing is signed without your explicit approval.
This applies to:
- Token transfers
- Smart contract interactions from the dApp browser
- DID credential sharing requests
- WalletConnect signing requests
- Multi-sig transaction approvals
Developer Mode
A Developer mode toggle in Settings enables access to developer tools and debug options. This is intended for advanced users and app developers. When you disable developer mode, it automatically turns off related features such as screen capture permissions and log collection.
Developer mode is separate from "core developer mode," which is for Essentials contributors only and is not visible in the normal settings UI.
Settings Visibility by Wallet Mode
Most settings (Language, Privacy, Wallet Mode, Change password, About, Developer mode) are available in both modes. Two settings are only visible in Advanced mode:
| Setting | Lite Mode | Advanced Mode |
|---|---|---|
| WalletConnect sessions | Hidden | Yes |
| Startup screen | Hidden | Yes |
See Home Screen & Navigation for details on Wallet Mode.
Privacy Settings Overview
The Privacy section in Settings contains several important toggles beyond the security features described above:
| Setting | Default | Description |
|---|---|---|
| Built-in browser | Android: on, iOS: off | Controls whether dApps open inside Essentials or in your external browser. See dApp Browser. |
| Hive data sync | Off | When enabled, Essentials periodically syncs data with your Hive vault in the background. See Hive Vault. |
| Credential toolbox stats | On | Sends anonymous usage statistics to help improve the app |
| Elastos API provider | Default | Lets you select which Elastos API endpoints Essentials uses for blockchain data |
How Keys Are Stored (technical detail)
Your private keys and recovery phrases are encrypted at rest using AES encryption with your pay password. They are decrypted only in memory during signing operations and are never written to logs or analytics. When a signing operation completes, the decrypted material is discarded from memory.
The DID store password (which protects your identity keys) is auto-generated and stored inside the password manager, which is itself locked behind your master password or biometrics. You never see or manage the DID store password directly.