Mobile / App
One policy covers what shaka7 holds about you: the account details behind your sign-in, the wallet records from a bKash, Nagad or Rocket transfer, and the device you use most. Access to the lobby depends on your local law and eligible regions, so treat this page as the rule set for your account rather than a general promise.
We keep one privacy policy for the whole account journey, from the first time you open the site to the records you build later. Our posture is simple: we say what we hold, why we hold it, and how you can ask us to change it. Anything outside that path — a wallet page you reach through a link we do not control, for instance — sits outside this policy and follows the terms of whoever runs it. Some parts of the policy move with local law. What we may store, how long we keep it and which payment routes appear for your account all depend on where you are and whether your region is eligible. We cannot promise one rule set for every country, because we do not run one. Where your local law is stricter than ours, your law applies to your account. That is why the payment chips below sit inside this section rather than above it. When you start a bKash, Nagad or Rocket transfer, your account links that movement to your profile, and the linked entry forms part of what this policy covers for members in Bangladesh. If your situation changes — a new number, a new handset, a new region — tell us through the published route and we adjust what we hold. We would rather update a record than carry one you no longer use. Questions about the wording are welcome, and they travel the same support path as your account queries.
Not everything you touch while signed in is covered by this page. Our policy follows four areas: your account access, the transaction records attached to it, the content we publish in the lobby, and the outside services you reach by your own choice. We write the rules for the first three. The fourth answers to someone else. Take account access. Your sign-in email, mobile number and the device you use most often are held so the account stays yours. Transaction records — a bKash deposit, a Nagad transfer, a Rocket payment — are kept so you and we can both see what moved and when. Lobby content, including the game pages you open and the screens you read them on, shapes how we keep the site working on your handset. Third-party services sit outside. If you follow a link to a payment app or any site we do not run, that operator collects what it collects under its own terms. Where an area is unclear, ask us through the published support route and we will tell you which rules apply.
Your sign-in email, mobile number and the device you register with are held so only you can open the account. Move to a new handset and the session data tied to the old one refreshes at your next sign-in. Ask us to change the contact details on file whenever you need.
Every bKash deposit, Nagad transfer or Rocket payment you start from the account wallet creates a matching entry in your transaction history. We keep those entries so you can compare what left your wallet with what landed in the account, and so a disputed entry can be traced back.
Which game pages you open, how long a session runs and which screen you use help us decide what loads first on mobile. This is activity tied to your own account rather than a shared profile, and it is what we check when a page misbehaves on one handset but not another.
Payment apps, wallet pages and any site you reach through a link we do not run sit outside this policy. Those operators collect their own account data under their own rules, so read their terms before you share anything there. We hold only the part of the movement that touches your account.
The policy gives you moves, not just statements. You can open your account settings and check the details we hold, correct a phone number or email that has changed, ask what sits behind a transaction entry, and tell us to delete what we no longer need. Start with the fields you can see. Saved contact details, your linked payment route and recent activity all sit in the signed-in area, so a correction takes a few taps instead of a support ticket. If a field will not accept your change, send the request through the support route with your account email attached. Deleting everything is not always possible while an account stays open, because a transaction record has to survive long enough to be checked. Close the account and the linked records go once the retention period for your region ends. Where your local law gives you a stronger right, that right applies.
Open the account area and look at the fields we hold against your name: email, mobile number and linked payment route. Everything there is yours to inspect, and nothing on that page needs a support request first. Compare it with the wallet receipt on your phone if a number looks off.
Changed your number? Moved the account to a new handset? Update the contact field directly and we carry the new value across your account. If the field will not accept the change, send the request through support with the account email attached so we can match it to your record.
Point at any line in your transaction history — a bKash deposit, a Nagad transfer, a Rocket payment — and ask us what it links to. We walk you through the matching step instead of leaving you to guess, and where a wallet receipt and our entry disagree we look at both.
You can ask us to remove data we no longer need, and to hand back a copy of what we hold. Some records stay while an account is open, and the retention period depends on your region and local law. Send the request from the email on your account.
A privacy question deserves a straight path, so keep using the route you already know. The same support channel that answers a deposit question also answers a question about your records. No separate form, no second email address. Open the signed-in account area first. Most questions about held data come down to a field you can see, and the page answers them without a wait. When that is not enough, send your message through the contact route published on the site and put your account email in it. That one detail is what lets us match your record. Keep the message short and specific: which field, which transaction, which device. A short message naming one entry is easier for us to act on than a long description about the whole policy. We do not print hours we cannot keep, or a reply window we cannot measure. Every message that arrives through the published route reaches the team that holds your account data.
Sign in and open the help link inside your account. It puts your email and account number in front of the team already working with your records, so you skip the step where we ask who you are. Use this route for anything tied to a specific field, entry or device on screen.
The contact route published on our site is the second path, and it works without a sign-in. Put your account email in the message so we can attach it to the right record. Use it for questions about the policy wording, or anything you want to raise before opening an account.
For a bKash deposit, Nagad transfer or Rocket payment you cannot match to a history entry, send the wallet receipt with your message. Add the date and the account email. We look at both sides of the movement before answering, which is the step a general question about deposits skips.
What we hold is small and tied to the account: your email, mobile number, the payment route you pick and the activity that shows the account is yours. We keep it to run sign-in, to match a wallet movement to your record, and to answer you when something looks wrong. Cookies do a narrow job here. They keep you signed in between pages, remember your screen size and language, and tell us when a page fails to load on one handset. Blocking them may sign you out or reset your view, but the lobby stays readable. Your browser settings control that choice. Account security rests on the details you give us. Keep the email and mobile number on file current, because a recovery request is matched against them. On a shared device, sign out when you finish and tell us at once if a sign-in was not yours. Retention follows your region. Transaction records stay while an account is open and for the period your local law requires afterwards, then they are removed.
Your email, mobile number, chosen payment route and account activity make up the working set. We do not ask for details we cannot use, and we do not sell what we hold to anyone outside the service. A record exists because it supports sign-in, a transaction entry or an answer to you.
Session cookies keep you signed in and remember your language and screen size. A small amount of local storage speeds up repeat visits on the same handset. Clear your browser storage and the account still works — you simply sign in again and pick your settings back up.
Your sign-in email and mobile number anchor any recovery request. Keep both current, use your own device where you can, and sign out on shared phones. If a sign-in looks wrong to you, raise it through the published support route so we can end the session and check it.
Transaction records stay while your account is open and for the period your region requires afterwards. Ask us to change or remove what we hold through the published route, and we tell you what was done. Some entries stay while the account is live, because they have to be checkable.
These are the questions that reach us most often, answered without the legal padding. If yours is not here, the published support route is the next stop, and the account email in your message gets it to the right record. Most questions come down to three things: what we hold, who can see it, and how you get it changed. On the first, the working set is small — contact details, payment route, activity. On the second, the answer is the team that runs your account and the payment provider handling the movement you started. On the third, you either change the field yourself in the account area or ask us through support. One rule survives every answer below. Where your local law gives you a stronger right than this policy does, the law applies, and eligibility for the service itself always depends on your region.
Your email, mobile number, the payment route you picked and the activity tied to your sign-in. We also keep the transaction entries created by a bKash deposit, Nagad transfer or Rocket payment. That set exists to run the account, match payments and answer your questions rather than to build anything else.
Yes. Send the request through the support route published on the site and put your account email in the message. We attach the request to your record and reply with what we hold. Where local law sets a different process for your region, we follow that instead.
Only where it is needed to run the service — the payment provider handling a transfer you started, for example. We do not sell account data. Links to payment apps or other sites take you outside this policy, so read the terms on that page before you share anything there.
Sign in and open your account details. The contact fields sit there, and a correction takes a few taps. If a field will not accept your change, send the request through support with your account email attached and we match it to your record by hand.
Transaction entries stay for the retention period your region requires, then they are removed. Contact details and sign-in data go with the account. You can ask us to confirm what was removed once the period ends by sending a message through the published support route.
Yes. What we may hold, how long we keep it and which payment routes appear all depend on your local law and whether your region is eligible for the service. Where your local rules are stricter than this policy, those rules apply to your account.