Live / Mobile
ea2222 collects only the account and transaction data needed to run your sessions, process payments through Rocket and Bank Transfer, and keep your wallet records accurate. Access to this platform and its policy routes depends on your local law and eligible regions.
This policy describes the categories of information ea2222 collects when you register, log in, deposit or contact support. We collect your name, contact details, device identifiers, session activity and transaction records. Payment context — including records tied to Rocket transfers and Bank Transfer settlements — is stored to reconcile your account wallet and respond to disputes. We do not sell your personal data to advertising networks or unrelated third parties. Data shared with payment processors is limited to what those processors require to complete your transaction. We retain account records for as long as your account remains open and for a period after closure as required by applicable compliance obligations. Cookie data captured during your mobile sessions is used for session continuity and fraud detection, not for cross-site advertising profiles. Where our platform is accessed from Bangladesh, eligibility and lawful use depend on your local law and the eligible regions we serve. You can review the categories of data held on your account by contacting us through the support routes listed on this page. Any correction or deletion request is handled according to the process described in the rights section below.
Not every interaction with ea2222 falls under the same data rules. Understanding what this policy covers — and what falls outside it — helps you know which rights apply to which part of your experience. The four areas below set the boundary clearly.
Login events, session tokens and device identifiers collected when you sign in are fully within this policy. We use them for session continuity and to detect unusual access patterns on your account.
Payment records for Rocket and Bank Transfer deposits and withdrawals are covered here. These records are retained for reconciliation and are not shared beyond what your payment processor requires to settle the transaction.
Game session data — rounds played, wager totals, session duration — is captured at platform level and governed by this policy. It is used for account history and session control, not profiling for external advertisers.
Links or services operated by third parties outside the ea2222 platform are not covered here. Once you leave our domain, the privacy terms of those third-party services apply. We do not control or take responsibility for their data practices.
You have specific, actionable options when it comes to the data ea2222 holds on your account. You can ask us to confirm what categories of personal data we have stored, request corrections to any inaccurate account detail, or raise a question about how a particular record was used. These aren't abstract promises — they are steps you can start by contacting us directly through the support routes published on this page. If you believe a record is wrong, the fastest route is to open your account settings and update the relevant field yourself; for data you cannot edit directly, submit a correction request to our support team. Eligibility to exercise certain rights may depend on your local law and the region from which you access the platform. We aim to acknowledge every data request within a reasonable period and will follow up via the contact method on your account.
Request a summary of the personal data categories held on your account. We will confirm what is stored and why each category is needed for your account to function.
Update your contact information or account details directly from account settings. For fields you cannot edit yourself, raise a correction request through our support channel.
If you are unsure why a specific piece of data was collected or how it was used, contact support with your account reference. We will explain the purpose in plain terms.
For any deletion or restriction request, reach our team via the contact paths listed in the support section of this page. State your account email and the specific request clearly to speed up the process.
If you have a question about this policy, a data request or an account detail that needs correcting, use the routes below. These are the contact paths published on the ea2222 platform. Do not send sensitive account credentials through any unverified channel.
Open the chat icon from any page while signed in. State your query and account email so the team can pull up your record without you repeating details.
Send your privacy or data query to the support email address shown in your account profile page. Include your registered contact detail and a clear description of the request.
The Help Centre section of your signed-in account lists published policy routes and self-service steps for common data and account queries without needing to contact the team.
Your account data is handled through controlled processes that limit access to what each function requires. We do not share wallet or payment records beyond the minimum needed to settle a Rocket or Bank Transfer transaction. Session cookies expire when you close your browser unless you choose a persistent login option. Data retention periods are applied by account status, not left open-ended.
Session cookies on ea2222 are set for continuity — keeping you signed in across pages during a single visit. You can clear them through your mobile browser settings at any time. Persistent advertising cookies from third-party networks are not placed by our platform.
Records tied to Rocket and Bank Transfer transactions are passed only to the payment processor handling that specific settlement. We do not store full payment credentials on our servers. Transaction history visible in your account wallet is a ledger record, not a live data link.
Account data is retained while your account is active and for a defined period after closure. If you request deletion after account closure, we will remove data that falls outside mandatory retention obligations and confirm what, if anything, must be kept.
Data correction and deletion requests go to our support team via live chat or the support email on your account profile. We do not process data change requests sent through unofficial social channels or unverified contact forms.
These answers cover the questions we hear most often about data rights, account records and privacy contact on ea2222. If your question is not here, use the support routes listed above.
We collect the details you enter during registration — name, contact information and account credentials — plus device identifiers and session activity generated during your visits. Payment method context, such as a Rocket or Bank Transfer reference, is captured only when you initiate a transaction.
Yes. Submit a data access request through live chat or the support email shown in your account profile. Include your registered contact detail. We will confirm the categories of personal data stored and the purpose each category serves on your account.
We share data only where it is necessary — with payment processors handling Rocket or Bank Transfer settlements, and with service providers directly supporting the platform. We do not sell personal data to advertising networks or unrelated commercial third parties.
Data is retained for a defined period after account closure to meet applicable compliance obligations. Once that period passes, data that does not need to be held further is removed. You can ask us to confirm the retention period relevant to your account type.
Open your account settings and update the field directly if it is editable. For details you cannot change yourself — such as registration name or verified contact data — contact support with your account reference and the correction needed. We aim to process corrections promptly.
Yes. The same data practices apply whether you access the platform on a mobile browser or desktop. Session cookies behave the same way on mobile — they expire when you close the browser unless you enable persistent login. Your mobile device identifier may be captured for session continuity and fraud detection.