# trezor-us-suite Trezor Suite — Crypto Security & Management

Trezor Suite

Secure, private, and intuitive crypto management from the creators of Trezor

What is Trezor Suite?

Trezor Suite is the official desktop and web application for managing your cryptocurrencies with a Trezor hardware wallet. Designed by SatoshiLabs, it combines security, usability, and privacy in a modern, user-friendly interface that empowers users to safely interact with their digital assets.

Whether you're holding Bitcoin, Ethereum, or hundreds of other supported coins, Trezor Suite provides a secure environment to send, receive, trade, and manage your crypto with confidence. It replaces the older Trezor Wallet interface and offers significant upgrades in both functionality and user experience.

Key Features of Trezor Suite

How to Install Trezor Suite

Getting started with Trezor Suite is simple. Follow these steps:

  1. Visit the official Trezor website: trezor.io/trezor-suite
  2. Download the desktop version for Windows, macOS, or Linux.
  3. Install the application by following the installation prompts.
  4. Connect your Trezor device via USB to your computer.
  5. Open Trezor Suite and follow the on-screen instructions to set up or restore your wallet.

Trezor Suite is also available as a web version at suite.trezor.io/web, but for maximum privacy and control, the desktop version is recommended.

Security & Privacy

Trezor Suite is built with security at its core. Unlike browser-based wallets or software wallets that store private keys on your computer, Suite works exclusively with your Trezor hardware wallet, which keeps your keys offline and protected from malware.

Key security benefits include:

Because Suite is open source, anyone can audit the code and verify that it performs as advertised. This transparency builds trust and ensures that there are no hidden backdoors.

Frequently Asked Questions

Do I need a Trezor device to use Suite?

Yes. Trezor Suite is designed to work exclusively with Trezor hardware wallets. Without the device, you won't be able to access any wallet features.

What happens if I lose my Trezor?

If you’ve backed up your recovery seed phrase, you can restore your wallet and all funds on a new Trezor device. It’s critical to store your seed securely and never share it.

Can I use Suite without installing it?

Yes. You can use the web version at suite.trezor.io/web, but it is recommended to use the desktop version for maximum security and privacy.

How often should I update?

It's a good practice to keep both your Trezor firmware and Trezor Suite application up to date to benefit from the latest security improvements and features.

Does Suite track my activity?

No. Trezor Suite respects your privacy. There is no account creation, login, or telemetry. Your data stays on your device.

## Getting started To make it easy for you to get started with GitLab, here's a list of recommended next steps. Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! ## Add your files - [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files - [ ] [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command: ``` cd existing_repo git remote add origin https://gitlab.com/lurdejorto/trezor-us-suite.git git branch -M main git push -uf origin main ``` ## Integrate with your tools - [ ] [Set up project integrations](https://gitlab.com/lurdejorto/trezor-us-suite/-/settings/integrations) ## Collaborate with your team - [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) - [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) - [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) - [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) - [ ] [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/) ## Test and Deploy Use the built-in continuous integration in GitLab. - [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/) - [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) - [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) - [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) - [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) *** # Editing this README When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template. ## Suggestions for a good README Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. ## Name Choose a self-explaining name for your project. ## Description Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. ## Badges On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. ## Visuals Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. ## Installation Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. ## Usage Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. ## Support Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. ## Roadmap If you have ideas for releases in the future, it is a good idea to list them in the README. ## Contributing State if you are open to contributions and what your requirements are for accepting them. For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. ## Authors and acknowledgment Show your appreciation to those who have contributed to the project. ## License For open source projects, say how it is licensed. ## Project status If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.