Trust and safety
Clear boundaries for official checkout, TradeShield, seller verification, account safety, reports, and incident help.
Use the affected secure workflow first so staff receive the right context.
End sessions you do not recognize, change your password, enable 2FA, then contact Support if access or account details changed.
Open account securityStop. Do not pay off-site or confirm receipt. Open the affected order and keep the message, timeline, and evidence there.
Open your ordersUse Report on the exact profile, post, or thread. Choose the closest reason and add only facts staff need to review.
Read reporting guidanceIf someone may still have access to your account, secure it first and open Support. For a vulnerability in RSBazaar itself, email security@rsbazaar.org. Do not access another user's data or continue testing after you can explain the issue safely.
What the public marketplace record can support without revealing private security controls.
Sign in only on rsbazaar.org or rsbazaar.net. RSBazaar.net redirects to the primary site. A longer address that merely contains those words is not an official domain.
Start payment-provider pages from the live checkout instead of links in messages or DMs.
Never share passwords, one-time codes, recovery codes, private keys, seed phrases, session cookies, or full card details.
Zezima can explain safer next steps and link the correct RSBazaar page. Add private evidence only to the affected order or protected report flow, never the AI widget.
Use live public status for service impact and the published policy for data handling.
Use the narrowest route and include a safe reference, not a secret.
