Live / Mobile
king777 collects only the account and payment data needed to keep your sessions running and your wallet secure. This policy explains what we collect, why we hold it, and the choices you have over your own information — with access depending on your local law and eligible regions.
When you open an account, we collect the registration details you provide — name, contact information and login credentials. When you make a deposit or withdrawal through Nagad or Bank Transfer, we record the transaction reference, amount and timestamp so your wallet history stays accurate and disputes can be resolved. We also collect device and browser signals — IP address, session tokens and page interaction data — to protect your account from unauthorised access and to keep the platform loading correctly on mobile. We do not sell your personal data to third parties. Data shared with payment processors like Nagad or Bank Transfer goes only as far as completing your transaction. Any analytics data we retain is aggregated: it tells us how sections of the platform perform, not what any individual account does. Retention periods follow the transaction record requirements applicable in supported regions. If you close your account, we retain only the minimum records required for financial reconciliation and legal compliance; everything else is deleted on a rolling schedule. Access to this platform and its data practices depends on your local law and eligible regions.
This policy covers the data king777 processes directly. Some areas — like third-party payment processors and linked services — operate under their own terms. The table below sets out what falls inside and outside the scope of this document so you know exactly where our obligations begin and end.
Covered. Login credentials, session history and account verification data are all processed by king777 and fall fully within this policy. You can review your account access log from the signed-in account area at any time.
Partially covered. We record transaction references and wallet balances on our side. The Nagad or Bank Transfer processor handles the actual transfer under its own privacy framework; their policies govern the payment leg of any transaction.
Covered. Cookies we place on your device for session management, security and platform performance are governed by this policy. You can adjust cookie preferences through your browser settings; disabling certain cookies may affect platform behaviour.
Not covered. Links to external sites, game studio lobbies hosted by providers, or any third-party tool you reach from our platform operate under those parties' own terms. We have no control over data collected outside king777 infrastructure.
Your account data belongs to you, and this policy sets out the practical steps available to you. Reviewing your records is the starting point: log in and open the account history section to see transaction timestamps, login events and wallet movements. If any detail looks wrong — a name spelling, a contact address, a linked payment reference — you can update most fields directly from the account settings page. For changes to sensitive fields that require verification, the support team can walk you through the steps shown in the help section. If you want a copy of the data we hold on your account, raise a request through the support channel and we will prepare a summary. Requests to delete account data are handled case by case; records tied to completed Nagad or Bank Transfer transactions may need to be retained for the minimum period required by applicable financial rules in your region. Every request is acknowledged and actioned in line with our published policy — no request disappears into a queue without a response.
Open the account history section after logging in. Transaction timestamps, wallet movements and login events are all visible there without needing to contact support.
Most contact and profile fields update directly from account settings. For verified identity fields, follow the instructions shown in the help section or raise it with support.
Contact us through the published support route and ask for a data summary. We will compile the account-level records we hold and share them with you in a readable format.
If anything in this document is unclear, reach the support team through the live chat or email route published on the site. Policy questions are handled separately from game or payment support tickets.
Privacy requests — data copies, correction queries or deletion notices — go through the same published support channels as account help. Use the route that matches your situation: live chat for quick questions, email for requests that need a written record.
Open the chat widget from any signed-in page to ask a privacy question or flag a data concern. Responses follow the queue shown in the chat window at the time you connect.
Send privacy requests — including data copy or correction requests — to the support email address published in the help section. Email creates a written record of your request and our response.
The help section inside your signed-in account lists step-by-step paths for common privacy actions: updating contact details, reviewing transaction history and submitting a formal data request.
Account security and data handling are not separate concerns — they sit in the same infrastructure. Here is how we approach each area so you can verify what we say against what you see in your account.
We place session and security cookies on your device when you log in. These keep your account active and protect against session hijacking. No third-party advertising cookies are placed without your browser's consent settings allowing them.
Login events are logged with device and IP data so you can spot any unfamiliar access in your account history. If you see a login you do not recognise, contact support immediately through the live chat route.
Active account data is held for the duration of your account. After closure, transaction records tied to Nagad or Bank Transfer payments are retained for the minimum period required under applicable rules; all other personal data is deleted on schedule.
When we update this policy, we post the revised version here and note the change date at the top of the document. Continuing to use the platform after a change is posted means you have had the chance to review the update.
These are the questions we get most often about how king777 handles your data. If yours is not here, reach us through the live chat or email route in the help section.
We collect the registration details you enter — name, contact information and login credentials — plus device and browser signals such as IP address and session tokens. We do not collect more than we need to run your account and process your transactions.
We pass only the transaction reference and amount to the payment processor to complete your deposit or withdrawal. The processor handles that data under its own privacy policy. We do not share account profile data, browsing history or login records with payment processors.
Log in and open the account history section to view transaction records and login events. For a full data summary, send a request to the support email published in the help section. We will prepare and share your account-level records on receipt of the request.
Yes. Send a deletion request through the support email route. Records tied to completed Nagad or Bank Transfer transactions may need to be retained for the minimum period required by applicable financial rules in your region; everything else is deleted on confirmation of your request.
We use session and security cookies to keep your account active and protected. You can adjust cookie settings in your browser; switching off certain cookies may affect how the platform loads on your device. We do not place advertising cookies without your browser settings allowing them.
We post the updated policy here and note the revision date at the top of this page. If a material change affects how your data is used, we will take reasonable steps to inform you through the account or support channel. Availability and obligations depend on local law and eligible regions.