Local-First & Private
All communication with your hardware wallet stays local to your machine. No account, no cloud keys, and no telemetry unless you opt in. We prioritize transparency and decisive user consent.
bridge.trezorconnect.net provides a simple, privacy-first connection layer between your Trezor hardware wallet and web-based dapps or services. Designed for clarity and safety: one-click pairing, explicit session controls, and transparent local-only communication. Keep your keys offline — we handle the connection.
Note: This project is an independent bridge implementation. It is not an official product of Trezor / SatoshiLabs. Always verify firmware and device prompts on your hardware wallet.
All communication with your hardware wallet stays local to your machine. No account, no cloud keys, and no telemetry unless you opt in. We prioritize transparency and decisive user consent.
Each connection shows a clear summary of requested actions. Approve device operations directly on your hardware wallet — never through the browser alone. Revoke sessions anytime.
Simple JSON-RPC style API for web apps and dapps. Lightweight, well-documented endpoints, and example integrations so developers can connect without compromising user privacy.
Because approvals happen on the hardware device itself, even compromised browsers cannot sign transactions without your explicit consent.
No. This bridge is an independent connection layer designed to be compatible with Trezor hardware. It is not produced or endorsed by Trezor / SatoshiLabs. Verify device prompts and firmware through official channels.
No. Keys remain on your hardware wallet. The bridge relays requests locally and does not store private keys or broadcast signed transactions unless you choose to share them with a selected web app.
Stop the local bridge service, disconnect the device, or revoke active sessions from the bridge UI. Sessions are short-lived by default to minimize lingering access.