Recognize Phishing and Impersonation
Fraudsters may copy familiar logos, page layouts or business names to persuade visitors to disclose passwords, verification codes or banking information. A polished appearance alone does not establish authenticity.
Check the complete domain and independently verify support contact details. Treat unexpected requests for urgency, secrecy or upfront payments as warning signs.
Essential Security Practices
- Use a unique password for each account and enable multi-factor authentication if available.
- Keep devices and browsers up to date.
- Avoid sending personal documents through informal chat channels.
- Do not share OTPs, recovery codes or credentials.
- Review account activity and report unexpected changes through verified channels.
If You Suspect Fraud
Stop interaction
Do not click further links or make payments to a suspicious contact.
Secure accounts
Change affected passwords using a verified website and review other accounts using the same credentials.
Contact providers
Use official support details to report suspicious activity or payment issues.
Preserve evidence
Keep transaction references, screenshots and messages for a legitimate complaint.
Privacy Is Part of Security
Review how a service handles data collection, retention, account closure, third-party sharing and breaches. See the privacy information page for a publication-ready checklist.
Frequently Asked Questions
Should I share a login OTP with support?
No. Verification codes should be kept private.
Is a HTTPS padlock enough to prove a website is genuine?
No. HTTPS encrypts a connection but does not independently prove business legitimacy.