1. Treat verification codes as private

A verification code is usually meant to prove that you control a phone number, email address, or login session. If someone else asks for the code, they may be trying to take over your account. Do not share one-time codes in chat rooms, direct messages, comment sections, or screenshots. A real support process should not require you to publish a private code publicly.

• Read the full message that contains the code before using it.
• Check which service requested the code and why it was sent.
• If you did not request a code, change your password and review recent account activity where possible.

2. Verify links before signing in

Many cryptocurrency scams use lookalike websites, shortened links, fake airdrops, fake KYC forms, or urgent reward messages. Before entering account information, inspect the domain carefully. Do not trust a page just because it uses a logo, a familiar color, or a message that says it is official. Search for official links from inside the official app or recognized official channels whenever possible.

3. Use a password you do not reuse elsewhere

Reusing passwords is risky because a leak from one website can be used to try logging in elsewhere. Use a unique password for accounts connected to your Pi activity, app store account, email account, and any service you use for authentication. A password manager can help you store unique passwords without memorizing every one.

Your email account is especially important because it may be used for recovery, login alerts, or app-store access. Protect it with a strong password and any available two-step verification feature.

4. Keep KYC and wallet information separate

KYC and wallet security are different topics. KYC may involve identity verification through an official flow. Wallet security depends on protecting your passphrase or private recovery information. Do not upload wallet recovery information to a KYC form. Do not send identity documents to someone who says they can speed up KYC approval through a private message.

If you are unsure whether a request is legitimate, stop and verify from an official source before continuing. It is better to wait than to permanently expose sensitive information.

5. Screenshot carefully

Screenshots are useful for support and personal records, but they can reveal more than intended. Before sharing a screenshot, check whether it includes your full name, phone number, email, verification code, account ID, wallet address, QR code, or transaction details. Crop or blur sensitive parts when sharing publicly.