App / Mobile
This page explains what 777jat records when you open an account, sign in and move money through your wallet, and it sets out what you can ask us to change. Read it before you register, and note that access to the platform still depends on your local law and eligible regions.
We keep the policy short in intent: we collect what the account and wallet need to work, and we do not collect the rest. When you open an account we record the details you type in, because your sign-in depends on them. When you move money, the transaction record has to exist so the wallet balance matches what you see. Device and browser details are logged so that a session on a new phone can be recognised and questioned. What we hold is limited to running the account, meeting the record-keeping duties that apply to us, and answering you when you contact us. We do not sell your details, and we do not pass them to game studios, because studios supply game content only and never see your account. How long a record stays depends on the type of record and on the law that applies where you live. Some obligations differ between countries, so treat this page as our general posture rather than a fixed promise for every region. Our payment routes currently include Nagad, Upay and Bank Transfer, and the record created when you use one of them is part of what this policy covers.
The boundary matters more than the wording. Four areas sit under this policy, and two of them are often confused with it. If you are unsure whether a request belongs here, send it through the support route and we will point you to the right place rather than leave it unanswered.
Sign-in details, the email you registered with, and the session data that keeps you logged in on your phone or desktop all sit inside this policy. If you change your email, the change and the record of it are covered here too.
A Nagad, Upay or Bank Transfer movement creates a record on your account, and that record is covered. Note that the wallet provider keeps its own records under its own terms, so a question about your Nagad history belongs with Nagad as well as with us.
Which games you open, such as Slot Rushhour or Live Cricket Pitch, and how long a session lasts, may be logged so the lobby works and so a disputed round can be checked. Game content itself comes from studios we do not control.
Your mobile wallet app, your bank, your browser and your device maker each handle data under their own policies. We cannot change, delete or explain what they hold, and a request to them has to go to them directly.
You do not need a special form to ask a question about your data, but you do need to ask from a route we can tie to your account. Sign in first, then use the published support channel so we can match the request to the right record. If you want to see what we hold, say so plainly and describe the period you mean, for example the weeks around a Nagad transfer you want checked. If a detail is wrong, tell us which field and what it should say, and we will look at the account record rather than ask you to open a new one. Where a request relates to a record we must keep under the law that applies to you, we will explain that instead of simply refusing. Deleting an account does not always remove every transaction record, and we would rather say that here than surprise you later.
Ask for a copy of the account and transaction records we hold. Name the period and, if it helps, the payment route you used, so the right entries are pulled rather than a broad export that takes longer to check.
If your name, email or contact number is wrong, tell us which field and the correct value. We will review the account record; some fields need a second look before they change because sign-in depends on them.
Ask about cookies, device logs or how a session was recorded. Give the device you were using and roughly when it happened, and we can find the matching entry instead of guessing.
You can ask us to stop using your details for a non-essential purpose, or to close the account. We will explain what can be done and what has to stay on record.
Privacy questions go through the same published support route as any other account matter, which keeps your request attached to your account instead of sitting in an inbox nobody can match. Sign in, open the support entry shown on the site, and describe what you need in one or two lines. Include the email on the account and, where it is relevant, the payment route involved, such as Bank Transfer or Upay. We do not publish separate hours for privacy requests, so treat the response time as the same one that applies to your other account messages. If your question is about a wallet record rather than our account record, raise it with the wallet provider as well, because some of that history is only visible on their side.
The support entry inside your account is the route we can match to your record. Open it after signing in and describe the request. Include the email registered on the account so the message lands against the right profile.
This page and the terms published on the site are the reference we work from. Read them before you write if your question is about what is covered, so the reply can address the actual point rather than restate the policy.
For Nagad, Upay or bank-side history, the provider's own support channel holds records we cannot see. Use it for anything about the transfer itself, and come back to us for the matching entry on your account wallet.
Handling is deliberately narrow. We keep the details the account needs, log what security requires, and leave the rest alone. Cookies exist so the lobby remembers your session and your device preferences between pages; clearing them signs you out rather than deleting your account. Security sits with your sign-in: keep the password to yourself, and if a device is shared, sign out when you finish rather than leaving the session open. When you play on mobile, the same account rules apply as on desktop, and a new device sign-in is the kind of event we may query. Retention follows the record type. Transaction entries stay longer than session logs because they support wallet balances and disputes. You can ask what applies to a specific record, and you can ask for a correction through support. If you want a change made, say which record and why; that is faster than a general request.
Account details you enter, wallet and transaction entries, and device or session logs needed to keep sign-in working. We do not hold studio-side game data, because studios provide game content and do not receive your information.
Cookies keep you signed in and remember basic preferences across pages. Clearing them ends the session. Blocking them entirely may stop parts of the lobby from loading, so change settings with that in mind rather than all at once.
Your password is the main lock. Do not share it, and sign out on a device you no longer use. If something looks wrong with a sign-in, message support with the approximate time so the entry can be found.
Records are kept for as long as the purpose and applicable law require, with transaction entries generally held longer than session logs. To request a change or removal, send the specific record and reason through the published support route.
These are the points that come up most often when someone reads this page and then writes to us. Each answer stays on the policy itself rather than drifting into how the lobby works. If your situation is not covered, the support route is still the right place to ask, and a short message with the account email is enough to start.
No. We use account and wallet records to run your account, keep the records the law requires, and reply to you. Game studios supply content only and do not receive your account data. Your mobile wallet and bank hold their own records separately, under their own policies, which we cannot change.
You can ask us to correct a wrong name, email or contact number, and you can ask what we hold for a given period. Some fields need review before they change because sign-in depends on them. You can also ask us to stop using details for a non-essential purpose, and we will explain what is possible.
Device and browser entries help us recognise a sign-in from a phone or desktop we have not seen before, and they let us check a disputed session if you raise one. That logging is tied to keeping the account secure, not to building a profile you would not recognise.
The entry created on your account wallet when you use Nagad, Upay or Bank Transfer is covered by this policy, and you can ask us about it. The wallet provider and your bank keep their own separate records, so anything about the transfer on their side has to go to them.
You can ask us to close the account. Not every record disappears with it, because transaction entries may have to be kept for a period under the law that applies where you live. We will tell you what can be removed and what stays, rather than promise a full deletion we cannot deliver.
Sign in, open the published support entry and ask for your account and transaction records. Name the period you want and, if it helps, the payment route you used. Doing it from inside the account means the request is matched to the right record without extra checks.