Support without custody.

Recovery and impersonation

• Nobody from RelayZero will ask for a recovery phrase, PIN, private key, QR packet, or signed transaction.
• A lost recovery phrase cannot be restored by the app, relay, assistant, or repository owner.
• Do not enter recovery words into chat, email, issue trackers, diagnostics, or websites reached through messages.
• If the device or phone number may be compromised, text LOCK immediately. Then open Account → Emergency recovery from a trusted device to disable RelayZero SMS access and permanently revoke the executor on-chain.
• If an on-chain recovery transaction is submitted or uncertain, inspect its transaction hash before doing anything else. RelayZero will not retry it automatically.

Transaction states

• Offline: signed locally but not submitted. Blockchain settlement has not happened.
• Queued: waiting for relay handling. This is not finality.
• Relayed: accepted for processing or observed on the network, but confirmation is still pending.
• Confirmed: the relay observed a successful Robinhood Chain receipt. Independently verify the chain ID, parties, amount, and public transaction hash.
• Failed or nonce conflict: do not blindly retry or sign a replacement. Refresh the pending EVM nonce and decoded fields first.

Safe diagnostic sharing

Use Safety & privacy inside the wallet to export the redacted diagnostic report. It contains only counts, state labels, release/network identity, and explicit disclosure text.

Before sharing any file, inspect it yourself. Never share the encrypted vault, browser storage export, queue envelope, QR chunks, transaction bytes, address book, PIN, or recovery words.

Operational boundary

A deployed aggregate status page exists, but no verified support address, ticket system, privacy-request channel, service-level agreement, or on-call rota is configured. Do not interpret an operational component check as a promise of settlement or recovery.