Trezor™ Login® | Getting started — Developer Portal

Access your SecureWallet safely. Never share your recovery phrase with anyone.

About secure login & recovery

This page is a design-first demonstration of a secure wallet companion login. Use it as a template for building a safe authentication page that pairs with a hardware device. Below are practical tips and design decisions included in the page content. Read carefully and adapt to your own security and legal requirements.

1) Never collect recovery phrases on the web. A legitimate hardware wallet workflow never asks users to enter their full recovery phrase into a website or a remote service. Recovery phrases should be generated and stored offline by the device, and only used during device recovery in a secure, offline environment.

2) Prefer device-based authentication. Authenticate actions by requesting the user to confirm on their hardware device (e.g., approve a signature or enter a PIN on the device). The web interface should act as a companion that forwards a challenge to the hardware device and verifies the signed response.

3) Use short-lived session tokens & MFA. Keep web sessions short and bound to the device that created them. Add multi-factor steps such as device confirmation, WebAuthn, or time-limited push approval flows.

4) Clear UI & clear warnings. Display explicit warnings about phishing risks, never ask for full recovery phrases, and show recognizable indicators (e.g., verified domain badges) to help users detect fake pages.

5) Accessibility & privacy. Use semantic markup, aria labels, and clear color contrast. Avoid tracking, and do not store sensitive fields in localStorage. Use HTTP-only, secure cookies for session state.

Implementation notes: the form above is intentionally minimal. In a production system, all communications must be encrypted (HTTPS/TLS), server responses validated, and cryptographic actions performed or confirmed by the hardware wallet. Never log unencrypted secrets (PINs, seeds). Consider rate limiting, device lockout policies, and strong telemetry for account recovery abuse detection.

UX note: prefer progressive disclosure — keep the interface simple for users who simply want to unlock their device, and show advanced options (pairing a new device, diagnostic export) only when necessary. Provide easy-to-access support links and human-readable verification steps when sensitive operations are requested.

Security checklist summary: TLS enforced, Content Security Policy, Subresource Integrity for assets, HTTP-only cookies, same-site cookies, strict transport security, server-side session validation, and device-authenticated operations. Treat every UI that touches keys or funds as sensitive — user education + minimal trusted surface area reduce risks.