App / Casino
ashs7777 keeps a single privacy policy for the whole account journey, from the mobile number you register with to the Nagad and Upay records your wallet shows afterwards. We wrote it so you can see what we hold, why we hold it, and who to ask when something on your account does not look right.
One policy, written for the way the account is actually used. When you open ashs7777 from Bangladesh, we hold the details you type in yourself — your mobile number, your account name, and the wallet records that appear after a Nagad or Upay transfer. Nothing beyond what running the account needs is gathered, and none of it is collected quietly in the background. Some of what we keep is there for one plain reason: so you can sign back in on a different device and see the same balance, the same transaction history and the same support thread you left behind. Where you live shapes the rest. Features and payment routes on this site depend on your local law and the eligible regions you are in, and parts of this policy read differently for that reason. We keep the wording broad enough to cover it and tell you plainly when a rule applies to your own account rather than to everyone. If a route you expect in your wallet is not available where you are, the account area will say so instead of leaving you to work it out. Your data is not sold, and your wallet records are not passed to another brand for its own marketing. Inside our team, access is grouped by role: a support colleague answering your question sees what is needed to resolve it, not the whole picture. If the way we handle data changes, this policy changes with it, and the newest version is the one that applies.
Not everything that happens around your account sits inside this policy, and it helps to know where the edges are. Sign-in details, the wallet records built from your Nagad and Upay transfers, and the messages you send support all fall inside it. So do the cookies that keep you signed in between pages, so your details are not retyped each time you return. What sits outside is narrower than most people expect. Third-party services you reach from our pages — a wallet app, a bank app, a studio page — answer to their own privacy rules rather than ours, and we cannot read or change what they store. Links that leave the lobby behave the same way. Browser-level choices stay with you. Clear cookies in your phone settings and parts of the account area will ask you to sign in again; that is expected behaviour, not a fault. Your own device settings decide what a shared phone remembers about you, and no policy of ours can override them.
Your mobile number, account name and the session details that let you sign back in on a second device are covered here. So is the device and browser record we keep to spot a sign-in that does not match how you usually reach the account. You can ask what we hold on this.
Everything your wallet shows after a Nagad or Upay transfer sits inside this policy: the amount, the reference, the time the record was written and the account it was tied to. Those entries are what we use when you raise a question about a transaction.
Pages you open in the lobby and the titles you launch from Pragmatic Play, Spadegaming, CQ9, Habanero and JDB are part of the site we run, so activity there feeds your account records. It does not create a separate profile that we hand to anyone outside.
A bank app, a wallet app or any outside page you reach from a link here follows that provider's own privacy rules. We cannot read, correct or remove what they store, and a request about their data has to go to them directly. We will point you to the right door.
You do not need a reason to ask what we hold. Send the question from the account area and we will show the records tied to your mobile number, your wallet and your support history — the same entries you can already see after signing in. If a detail is wrong, say which one. A misspelled account name or an old phone number slows down a Nagad or Upay withdrawal check, so correcting it early saves you a round of back-and-forth later. Some fields you can edit yourself in the account area; others we change once you ask, so the record stays right on both sides. You can also ask us to hold back messages that are not about your own account, and to gather what we hold into one readable copy. None of this depends on a paid tier or an invitation. It is open to every account holder, and asking will never affect how your account is handled.
Open the account area from any signed-in device and your wallet entries, sign-in history and past support threads sit together. You do not have to raise a request to read them, and nothing is kept behind a separate door.
If your name, number or wallet reference is written wrongly, tell us and we will update it. Keeping those fields right matters most around Nagad and Upay records, where a small mismatch can send a check back to you for another round.
Any question about this policy can go through the support route published on the site. Say which record you mean and roughly when it appeared, and the answer comes back sooner than a general message about the account would.
You can ask us to hold back messages that are not about your own account, without losing anything that concerns your wallet or your sign-in. Replies to a question you raised, and anything about a Nagad or Upay record, will still reach you as normal.
Every privacy question we answer starts in the same place: the support route you can see published on this site. There is no private address to hunt for and no separate desk for policy matters, because a question about your data is a question about your account and we treat it that way. When you write, tell us what you are asking about — a wallet record from a Nagad transfer, a sign-in you do not recognise, a correction to your account name. Add roughly when it happened. We match that against the entries in your account before replying, so the more specific your message, the less we have to ask before we can answer. Replies reach you through the same route you wrote in on, and they stay in your account thread, so you keep your own copy. We do not move a privacy request into a chat app or a call you did not start. If a request needs something only you can confirm, we will say what and why rather than leave it open.
Every privacy question starts with the support route published here, and it is the same door for a wallet record, a sign-in you do not recognise, or a correction to your account name. Write from your account so we can match your message to the right entries.
Replies land in the same thread you wrote in, so your own copy of the exchange stays with you. We do not move a policy question to a channel you never used, and nothing is closed without an answer you can read.
Say which record you mean — a wallet entry from a Nagad or Upay transfer, an account detail, a message you received — and roughly when it appeared. A specific question is answered faster than a broad one about the account as a whole.
Data care here is mostly ordinary housekeeping, repeated. We ask for the fields an account needs and nothing past that. Wallet records are kept while a dispute or a support question could still refer to them, and what no longer serves that purpose is removed or made untraceable. What stays is what your own history needs to make sense. Cookies do two jobs. One keeps you signed in between pages so your details are not retyped on every screen; the other counts how the lobby is used and which pages get opened. Clear them from your browser settings at any point and the trade-off is a sign-in prompt next time. Security sits on the account side, where you can see it. Sign-in is tied to your mobile number, and you can end a session from the device you are holding. If you think someone else has reached your account, write to us and we will go through the records with you. The policy moves when our practice moves, and the newest version is the one that applies.
The fields you enter yourself, your wallet records, the device used to sign in, and the messages you send support. We do not build a marketing profile from your game activity, and we do not sell what we hold to another brand.
Session cookies keep you signed in between pages, and a separate counter shows us which lobby pages get opened and where people leave. Clear them from your browser settings whenever you like; the account will simply ask you to sign in again next time.
Wallet entries tied to a Nagad or Upay transfer are held while a question about them could still come up. Once that period closes we remove what we no longer need, and what remains cannot be traced back to you on its own.
Requests to correct, copy or remove data go through the support route published on this site. Tell us which record you mean, and we confirm in writing what was changed, and when, so you have your own copy of the answer.
These are the questions that come up most often when an account holder reads this policy for the first time. Each answer below points to the route you can follow inside your own account, so nothing here depends on a special request or a paid tier. If your question is not covered, the support route shown on this site reaches the same desk that answers everything on this page.
It covers the data tied to your own account: the details you enter, wallet records from Nagad and Upay transfers, sign-in and device history, support messages, and the cookies that keep a session open. What an outside wallet app or bank app stores is theirs, not ours.
Yes. Sign in and your wallet entries, sign-in history and past support threads are there to read without asking anyone. If you would rather have everything in one place, send the request through the support route shown on this site and we will put it together.
Tell support which field is wrong and what it should say. Some details you change yourself in the account area; others we update once you ask, so the record matches on both sides. That matters most around wallet references attached to a Nagad or Upay transfer.
We do not sell it, and your wallet records are not handed to another brand for its own marketing. Inside our team, access is grouped by role, so a colleague helping you sees only what the task needs. Outside services you reach from a link follow their own rules.
Wallet records are held while a dispute or a question about them could still come up, then what no longer has a purpose is removed. If you want your details taken out sooner, ask through the support route published here and we will tell you plainly what can be done.
Use the support route shown on this site. It is the same door for account questions and policy questions, so there is no separate address to remember. Write from your account, say which record you mean, and the reply stays in your own thread.