Sports / Mobile
We built rx660 to keep your account, wallet activity, and support exchanges clear. This policy covers what we collect when you fund through bKash, Nagad, or Upay, how we use it to process your transactions, and the choices available to you under Bangladesh data practices.
rx660 collects the information you provide when opening an account, funding through bKash, Nagad, or Upay, and exploring Cricket Betting Inplay, Blackjack Club, Teen Patti Flare, Football BetMarket, Crash HotSpin, or Sylhet Live Lobby. We store transaction records so you can review deposit and payout history inside your account dashboard. Device and browser data help us keep sessions secure and detect unusual access patterns. We do not share wallet details or betting activity with third parties for marketing; transaction processing stays between you, our payment processor, and the wallet provider. Support tickets and account verification requests remain on file to assist future inquiries and meet record-keeping obligations where applicable. When you discuss access or eligibility, remember availability depends on your local law and eligible regions. Cookie use supports session persistence; you can adjust browser settings to limit tracking, though some features require cookies to function. Data retention follows industry norms: active accounts keep full history, closed accounts retain essential records for the period local regulations may require, then archives are cleared.
This privacy policy governs rx660 account creation, wallet transactions, lobby access, and support exchanges. It does not extend to external wallet apps, social-media platforms you use to share content, or third-party game providers whose titles appear in our catalogue—those entities operate under separate policies.
Covers sign-up details, password management, two-step verification where enabled, and session logs from desktop or mobile browsers accessing rx660.
Includes bKash, Nagad, Upay deposit timestamps, amounts, reference codes, and payout requests visible in your account history; does not govern the wallet provider's own data practices.
Applies to lobby navigation, game-launch activity, and support messages you send through our contact form; does not cover external links or embedded studio content served from provider domains.
Payment processors and game studios process data under their own terms; we share only the minimum required to complete each transaction or launch a table, and you should review those entities' policies separately.
You control how we hold your information. Open your account settings to review stored details—name, contact methods, wallet identifiers—and update them if anything changes. Transaction history remains visible in the deposit and payout logs; export a statement if you need records for personal tracking. To request deletion or correction beyond what the settings panel offers, reach our support team through the contact form or live-chat route published on the site. We aim to action straightforward requests within a reasonable time frame, though legal or security holds may delay full removal. If you close your account, core verification and transaction data stays archived under record-keeping rules, then purges once the retention window ends. Where local data-protection law grants additional rights—access, portability, objection—state your request clearly and we will assess it under the framework that applies to your region.
Log in, navigate to account settings, and check the profile fields and transaction history tabs; every deposit, payout request, and support ticket you opened appears there.
Edit your contact methods or linked wallet identifiers directly in settings; verification steps may repeat if you change sensitive fields like withdrawal destination.
Use the support form or live-chat link to ask how specific data is used, how long we keep it, or whether a third party received any portion of it.
Submit a formal closure request through support; we will deactivate your access, archive essential records as required by regulation, then schedule full deletion once the retention period lapses.
Questions about what we collect, how we share it, or how to exercise your rights go straight to our support team. Use the channels below—each connects to the same team, so pick whichever fits your schedule.
Click the chat icon in the lower corner of any page; an agent will walk you through account settings, explain what data sits in your transaction log, or start a formal request if you want deletion.
Open the support page, fill in your registered details and question, then submit; expect a reply by the contact method you listed, typically within one business day.
Browse the FAQ section for common privacy topics—cookie settings, transaction-log access, account closure steps—before opening a ticket, though the team stands ready for anything not answered there.
rx660 separates account credentials from transaction records, encrypts wallet identifiers in transit, and limits team access to support staff who need it for verification or troubleshooting. Cookies track sessions and preferences; essential cookies keep you logged in, while analytics cookies measure lobby usage so we can adjust navigation. Retention schedules differ by data type: active sessions clear on logout, transaction logs persist while your account stays open, and closed-account archives hold core records for the minimum period local rules demand. If you want to review exactly what sits in our system or request an export, contact support with your registered details and we will compile a summary.
We encrypt bKash, Nagad, Upay references during transmission, store them in access-controlled databases, and never sell wallet or betting history to advertising networks.
Session cookies remember your login, preference cookies save language and layout choices, analytics cookies count page views; adjust your browser to block non-essential ones if you prefer, though login may require re-entry each visit.
Password hashing, optional two-step codes, session timeouts, and device-change alerts work together to keep unauthorized users out; review active sessions in account settings and terminate any you do not recognize.
Active accounts keep full transaction and support history; closed accounts archive essential records for the statutory minimum, then delete them; reach support through the contact form if you need early removal or want confirmation of deletion timing.
We collect your name, contact method, and wallet identifier during sign-up, plus device and browser data when you log in. Transaction records—bKash, Nagad, Upay deposits and payout requests—appear in your account history so you can track every fund movement.
Yes. Log into account settings to review stored profile fields, wallet identifiers, and transaction logs. For a complete export including support tickets and session history, contact our team through the support form with your registered details.
While your account stays active, full deposit and payout history remains visible in the dashboard. After you close the account, we archive core records for the minimum period local regulation requires, then delete them once that window ends.
We share only the reference data payment processors need to complete your bKash, Nagad, or Upay transaction, and game studios receive a session token to launch tables—never your full wallet identifier or betting history. We do not sell activity logs to advertisers or external marketing platforms.
Open account settings to edit contact methods or wallet identifiers directly; verification steps may repeat if you change withdrawal details. To request full account closure and deletion, submit a ticket through the support form; we will deactivate access, archive essential records as required, then schedule final deletion.
Session cookies keep you logged in, preference cookies save language and layout, analytics cookies measure page visits. Essential cookies are required for login; adjust your browser to block analytics and preference cookies if you prefer, though some features may prompt re-entry each visit.