Legal
Account, marketplace, payment, content, enforcement, and dispute rules for using RSBazaar.
RSBazaar was an independent player-to-player marketplace for OSRS and RS3 digital goods and services. Users could buy and sell gold, items, accounts, auctions, boosting quotes, gold swap listings, and VIP item exchange listings where the product flow allowed it.
RSBazaar was not Jagex, was not affiliated with Jagex, and did not guarantee that a game publisher would allow any third-party trade. Users remained responsible for understanding the rules and risks of the game they used.
Users had to provide accurate account information and keep their email secure. Sellers could be required to complete seller verification, KYC, business information, role review, or additional risk checks before listing, withdrawing, quoting boosting jobs, or using higher-risk tools.
Fake identities, stolen payment instruments, duplicate accounts used to avoid restrictions, and another person's account without permission were prohibited. Payment partners could require legal names, company names, cardholder details, sanctions screening, fraud checks, and transaction monitoring.
Sellers had to list the correct game, category, product, stock, delivery time, account details, price, images, restrictions, and service scope. Manual-delivery products used the delivery promise shown at listing or checkout. Account listings used automated account-delivery semantics where the product flow supported it.
Misleading or copied listings, prohibited content, fake stock, bait-and-switch pricing, feedback farming, order farming, off-platform payment pressure, and attempts to bypass fees or verification could result in listing removal, hidden feedback, withdrawal restriction, suspension, or ban.
Checkout applied the RSBazaar wallet first where available. Any remaining balance could be paid with the payment method shown in the flow, such as crypto or card. Skrill, Airwallex-style rails, bank rails, or additional methods appeared only when enabled for the user's account, region, and risk profile.
Minimum listing, checkout, and deposit floors were enforced server-side. Crypto invoices, card payments, hosted payment pages, and processor records could have their own fees, confirmations, reversals, and compliance rules.
Seller marketplace fees depended on seller level, game, product category, and set-priced versus auction sale type. Seller level was based on recent sales, order count, and positive feedback share. The live listing, seller dashboard, and checkout screens were authoritative if public help text lagged behind.
Seller withdrawals were crypto-first where enabled and subject to minimums, fees, sanctions and risk checks, wallet holds, payout locks, and review. RSBazaar could delay, reject, or reverse withdrawals when fraud, abuse, disputes, chargebacks, sanctions, or account restrictions required it.
Buyers were expected to confirm receipt only after verifying the delivered product. Standard disputes were generally available before an order reached finality. After buyer confirmation, auto-completion, refund, cancellation, closure, or dispute resolution, normal standard dispute options could close.
Account purchases could have separate account-protection windows shown on the order page. Gold swap was a direct in-game exchange between users; RSBazaar did not take custody of either side's swap gold.
Users were directed to order chat, dispute tools, Live support, or Support for issues, with order IDs, payment references, screenshots, delivery proof, and timestamps. Threats, harassment, doxing, and duplicate reports for the same issue were prohibited.
Refunds depended on order state, payment method, wallet state, processor rules, network confirmations, and dispute evidence. Card issuers, crypto providers, Skrill, Airwallex-style rails, and banks could have independent dispute or chargeback rules. Abusive chargebacks, fake disputes, stolen funds, or money-laundering patterns could result in account restriction and reporting to payment partners where required.
RSBazaar could not be used for illegal goods or services, stolen accounts, stolen funds, malware, phishing, identity theft, sanctions evasion, money laundering, terrorism financing, harassment, hate, threats, sexual exploitation, fraud, marketplace manipulation, or anything a payment partner or law required the service to restrict.
RSBazaar could block a transaction, hold funds, request more information, restrict a rail, remove content, suspend an account, or preserve records for safety, compliance, chargeback defence, or legal process.
Donations were supporter features funded from onsite balance where implemented. Donor rank, loyalty visuals, highlights, seller levels, and profile badges were product features, not investment products or guaranteed business outcomes. Feedback had to reflect real order experience. Staff could hide fake, abusive, farmed, coerced, or policy-violating feedback while preserving the audit record.
Support requests belonged at Support. Legal, privacy, rights-holder, and compliance notices belonged at legal@rsbazaar.org. Urgent platform operations belonged at admin@rsbazaar.org.
Passwords, private keys, full card details, one-time codes, and recovery codes could not be sent by email, chat, or Discord.
RSBazaar could update these terms, help articles, pricing disclosures, payment availability, product flows, and safety rules. Rules could be enforced using evidence, account history, risk signals, provider requirements, and staff judgement. Mandatory legal rights were not excluded.
Published versions are immutable. A rollback creates a new version.
RSBazaar contact entity
Use the narrowest inbox for the issue. Do not send passwords, recovery codes, private keys, one-time codes, or full card details by email.
