App / Mobile
eo66 is committed to being clear about what data we collect, why we collect it, and how you can manage or question it. Access to this platform and its features depends on your local law and eligible regions — this policy covers what applies when you use our services.
When you open an account with eo66, we collect information you provide directly — your name, contact details, and the credentials you set. We also gather data generated by your activity on the platform, such as session records, device type, and transaction references linked to payment methods like bKash, Rocket, and Bank Transfer. This information helps us run the account, process supported transactions, and respond to support queries routed through our published channels. We do not sell your personal data to third parties for their own marketing. Data shared with payment processors — including those handling bKash and Rocket transactions — is limited to what is needed to complete the operation. Any data transfer outside your region depends on the legal frameworks applicable to your jurisdiction. We retain account records for as long as your account is active and for a period after closure as required by applicable rules. Cookies and similar tracking tools are used to keep your session running, remember your preferences, and understand aggregate site usage. You can manage cookie settings through your browser. We apply reasonable technical and organisational measures to protect the data we hold. No method is completely without risk, and we will inform you if a breach occurs that materially affects your account. Availability of specific services depends on local law and eligible regions.
Transaction references tied to bKash deposits are passed only to the payment processor handling that operation. We do not store your full mobile wallet credentials. Your bKash transaction history on eo66 is visible in your signed-in account area under transaction records.
Rocket payment data follows the same handling as other supported local rails. Only the reference and amount needed to match and confirm your deposit are recorded on our side. You can review confirmed deposits in your account wallet section.
Bank Transfer instructions and references are logged against your account for verification and support purposes. If a transfer reference needs correction, raise it through the support route published on the site and our team will check the record.
Session tokens, device type, and browser information are collected to keep your login secure and to detect unusual access patterns. You can end active sessions from the account security section. If you spot a session you do not recognise, contact support immediately.
Not every service or link you encounter through eo66 falls under this policy. Understanding the boundaries helps you know where to direct questions and what choices are yours to make.
Any data created when you register, log in, or update your account profile is covered fully by this policy. This includes email address, contact number, and the security credentials you set. Review and correction requests for this data go through the account settings page or our support route.
Transaction data for supported payment methods — bKash, Rocket, Bank Transfer — is covered to the extent it passes through our platform. The privacy practices of the payment provider on their side are governed by that provider's own policy, which we do not control.
Pages, game lobby content, and cookies served from eo66 are within scope. Analytics data collected through on-site tracking is aggregated and used only to improve platform performance. You manage cookie preferences through your browser settings.
Links to external sites, third-party identity verification services, or payment gateways operate under their own policies. We are not responsible for how those parties handle data once it leaves our platform. Check the relevant provider's policy directly for those interactions.
You have practical choices available to you regarding the data we hold. Reviewing your account records is straightforward — log in, go to account settings, and the information we hold against your profile is visible there. If something looks incorrect, you can update contact details directly in the same section or raise a correction request with our support team by using the published contact route on the site. If you want to understand what data we hold beyond what is shown in your account, or if you want to ask us to delete your account and associated records, send a written request through the support channel listed under the contact section of this page. We will respond within a reasonable period, subject to any retention obligations that apply under local rules. Where this platform is available depends on your local law and eligible regions, and the same applies to how certain data rights are exercised in your jurisdiction.
Log in and open the account settings page to see the personal details we hold. Transaction history and session records are in separate sub-sections. If a record does not match what you submitted, note the discrepancy before contacting support.
Contact details and display preferences can be updated directly in account settings without contacting support. For identity-related fields that are locked after verification, a correction request through the support route is required.
If you have a question about how we use a specific piece of your data, use the support contact route published on this site. State your account reference and the specific data point in question so we can give you a precise answer.
A request to close your account and ask about data retention can be submitted through the same support route. We will confirm what is deleted, what is retained, and for how long, based on the obligations that apply at the time of your request.
For any question or request related to this policy, use the support routes published on the site. We do not publish channels we cannot staff, so only the routes listed here are active.
The live chat widget on eo66 connects you to our support team. Use it to raise an urgent account or data question. Have your account reference ready so the team can locate your record without delay.
For written requests — including correction requests, data queries, and account closure — use the email address published in the contact section of the site. A written channel creates a record of your request and our response.
The help section on the site covers common account and data questions with step-by-step answers. Check there first for questions about session management, cookie settings, or updating your contact details before raising a support ticket.
We have designed the account and data layer around the practical needs of our members — keeping records accurate, access controlled, and support responsive. Here is how each area works.
Account and transaction data is stored on secured infrastructure with access restricted to staff who need it to operate the service. We retain records for the period your account is active plus a post-closure window required by applicable rules. You can ask about specific retention periods through the support route.
We use session cookies to keep you logged in and preference cookies to remember your settings. Analytics cookies track aggregate usage patterns, not individual journeys. Manage or block cookies at any time through your browser settings — some platform features require session cookies to function.
Access to your account data is protected by the login credentials you set. Unusual login activity triggers a review process visible in your account security section. If you see activity you do not recognise, end the session there and contact support using the published route on the site.
When we update this policy, the revised version is published at this URL with the date of change noted at the top. For questions about a specific change or to request a copy of the previous version, contact us through the email route published in the support section.
These are the questions we hear most often about how we handle your data and what options you have.
We collect the details you enter during registration — name, contact number, and email — plus session and device data generated when you use the platform. Transaction references for bKash, Rocket, or Bank Transfer deposits are logged against your account for verification purposes.
We share data only where necessary to operate the service — for example, passing a transaction reference to a payment processor when you deposit via Rocket or bKash. We do not sell your data to advertisers or unrelated third parties. Each processor handles data under its own policy.
Log in to your account and open account settings. Your profile details, session history, and transaction records are visible in separate sections there. If you need information beyond what is shown, submit a written request through the email support route published on the site.
Yes. Send a deletion request through the published support email. We will confirm what is removed immediately and what we are required to retain under applicable rules, along with the retention period for anything kept. Availability and retention obligations depend on local law and eligible regions.
We use session, preference, and analytics cookies. Session cookies are required to keep you logged in; the others can be managed or blocked through your browser settings. Blocking non-essential cookies does not prevent you from accessing your account, though some preferences may reset between visits.
Use the email support route published in the contact section of the site. State your account reference and describe the specific concern clearly. We will acknowledge your message and respond within a reasonable period. If you remain unsatisfied, you may have recourse through the relevant authority in your jurisdiction.