Setting Up Notifications — Trezor.io/Start

Step-by-step guide: opt in safely, choose what matters, and keep your device alerts actionable and phishing-proof.

Why Notifications Matter

Security • Updates • Awareness

Notifications are your early-warning system: firmware updates, device connection events, suspicious login attempts (if using Trezor Suite integrations), and important security advisories. They help you act fast and keep your wallet healthy.

Pro tip: enable only the channels you actually check (email you own, and optionally Suite desktop notifications).

Start at Trezor.io/Start

Official only

Begin at the official onboarding URL: trezor.io/start. Follow the in-app prompts during device initialization and opt-in for notifications when prompted — never sign up via unsolicited links or messages.

Trezor will never ask you for your recovery seed via email or link — treat any such request as phishing.

Notification Channels

Email • App • Desktop

Common channels: verified email (recommended), Trezor Suite desktop/browser notifications, and RSS or webhooks for advanced users. Choose secure email (with 2FA) and avoid disposable/shared inboxes for critical alerts.

If you use a team/shared wallet, use a dedicated channel and maintain an internal escalation policy.

How to Enable & Manage Notifications — Step-by-Step

During First-Time Setup (trezor.io/start)

  1. Go to trezor.io/start and follow the guided setup with your connected device.
  2. When prompted about updates or notifications, choose to opt-in and provide a secure email address you control.
  3. Confirm the opt-in via the verification email — this prevents typo signups and ensures only you receive alerts.
Why verify? It proves you control the address and prevents attackers from subscribing you to spoofed channels.

From Trezor Suite (after setup)

  1. Open Trezor Suite (desktop app or suite.trezor.io).
  2. Go to Settings > Notifications (or Preferences depending on Suite version).
  3. Toggle the notification types you want: firmware updates, device connection alerts, critical security advisories, and optional product news.
  4. Choose delivery method per type: email, desktop push, or both.

Fine-Tuning: Make Alerts Actionable

  • Enable only security & firmware alerts on your primary email — less noise = faster reaction.
  • Keep promotional/marketing notifications off for your primary security inbox.
  • Set up desktop notifications on a secure machine (not a public/shared workstation).
  • For teams, set up a monitored incident channel (dedicated email or internal Slack) for firmware/security bulletins.

Verification & Testing

  • After subscribing, confirm you received the verification email and that Suite notifications appear when enabled.
  • Periodically check the notification settings — Suite updates may add new alert categories.
  • If you change your email, re-verify immediately and update any internal escalation lists.

Types of Notifications & What They Mean

Security reminder: Trezor will never ask for your recovery seed or PIN in an email or push notification. If you see that request, treat it as phishing and report it.

Quick FAQ

Q: Can notifications be sent to multiple emails?
A: Trezor's standard flow ties alerts to a single verified address; for teams, use a monitored distribution list or internal forwarding rules with strict access control.

Troubleshooting

Problem: Didn't receive verification email.
Fix: Check spam, verify address entry, allowlist notifications from trezor.io, or try resending from Suite settings.

Checklist

  • Use a private, 2FA-protected email for security alerts.
  • Enable firmware + security advisories; disable low-value marketing.
  • Verify your email and test desktop notifications.
  • Document an internal incident response path for critical alerts.