About this guide

An independent guide, and honest about what that means

This site explains how the Trezor Suite desktop and web app works: what it does, how its security model holds together, how to set a wallet up carefully and how to keep a portfolio readable over time. It is written for people who own or are about to own a hardware wallet and want the reasoning, not the marketing.

Last reviewed: September 2026

Desk with a laptop and notebook, the setting in which these guides are written and checked

What this site is

An independent editorial resource about the Trezor Suite application and the hardware wallet it pairs with. The pages here cover the practical ground: what the desktop and web versions do differently, how accounts, labels and history are organised, how fees and coin control work, how the security model behaves under realistic threats, and what a careful setup looks like from unboxing to a first small test transaction.

Every page is written to be readable on a phone, to load as plain HTML with no scripts required for the content, and to answer the question a reader arrived with before suggesting anywhere else to go.

What it is not

  • Not the maker's site. This guide is not affiliated with, operated by or endorsed by the wallet's manufacturer. Product names and trademarks belong to their owners. Only the manufacturer's own channels can tell you what its software officially does, and its published documentation always outranks a third-party page.
  • Not software. Nothing here is a download, an installer, a wallet, an app or a support channel. If any page claiming to be this one offers you a file to run, it is not ours.
  • Not financial advice. Tax, investment and legal decisions depend on your circumstances and jurisdiction. Talk to a qualified accountant or lawyer about anything with those consequences.
  • Not support. There is no help desk behind this site, and no one here will ever contact you about your funds. Treat any such message as an impersonation.

How pages are researched

Pages are written from the manufacturer's own published documentation and release notes, from the behaviour of the desktop and web applications as shipped, and from the public technical record around hardware wallets — standards, audits and known classes of attack. Where a claim depends on something that changes often, such as supported assets or provider availability, the page says so rather than asserting a permanent fact.

Each page carries a review date. Content is revisited when the application changes materially, when a security issue in the wider ecosystem changes the advice, and when a reader points out a mistake.

What each type of statement is based on
Statement Basis
What a feature does Manufacturer documentation and the app's own interface
How the security model holds Published design documentation, audits and known attack classes
Setup and everyday practice Conventional wallet practice, with the reasoning stated

How it is funded

This is an informational site. It does not sell the hardware, does not take custody of anything, and does not ask for payment, account details or recovery words. Where a page mentions third-party buy, sell or swap providers, that is description, not an invitation: those services have their own terms, fees and identity checks, and the privacy trade-off that comes with them is stated plainly rather than smoothed over.

Our safety policy

Price of entry to writing about wallets is a clear rule, and it is the same on every page here:

  • Recovery words are entered on the device and nowhere else — no form, chat or page.
  • No one here requests a PIN, a passphrase, or remote access to any computer.
  • Downloads always come from the manufacturer's own published channels, never a mirror or a link in a message.
  • Any page, ad, email, pop-up or phone call asking for those things is an attempt at theft, however official it looks.

If you take one thing from this site: your recovery words are the funds. Anyone who has them has your money, and anyone who asks for them is an attacker — there is no legitimate exception.

Corrections and reviews

A guide that quietly keeps its mistakes is worse than no guide. If a page is wrong — out of date on a feature, unclear about a risk, or stating something the documentation contradicts — it is corrected rather than patched over with vaguer wording. Pages are re-read as the application updates, and the review date at the top of each page reflects the last pass.

Where a topic genuinely depends on your situation, the page says so and points at the person who can answer it properly: an accountant for tax, a lawyer for legal exposure, the manufacturer's own documentation for what its software officially supports.

Start reading

Related pages