Mobile / Slots
555r2 collects only the account and transaction data needed to run your session, process wallet activity through bKash, Rocket or Upay, and respond to support requests. This policy tells you exactly what we collect, where it goes, and what choices you have — availability of this service depends on your local law and eligible regions.
When you open an account, we collect the registration details you enter — your name, email address, and the mobile number linked to your bKash, Rocket or Upay wallet. During an active session, we record standard browsing signals: pages visited, device type, browser version and connection region. This helps us display the correct lobby layout on your Android screen and route wallet confirmations to the right payment channel. If you contact our support team, the conversation record is stored against your account so follow-up is consistent. We do not sell your personal details to third parties, and we do not share wallet identifiers with studios such as Habanero, PG Soft, Joker or Microgaming — those providers receive only the session tokens needed to load game content. Data collected through your bKash or Rocket transaction is governed jointly by our policy and the respective wallet provider's own terms. We keep account records for as long as your account is open and for the period required under applicable rules. You can ask us to review or correct your records at any time through the support routes listed on this page.
Not every interaction on or around 555r2 falls under this policy. The four areas below clarify what is inside our control and what sits with a separate party. Understanding this boundary helps you know where to direct a question.
Login events, session duration, device fingerprint and any account detail you enter at registration or update in your profile are fully within the scope of this policy. We hold and manage that data directly.
When you move funds through bKash, Rocket or Upay, the transaction data is shared between us and the wallet provider. Both parties' policies apply. We record the transfer reference on our side; the wallet provider controls its own logs.
Game content delivered by Habanero, PG Soft, Joker and Microgaming runs inside our lobby frame, but the session data each studio collects for game-state purposes is governed by their own data practices, not solely ours.
Links to external sites, payment gateway pages or wallet apps leave our environment. Once you navigate away from 555r2, this policy does not apply. We cannot control how external services handle your data.
Your account data is yours to review and correct. Log in and open the account settings page to check the details we hold — name, contact number and linked wallet identifiers. If anything is wrong or out of date, you can update it directly in the profile fields shown there. For details that are not editable in self-service mode, or if you want to understand exactly which records are stored against your account, write to our support team using the live chat or email route listed in the support section below. We will acknowledge the request and tell you what we hold. If you decide to close your account, contact support to start that process; we will explain which records we are required to retain under applicable rules and which can be removed. Access to and correction of your data does not depend on your reason for asking — just reach out through a published channel and we will handle it.
Open account settings after login to see the registration details and wallet identifiers we currently hold for your account.
Update editable fields directly in your profile. For locked fields, contact support and we will make the correction after confirming your identity.
Send a specific question about what data we hold or how it is used to our support team. We will respond through the same channel you used to reach us.
Contact support to begin a closure request. We will outline which records must be retained under applicable rules before completing the process.
If you have a question about data handling, want to correct a record or need to understand how your bKash or Rocket wallet details are stored, the routes below connect you directly to the team that handles account and privacy matters. Use the channel that suits your device — all three are monitored and will log your query against your account for consistent follow-up.
Open the chat widget on any page of 555r2 while you are logged in. Describe your data or privacy question and the agent will access your account record directly.
Send your query to the support email address shown in the Help section of the site. Include your registered mobile number so we can locate your account without delay.
The Help section on 555r2 lists published answers to common account and privacy questions. Check there first — many data queries are resolved without needing to contact the team directly.
We apply access controls so that your account record is readable only by authenticated sessions and the internal team handling your support queries. Cookies on 555r2 are used to keep your session active across pages, remember your lobby position and pass the correct wallet context when you move between the sports and casino sections. You can manage cookie preferences through your browser settings; disabling certain cookies may affect how the lobby loads on your Android device. Wallet identifiers for bKash, Rocket and Upay are stored in encrypted form and are never displayed in full after the initial verification step. Data retention periods follow applicable rules — we do not hold records longer than necessary, and we review stored data periodically.
Your login session is protected by access controls. Only authenticated requests can read your account record. Logging out from shared devices clears the active session token immediately.
We use cookies to hold lobby state, session continuity and wallet routing. Browser-level cookie controls let you limit non-essential cookies, though core session cookies are required for the account to function.
bKash, Rocket and Upay identifiers are stored encrypted. The full wallet number is masked after verification; only the last few digits are shown in your transaction history for reference.
When this policy changes, we post the updated version at 555r2/privacy-policy/ and note the revision date at the top of the page. Continued use of your account after a change is posted means you have seen the update.
These are the questions that come up most often when account holders want to understand how their data is handled. If your question is not covered here, use the live chat or email route listed in the support section above.
We collect the name, email address and mobile number you enter at registration, plus the wallet identifier you link for bKash, Rocket or Upay transactions. During sessions we also record device type, browser version and connection region to serve the correct lobby layout.
Yes. Wallet identifiers are stored in encrypted form after the initial verification step. Only the last few digits appear in your transaction history. Neither the full number nor the wallet PIN is accessible to support agents or passed to game studios.
Log in and open the account settings page to review your stored registration details and linked wallet information. For a fuller picture of records held against your account, contact support through live chat or email and we will tell you what we have.
Editable fields such as your email address can be updated directly in your profile. For fields that are locked — such as your verified name or linked wallet — contact our support team. We will confirm your identity and make the correction.
We share only the session tokens needed to load game content. Studios such as Habanero, PG Soft, Joker and Microgaming do not receive your personal registration details, wallet identifiers or transaction history.
Contact support to begin the closure process. We will explain which records must be kept under applicable rules and which can be deleted. Records required for compliance are retained for the minimum period only, then removed.