App / Live
er666 collects only the account and transaction data needed to run your wallet, process payments through bKash, Rocket, or Upay, and keep your session secure. What we collect, why we keep it, and how you can review or correct it — that is what this policy covers. Access to er666 and the rights described here depend on your local law and eligible regions.
When you open an account, we record the details you enter at registration — your contact information, login credentials, and any verification data required to activate your wallet. When you fund your account using bKash, Rocket, or Upay, our system logs the transaction reference, the payment channel used, and the timestamp. We do not store your mobile wallet PIN or bank credentials; those remain with your payment provider. We keep session data — device type, browser version, and IP address — for security purposes only. This helps us detect unusual login patterns and flag account access that does not match your normal device or location. We do not use this data for advertising profiling or sell it to third-party marketing networks. Account records are retained for as long as your account remains active and for a period afterward as required by applicable rules. If you close your account, you can request a summary of the data we hold before deletion is processed. Availability of all features, data rights, and the retention obligations described here depend on your local law and the eligible regions where er666 operates.
This policy applies to information collected through er666 directly — your account, your wallet activity, and your use of our site on any device. It does not extend to third-party services you reach through links on our pages. Understanding the boundary matters, especially when your bKash or Rocket wallet provider operates under their own separate terms.
Data gathered when you log in, update your profile, or verify your identity falls under this policy. This includes the email, phone number and device session recorded at each sign-in.
Payment records created when you deposit or withdraw using bKash, Rocket, or Upay are covered here. We log the channel and reference number, not your wallet PIN or bank password.
Your interaction with game lobbies, sports markets, and navigation events on er666 pages is within scope. We use this data only to maintain session continuity and detect errors.
External links, your mobile wallet provider's own platform, and payment processors operate under their own privacy terms. This policy does not govern data handled outside our domain.
You have concrete steps available if you want to review, correct, or question how your data is held. Start by opening your account settings — the profile section shows the contact details and verification records we hold against your login. If any detail is wrong, you can edit it directly in the account form or send a correction request to our support channel. For transaction records tied to bKash, Rocket, or Upay deposits, the history tab in your account lists each entry with its channel label and reference code. If a record appears incorrect or missing, note the reference and raise it through the support route described on the contact page. We will investigate and reply through the same channel. Where you want a copy of all stored data, or you want to request deletion after closing your account, submit that request in writing via the published support route. Processing times depend on the nature of the request and any obligations under applicable rules in your region.
Open the account history tab to see every transaction reference, including the payment channel used for each bKash or Rocket deposit.
Update contact information directly in profile settings. For verification data that cannot be self-edited, submit a correction request through support.
If a transaction record or stored detail looks wrong, note the reference number and contact us through the published support route shown on the contact page.
Submit a written request via the support channel to receive a copy of your stored data or to initiate deletion after your account is closed.
If you have a question about this privacy policy, a request to review your account data, or a concern about how a transaction record was logged, reach us through the routes published on the er666 contact page. We do not invent operating hours or response windows here — check the contact page for the current available channels and any stated response detail.
Open the chat icon from any page while signed in to raise a data question or flag an incorrect account record in real time.
Send a written request to the support email listed on our contact page. Include your account reference and describe the specific data matter clearly.
The help section inside your account lists step-by-step paths for common data requests, including how to download a transaction summary or update verification details.
We apply access controls to your account data so that only the processes that need it — payment verification, session authentication, and account record keeping — can read it. Cookies on er666 are used for session management and security checks, not for building an advertising profile. You can review cookie settings through your browser controls at any time.
Account and transaction records are kept while your account is active and for a period afterward as required by applicable rules. When that period ends, records are removed from active systems.
Cookies on our site handle session continuity and security checks only. We do not use tracking cookies to build advertising profiles or share browsing behaviour with ad networks.
Login sessions are protected by credential checks on every access. Unusual sign-in patterns — a new device or unfamiliar location — may trigger a verification step to protect your wallet.
If we update this policy in a way that changes how your data is used, we will post the revised version on this page. Checking this page periodically keeps you up to date.
Below are the questions we hear most often about account data, transaction records, and your rights under this policy. If your question is not covered here, the support channel on the contact page is the right place to ask.
We collect the contact details and verification information you enter at registration, plus device and session data at each login. Payment details like bKash or Rocket transaction references are logged, but your wallet PIN or bank password is never stored by us.
Yes. Open the history tab in your signed-in account to view each deposit and withdrawal entry, including the payment channel — bKash, Rocket, or Upay — and the transaction reference code linked to each one.
No. We do not sell or share your account or transaction data with third-party marketing networks. Data is shared only where required by the services that process your payments or by applicable rules in eligible regions.
For contact information, go to your account profile and edit the relevant field directly. If verification data cannot be self-edited, raise a correction request through the support channel, quoting your account reference so we can locate the right record.
After closure, your records are retained for the period required under applicable rules and then removed from active systems. Before deletion, you can request a copy of your stored data through the published support route shown on the contact page.
No. Your mobile wallet provider — bKash, Rocket, or Upay — operates under its own privacy terms. This policy covers only the data we collect on er666 itself, not the data your wallet app handles independently.