Casino / Mobile
ere77 collects only the information needed to run your account and process transactions through local payment routes like bKash, Nagad and Rocket. This policy explains what we collect, why we hold it and what choices you have — read it before you use your account.
When you open an account with us, we collect the details you submit during registration — name, contact information and the payment identifiers linked to your wallet. If you transact through bKash, Nagad or Rocket, we record the transaction reference that your wallet provider returns to us. We do not store your full mobile banking credentials. Session data — the device type, browser version and connection timestamps — is logged automatically each time you sign in. We use this to maintain your session across devices and to flag unusual access patterns on your account. We do not sell your personal data to third parties. Data shared with payment processors is limited to what those processors require to complete or verify a transaction. Where local law in Bangladesh or your eligible region sets out specific data-handling obligations, we follow those requirements. Retention periods depend on the category of data: active account records are kept while your account remains open; transaction references are retained for as long as our compliance obligations require. If you close your account, we will explain which records we must keep and for how long before we complete the closure.
This policy applies to information collected through ere77 and its account services. It does not extend to third-party sites you reach through links on our pages, nor to the data practices of payment processors such as bKash, Nagad or Rocket — those services have their own policies that govern how they handle your wallet data. Availability of any account feature depends on your local law and eligible region.
Registration details, login history and session tokens generated when you sign in to your account on any device are within scope. We control how this data is stored and can respond to your requests about it.
Payment references returned by bKash, Nagad or Rocket after a transaction are within scope. The internal records of your wallet provider sit outside our policy — check directly with your wallet service for those.
Browsing behaviour on ere77 — pages visited, time on page, device type — is within scope and used only for session management and service improvement. We do not use it to build advertising profiles.
Game content providers, external analytics tools and payment processors operate under their own privacy terms. Our policy does not cover how those third parties handle data once it reaches their systems.
Your rights under this policy are practical, not just procedural. You can ask us to show you the account data we hold — we will provide a summary through the support route listed below. If any detail is wrong, you can ask us to correct it; for straightforward items like a contact number, this is usually handled quickly once we verify your identity. If you believe data is being held beyond the period it should be, raise that in writing and we will check the retention rule that applies. Closing your account is also an option; we will tell you which records we are required to keep before you confirm. Access to these rights depends on your local law and the eligible region under which your account was opened. We aim to respond to each request within a reasonable period, though we cannot commit to a fixed timeline without knowing the nature of the request.
Contact support to request a summary of the personal data we hold on your account. We will verify your identity before sharing any record.
If your name, contact number or linked payment identifier is recorded incorrectly, raise a correction request through the support channel and we will update it after verification.
If you think we are holding data longer than necessary, write to us with the specific record in question. We will check the applicable retention rule and respond in writing.
You can ask us to close your account at any time. Before we complete the closure, we will tell you which records must be retained and under which obligation.
If you have a question about this policy, the data we hold on your account, or a correction request, use the routes below. We do not publish a direct email address in this policy text to avoid harvesting; all contact is routed through the channels visible inside your signed-in account area. Response times vary depending on the complexity of the request — we do not commit to a fixed SLA here.
Open the support panel inside your signed-in account to start a live chat session. This is the fastest route for straightforward account and data questions.
For formal data requests — access summaries, corrections, retention queries — use the written request form in your account settings. We handle these separately from general support tickets.
A dedicated policy contact address is shown inside your signed-in account under the privacy section. Use this for matters that require a documented response or account closure requests.
Our approach to data is shaped by what your account actually needs. We do not collect data speculatively. Cookies on ere77 are used to maintain your session state and remember your device between visits — not for cross-site advertising. You can clear session cookies through your browser settings at any time, though doing so will sign you out of your current session. Account security relies on login verification at each session start; we log the device and time of each sign-in so you can identify unfamiliar access in your account history.
Session cookies keep you signed in across page loads. Persistent cookies remember your device for future visits. Neither type is used to serve ads on other sites or build a profile outside ere77.
Each sign-in generates a session log visible in your account history. Check this regularly — if you see a device or time you do not recognise, contact support immediately through the account panel.
Active account data is held while your account is open. Transaction references linked to bKash, Nagad or Rocket payments are kept for as long as our compliance obligations require, which we can explain on request.
If we update this policy in a way that affects your rights or how we process your data, we will notify you through your account before the change takes effect. Continued use after notice means acceptance.
These are the questions we receive most often about how ere77 handles account data, cookies and privacy requests. If your question is not answered here, use the support routes listed above.
No. When you transact through bKash, Nagad or Rocket, we receive only the transaction reference that your wallet provider returns. We do not store your wallet PIN, password or any internal wallet credentials. Those remain entirely within your wallet provider's system.
Yes. Submit a data access request through the written request form in your account settings. We will verify your identity and provide a summary of the records we hold. The scope of this right may depend on your local law and eligible region.
Some records — primarily transaction references — must be kept for a period set by our compliance obligations even after closure. Before we complete an account closure, we will tell you exactly which records are retained and under which requirement, so you can make an informed decision.
We use session cookies to keep you signed in and persistent cookies to remember your device. You can clear or block cookies in your browser settings at any time. Blocking session cookies will sign you out; some account features may not work correctly without them.
This policy covers data collected through your account and browsing on ere77. Game content from studios like JDB, Habanero or CQ9 is delivered through their platforms; those studios handle any data collected inside their game environments under their own policies, not ours.
Open the account support chat immediately and report the session. Include the device type and timestamp shown in your account history log. We will review the session record and advise you on securing your account. Do not wait — act as soon as you notice the unfamiliar entry.