Understand alerts and unsubscribe links

Wallet and account · Reference and troubleshooting · Implemented security history and retained unsubscribe flow; not a general notification inbox.

Distinguish saved preferences, durable security events and actual external delivery.

Reviewed: 2026-10-18

Before you start

  • Sign in to read private security history.
  • Unsubscribe requires the original complete valid link, not necessarily app login.

A preference is not delivery evidence

Email alerts in Settings saves a preference. Each notification service must separately support delivery; the preference does not prove an email was sent or reached an inbox. Telegram connection is not configured and sound is not implemented.

The general Notifications account route is unavailable, not an inbox with hidden messages. Use the actual security history in Account or Wallet for its supported recorded events. No event returned is different from a failed history read.

  1. Open Settings, choose the email-alert preference and Save preferences if you want to change it.
  2. Read Saved or the action error; do not assume the preference changed while pending.
  3. Check the relevant service/history for actual event and delivery state. Do not treat absence of email as proof that no financial action occurred.

Read the event and its evidence

Durable in-app security alerts record account/session events and wallet destination or withdrawal activity. Read the event time, current request status and transaction signature when present. The history is bounded, not an exhaustive independent chain audit.

A legacy email record explicitly does not prove inbox delivery. Security notices remain mandatory regardless of the optional alert preference. An acknowledgment or alert does not replace genuine wallet-owner authorization.

For a pending destination request, use Cancel destination request only when offered and check its result. An immediately active destination or completed transfer cannot be assumed reversible through an old alert.

Explicitly confirm an unsubscribe

The retained unsubscribe link concerns launch announcements, not mandatory security notices. Launch marketing signup is retired. Opening the link alone does not confirm unsubscribe; use the explicit Confirm Unsubscribe action.

The full link carries a sensitive fragment, which the page removes from the address bar after reading. A missing/partial link cannot authorize the action. The result is intentionally generic and does not disclose a subscription identity.

  1. Open the original complete unsubscribe link privately; do not paste it into a public report.
  2. Read the page and select Confirm Unsubscribe.
  3. Wait for the result. If the request fails, retry the offered action; if the link is incomplete, return to the original message rather than inventing a token.