Non-custodial boundary
Users control external wallets; TVK Wallet never requests seed phrases or private keys.
Security
Defence in depth, described without impossible promises.
Technical controls, safer flows and documented responsibilities keep the custody boundary clear.
Pre-action context
Supported flows show recipient, network and transaction details before approval.
Session discipline
Visible connection state and timeout controls reduce forgotten-session risk.
Edition governance
Buyer modules and identity use controlled configuration, not uncontrolled forks.
Deployment controls
HTTPS, restrictive headers, scoped secrets and domain ownership are handover gates.
Shared responsibility
Security also depends on the buyer.
The licensed customer controls production accounts, legal permissions, support and incident response.
- Keep keys and API secrets out of source control.
- Use buyer-controlled accounts and domains.
- Complete acceptance testing before launch.
- Maintain privacy, regulatory and support processes.
Review security during buyer acceptance.
The product boundary is included in the commercial and technical fit review.