It helps prevent account sign-in alone from becoming wallet access. NordBalticum treats an approved wallet device as a separate trust decision, so a new device must complete the appropriate wallet approval or recovery path before it can open the wallet.
Separate from sign-in
Account-scoped approval
Recovery path required
01
A session is not a wallet key
Being signed in proves an account session; it does not automatically authorize the wallet on that installation.
02
Devices are approved deliberately
Additional wallet devices follow an explicit pairing or recovery flow.
03
Revocation has a narrow purpose
Removing a wallet device ends that device's wallet access without redefining the entire custody model.
Why separate account and wallet access
Email or federated sign-in is useful for account continuity, but a self-custody wallet needs a stronger boundary around the material that authorizes transactions. NordBalticum keeps those domains separate.
This means a new session is not silently treated as an approved wallet environment. The wallet checks its own device authorization state before protected wallet operations can continue.
Adding another device
A user can approve another wallet device through a one-time pairing flow or use the defined recovery process. The existing approved environment and fresh wallet confirmation remain part of that decision.
Exact internal signals and defensive thresholds are intentionally not published. The user-facing principle is simple: new wallet access is explicit, scoped and reviewable.
NordBalticum product view
Wallet approval that does not collapse into login
The result is a clearer boundary: account access gets you to NordBalticum; wallet authorization determines whether that device may open the wallet.
Practical flow
What to do next
1
Sign in to your account
Establish the account session on the intended device.
2
Complete wallet approval
Use an approved-device pairing or the documented recovery path.
3
Review active wallet devices
Keep only the devices you recognize and revoke access you no longer need.
Security, in plain English
Controls with defined responsibilities
Distinct trust domains
Session device trust and wallet device authorization do not substitute for one another.
Fresh proof for changes
High-impact device and recovery actions require fresh wallet confirmation.
Account-scoped control
Wallet-device approval belongs to the relevant account rather than a global browser label.
Clear answers
Frequently asked
Does logging in approve my wallet automatically?
No. Account session trust and wallet-device authorization are designed as separate controls.
Can I use more than one wallet device?
Yes, when the additional device completes the supported approval or recovery flow.
What happens when I revoke a wallet device?
That device loses its wallet authorization for the account. Other legitimate approved devices are not meant to be changed by that action.
