App / Casino
At 55 rr, we collect and use your information to keep your wallet, payment records, and session history working correctly on every device you carry. This policy covers what data we hold, why we hold it, and what choices you have — access and eligibility depend on your local law and the region from which you connect.
55 rr collects information you provide when you create an account — your contact details, login credentials, and the payment methods you attach, including bKash mobile wallet details and Bank Transfer records. We also collect data generated by your activity: pages you visit, games you open, deposit and withdrawal timestamps, and the device type and browser you use to connect. This data has a clear purpose. We use it to authenticate your account, process transactions through your chosen payment rail, detect unusual access patterns, and keep your session consistent whether you are on Android, iOS, or a desktop browser. We do not sell your personal data to third parties. We share it only where processing a bKash deposit or a Bank Transfer requires it, where a legal obligation applies, or where you give explicit consent. Data we collect is stored securely and retained only as long as your account is active or as required under applicable law. If you close your account, we will remove data that no longer serves a legal or operational purpose within the period set by our retention schedule. Availability of this service and the rights described here depend on your local law and eligible region.
Transaction references for bKash deposits and withdrawals are logged against your account wallet. These records help you verify a transfer and allow our support team to trace a payment if something goes wrong on your end.
When you use Bank Transfer, we retain the transaction reference, amount, and timestamp. This record exists solely to reconcile your account balance and resolve any discrepancy you raise with our support team.
We log the device type, operating system, and browser session that accessed your account. This lets us flag logins from unfamiliar devices and keep your mobile session active without asking you to re-authenticate unnecessarily.
Your registered name, contact details, and verification documents are held to authenticate you at login and satisfy the account verification requirements that apply in your region under local law.
This privacy policy applies specifically to data collected and processed through the 55 rr platform — your account, your wallet activity, and your interactions with the site and its mobile interface. It does not extend to third-party services you access via external links, and it does not govern how payment processors such as bKash or your bank handle data on their own infrastructure. Understanding the boundary helps you know where to direct a question. Use our support route for anything related to your 55 rr account record; contact your payment provider directly for queries about how they process a transaction on their side.
Data collected at login, during your session, and on account settings pages falls inside this policy. This includes your credentials, session token, device fingerprint, and any changes you make to your account profile or notification preferences.
Records of bKash and Bank Transfer activity processed through the 55 rr platform are covered here. The data the payment provider captures on their own system — your bKash account history, for example — is governed by that provider's own privacy terms.
Pages you visit, game sessions you open, and lobby navigation data we collect are within scope. We use this data to improve how the platform works on mobile and to present content relevant to your history, not to share with advertisers.
External links, embedded content from providers, and any service you reach by leaving the 55 rr domain are outside the scope of this policy. Those services operate under their own privacy terms, which we encourage you to read before sharing any information with them.
You have practical choices about the data we hold on your account. You can request a summary of the personal information we have recorded, ask us to correct something that is wrong, or raise a question about how a particular piece of data is being used. For most routine changes — updating your contact details, adjusting notification settings — the fastest path is your account settings page, where the fields are editable without contacting support. For anything that requires us to review records on our side, the support route below handles these requests directly. Where local law in your region grants additional data rights such as portability or erasure, you can raise those through the same contact route. We will acknowledge your request and respond within the period required under applicable law. Note that some records — such as transaction logs tied to a completed bKash deposit — may need to be retained for a legally required period even after you request removal.
You can ask us for a copy of the personal data we hold on your account. Submit your request through the support contact route and we will compile the relevant records for you.
If your registered name, contact number, or email address needs updating, go to your account settings page and edit the relevant field directly. For changes requiring identity verification, contact support.
If you are unsure why a specific piece of data is being held or how it is used, ask us via the support route. We will point you to the relevant section of this policy and explain the processing basis.
Where your local law and eligible region permit it, you can request that we erase data that is no longer necessary. Transaction records tied to regulatory obligations may need to be retained for the period set by applicable law.
For any question about this policy, a request related to your account data, or a concern about how your information is being handled, use the contact routes published on the 55 rr site. We do not handle privacy requests through social media or unofficial channels. Please use the routes below so your request reaches the right team and is tracked correctly.
Open the chat widget from the 55 rr site to speak with a support agent about your account data. Use this route for time-sensitive questions about a specific transaction record or login activity.
Send your data request or privacy question to the support email address listed on the Contact page of the 55 rr site. Include your registered account email so we can locate your record quickly.
The Help Centre on the 55 rr site includes published answers to common account and data questions. Check there first for general policy questions; it may resolve your query without needing to contact the team directly.
Account security and responsible data handling are part of how 55 rr is built, not an afterthought. Your login credentials are stored in hashed form. Your session on mobile or browser is protected by a token that expires after inactivity, so a device left unattended does not stay signed in. When you make a bKash deposit or Bank Transfer, the transaction is processed over an encrypted connection and the reference is logged in your account wallet, not stored in a way that exposes your full payment credentials. We review our data practices when regulations in eligible regions change, and we update this policy to reflect those changes. If a material change affects how we process your information, we will notify you through your registered contact details before the change takes effect.
We use session cookies to keep you signed in across pages during your visit, and analytics cookies to understand how the platform is used on mobile. You can adjust cookie preferences through your browser settings at any time.
Credentials are stored in hashed form and never transmitted in plain text. Sessions expire after a period of inactivity, and our system flags login attempts from devices not previously associated with your account.
We hold your account data while your account is active. Transaction records, including bKash and Bank Transfer logs, are retained for the period required under applicable law and then removed from active systems.
This policy is reviewed and updated when our practices change or when regulations in eligible regions require it. We will contact you at your registered email before any material change takes effect.
These questions cover what we get asked most often about account data, payment records, and your choices under this policy. If your question is not answered here, use the support contact route and we will respond directly.
We collect your name, contact details, login credentials, and any payment method details you add — including your bKash number or Bank Transfer information. We also log device type, browser session, and account activity to authenticate you and keep your session secure.
Yes. Submit a data access request through the support email listed on the Contact page. Include your registered account email and we will compile the records we hold for you and send them within the period required by applicable law in your region.
Transaction records are retained for the period required under applicable law and then removed from active systems. The exact retention period depends on the regulations that apply in your eligible region. You can ask support for details specific to your account.
We share data only where processing a bKash or Bank Transfer transaction requires it, where a legal obligation applies, or where you have given explicit consent. We do not sell your personal data. Third-party payment providers handle only the data necessary to complete a transaction.
Most contact details can be edited directly from your account settings page. Changes that require identity verification — such as updating your registered name — need to go through support. Open live chat or send an email to the support address shown on the Contact page.
When you close your account, we remove personal data that no longer serves an operational purpose. Some records — particularly transaction logs tied to bKash deposits or Bank Transfers — may need to be retained for a legally required period before deletion. Contact support to start a closure request.