Your keys are not a support ticket.

Start with what the request actually asks

A wallet request should match an action you deliberately began. Check the originating domain, selected account, network, recipient or program, asset, and scope of authorization. A site’s description of an operation as a login, verification, or reward does not replace reading the actual request.

If the purpose is unclear, stop. You are not required to finish a workflow simply because you started it. The approval and phishing checklist explains how to separate connections, signatures, transactions, and permissions.

Keep recovery material out of conversations

Never send a recovery phrase, private key, or secret backup to this website. Do not disclose it to an unsolicited helper, place it in an ordinary screenshot, or enter it into an online checker. A supposed support agent may expose a secret through screen sharing even without asking you to paste it into a chat.

Use the actual wallet publisher’s documented recovery method in an appropriate private environment. A local password, operating-system account, and wallet recovery can protect different layers. The backup planning guide helps make those distinctions explicit.

Verify software through a known route

Begin with the publisher’s independently verified website and check the destination it supplies. Compare identities rather than relying on a familiar icon. Do not install a special repair package or turn off device protection because an unverified message says the action is urgent.

Review the guide for your operating system before installing. Keep the software’s origin and update process understandable so that maintenance does not become another search through unfamiliar download pages.

Match the response to the exposure

Seeing a suspicious page, connecting an account, signing a message, granting an allowance, sending a transaction, and leaking a secret are different events. Record the facts without adding new authorizations. Do not assume one cleanup button or password change resolves every situation.

For common Ethereum token allowances, disconnecting a site is different from revoking on-chain spending authority. A leaked key is a different problem again. Read the relevant publisher’s documentation and use verified assistance if needed; avoid unsolicited recovery offers and demands for release fees.

Make room for a pause

Choose a calm review environment. Open full details on a small screen, compare destinations after copying or scanning, and investigate a transaction’s existing status before trying again. A little preparation makes it easier to notice when a request no longer belongs to the task you intended.

These habits reduce avoidable confusion but do not guarantee the safety of an asset, app, or transaction. This site is educational and cannot recover funds, reverse transfers, certify software, or provide incident-response services.