Still Need Help?
If you couldn't find the answer to your question in our FAQ, we're here to help. The Trezor community and support team are available through multiple channels.
Community Support
Join thousands of Trezor users in our community forums where experienced users and Trezor team members help answer questions and share knowledge. Our community is friendly, active, and always willing to help newcomers.
- Reddit: r/TREZOR - Active community with quick responses
- Discord: Real-time chat with other Trezor users
- GitHub: Technical discussions and issue tracking
- Telegram: Community groups in multiple languages
Official Support Channels
For official support from the Trezor team, you can submit a support ticket through the Trezor website. The support team typically responds within 24-48 hours, though response times may be longer during high-volume periods.
Important Security Notice
Trezor support will NEVER ask for your recovery seed, PIN, or passphrase. If anyone claiming to be from Trezor support asks for this information, it's a scam. Always verify you're on the official Trezor website before submitting any information.
Additional Resources
- Knowledge Base: Comprehensive articles covering all aspects of Trezor products and services
- Video Tutorials: Step-by-step video guides for common tasks and troubleshooting
- Blog: Latest news, updates, and security advisories
- Developer Documentation: Technical documentation for developers building on Trezor
Reporting Security Issues
If you've discovered a security vulnerability in Trezor Bridge or any Trezor product, please report it responsibly through our security disclosure program. Do not post security vulnerabilities publicly until they have been addressed.
Security researchers who report valid vulnerabilities may be eligible for rewards through our bug bounty program. Visit the Trezor website for more information about responsible disclosure and our security program.
Contributing to Documentation
Trezor Bridge is open-source software, and we welcome contributions from the community. If you've found an error in our documentation or would like to suggest improvements, you can submit a pull request on our GitHub repository.
Contributing to documentation is a great way to help other users and give back to the community. Whether it's fixing a typo, clarifying unclear instructions, or adding new troubleshooting guides, every contribution is valuable.