Slots / App
We keep this Privacy Policy on one page so you can see what we record when you sign in from your phone, what we store against your account wallet and payment activity, and how you can ask us to check or change it. Access to our services depends on your local law and eligible regions, so read this page together with the terms published on the site.
Privacy sits at the centre of how we run accounts, so this page explains the posture we take rather than burying it in small print. When you sign in on your phone, we keep the details that make the session yours: your login, the device and browser you used, and the activity that appears on your account page. Payment records follow the same path. If you move money through bKash or Upay, the reference lands in your wallet history so you can check it yourself instead of writing to us first. That is the whole point of record-keeping here: you should be able to see what we see. How long we keep a record, and what we are allowed to hold, depends on the laws that apply where you are. Access to our services depends on your local law and eligible regions, and where a local rule asks for something different, we follow that rule for your account. This page is kept current, not frozen. When our handling of account data changes, the wording changes with it, and you can return to read the live version at any moment. Anything you want clarified about a clause goes to the support route published on the site, and we answer there.
One policy cannot answer for everything, so we draw the line clearly. This page governs the personal details tied to your nogd888 account: the login you create, the contact details you save, the wallet references from your deposits and withdrawals, and the messages you send us. It also covers what we log when you browse the lobby from a phone. It does not govern the app store or browser you open us in, the mobile wallet that moves your money, or any outside page you reach from a link in our lobby. Those services run under their own policies, and we cannot speak for them. If you want to know how a wallet handles your transaction, that answer belongs to the wallet provider. If you want to know what we hold about your account, that answer belongs here. That line matters on a page like this one, because it tells you where to send which question.
This part of the policy covers the login you create with us, the contact details saved on your profile, and the session data that keeps you signed in on your phone. It also covers the messages you send through the support route in the lobby. Nothing about your wallet outside our site sits here.
Deposits and withdrawals made through bKash, Upay, Nagad or Rocket leave a reference that we keep against your account so you can trace it later. Our policy covers how that reference is stored and used. How the wallet itself handles your money is the wallet provider's own business.
When you open the lobby on a phone, we log basic technical details: the browser you used, the type of device, and the pages you moved through. Those logs help us keep the site working on small screens. This policy explains what we record and what stays outside it.
Links out of our lobby lead to services we do not run, and this policy ends at the edge of our site. Your mobile operator, your wallet app and any outside page you open are governed by their own terms. Take a moment to read those before you share details there.
You have more control over your account data than a single settings page suggests. Open your account page and check the profile fields we hold: your name, contact details and the wallet references attached to your history. If something there is out of date, correct it from the same screen rather than opening a new account, because a second login splits your records and makes them harder to trace. Where you cannot edit a field yourself, ask us and we will tell you what the published process allows. You can also ask what we hold, ask why we hold it, and ask us to remove what we are not required to keep. Those requests go through the support route on the site, and we handle them under the rules that apply where you live, so eligibility depends on your local law and region. You do not need a separate form for any of it.
Open your account page on your phone and read the profile fields we hold about you: your name, your contact details and the wallet references connected to your history. If you spot something that no longer matches reality, that screen is where the change starts.
Where a field can be edited, change it yourself from the account page rather than opening a second account, because a duplicate login splits your history and makes old records harder to find. If a field is locked, send the correction through the support route and we will tell you what the published process allows.
You can ask us what personal details sit on your account, ask why we keep them, and ask what we are not allowed to delete. Send the request through the support route in the lobby and we will answer under the rules that apply where you live.
If you want a detail removed, tell us which one and why. We handle these requests under the law that applies to your account, so what we can do depends on your local law and eligible regions. We will always say plainly what we can and cannot change.
Questions about privacy should not sit unanswered in a drawer, so we keep one published route for them. The support link in the lobby is where a data question starts: open it from the same device you use to sign in, so your message arrives with the account context attached. When you write, include the account email you registered with and the part of this policy you are asking about. If your question is about a payment record, quote the wallet reference from your history rather than an amount alone. If it is about a login or a device, say which phone or browser you were on. We answer through the site itself, so keep the question on the published route rather than sending it anywhere else. That keeps the question tied to the account it is about, which is how we answer it accurately.
Privacy questions go through the support link inside the lobby, which is the one contact route we publish. Open it from the same device you usually sign in with, so your message arrives with the account context already attached. Use that route rather than a public social page, so the question stays with your account.
If your question is about a record rather than a general policy clause, start from your account page and note the wallet reference shown in your history. Quoting that reference lets us find the entry quickly instead of asking you to describe the transaction again.
Ask about any clause on this page: what a section means for your account, which records it covers, or how a request is handled. Mention the section heading you are reading so the answer lands on the right point. We reply through the same published route.
Handling data well comes down to a handful of habits, and we keep them visible. Cookies do part of the work here: they hold your signed-in session so you are not asked for the same details on every screen, and your browser settings decide whether they stay. Account access is tied to the login you create, so keep that password to yourself and check the devices you have signed in from. Retention is deliberate rather than indefinite: we hold account and transaction records for as long as the rules that apply to us require, and then we let them go. Nothing on your account is kept because it is convenient, it is kept because a rule calls for it. If you want to know what we hold, want a field corrected, or want a change made, send the request through the support route published in the lobby. We answer from there, and we say plainly when a request falls outside what we are permitted to do.
Cookies keep your signed-in session alive so you are not retyping the same details on every screen, and they tell us which parts of the lobby load slowly on a phone. Your browser settings decide which of them stay, and you can clear them at any time.
Your login is the key to everything held on your account, so keep the password to yourself and check the devices you have signed in from. If a device is no longer yours, sign out of that session and change the password before anything else.
We keep account and transaction records for as long as the rules that apply to us require, then let them go. That period is set by law rather than by preference, which is why some details stay even after you stop using the account.
If you want to know what we hold, need a field corrected, or want to ask for a change, send it through the support route in the lobby. Say which detail you mean and what you want done. We will tell you what the applicable rules let us do.
These are the privacy questions we hear most from Bangladesh members, answered in the same plain wording we use in the policy itself. If your question is not here, the support route in the lobby is the place to send it, and we will answer against your own account rather than in general terms. Where a rule differs in your area, the answer follows your local law and the regions where access is available.
It covers the personal details tied to your account: your login, the contact details on your profile, your wallet references from payments, the messages you send us, and basic device logs from browsing the lobby. It does not cover the wallet app or any outside page you open from our links.
Yes. Open your account page on your phone and read your profile fields and wallet history, which is most of what we hold. For anything not shown there, send a request through the support route in the lobby and we will tell you what we keep and why.
Change it yourself from the account page if the field is editable, because editing keeps one clean record instead of two. If the field is locked, send the correction through the support route with the exact change you need, and we will handle it under the rules that apply.
Payment references from bKash, Upay, Nagad or Rocket stay attached to your account so you can trace a deposit or withdrawal later without asking us. How long we hold them follows the rules that apply to us. The wallet app keeps its own record separately.
A new device creates a fresh session alongside the old one, and both stay visible on your account. If you no longer use the earlier phone, sign out of that session and change your password. Cookies stored on that device should be cleared too.
Use the support route published inside the lobby. Say which part of this policy you are asking about, include your account email, and add a wallet reference if the question concerns a payment. We answer through that same published route rather than outside channels.