Skip to content
gd2go Sports / Casino
POLICY DESK

gd2go Privacy Policy and Your Account Details

This page sets out what gd2go holds when you open an account and move money from your wallet to the lobby, and what you can ask us to change. Read it once, then keep our support page within reach for anything that looks off — access to the service depends on local law and eligible regions.

  • Account data
  • Payment references
  • Transaction records
  • Cookie control
POLICY POSTURE

What This Policy Holds and Why

This page explains how gd2go handles the details you give us when you open an account and move money through your wallet. We keep the list short on purpose: the name and contact details on your profile, the payment reference attached to a bKash or Nagad transfer, and the transaction records that show what left your wallet and what landed in your account. We do not ask for anything we cannot explain, and if a field is optional we say so on the form itself. What we can collect, and where it is stored, depends on the law that applies in your region — availability of the service is decided the same way, by local rules and eligible regions rather than by anything on this page. Where a transfer goes through Bank Transfer, the bank's own record sits with the bank; we only hold the reference that connects it to your account. Nothing here overrides the terms shown in your signed-in account area, and where the two differ the account copy and the law that applies to you take priority. We will tell you through the site if this policy changes in a way that affects what we hold, and the current version stays published at this address.

  • bKash

  • Nagad

  • Bank Transfer

  • Account wallet

  • Mobile access

INSIDE THE SCOPE

Where the Policy Applies and Where It Stops

Scope is easier to picture as four doors. Your account login is ours: the email you register with, the password you set and the session that keeps you signed in on your phone. Transactions are split — we hold the record of a bKash, Nagad or Bank Transfer you send us, while the wallet or bank holds the money movement on its own side. Site content covers what you see in the lobby, including the titles we carry from Bigtime Gaming, JDB, Habanero and PlayStar, plus the display settings saved to your device. Third-party services sit outside this policy; when a payment app or a bank asks you for details, their own notice applies, not ours. Cricket Betflash and the rest of the sportsbook follow the same rule as the slot rooms. If a page points you somewhere else, read the notice there before you type anything in. Keep that split in mind when you ask about a missing transfer — start with the reference we can see.

  • Account access

    The email you register with, your password and the signed-in session on your phone sit with us. If you change device, sign in again so the old session stops carrying your lobby view. Anything you save to your profile is covered here, and you can edit most of it yourself.

  • Transaction records

    Every bKash, Nagad or Bank Transfer you send us leaves a record on your account: what was sent, the reference and the direction. The wallet or bank keeps its own copy of that movement, and we point to ours when you raise a question about it.

  • Lobby and site content

    Game tiles, sportsbook lists, display language and the way pages load in your browser are part of the site we run. Titles from Bigtime Gaming, JDB, Habanero and PlayStar appear here as lobby content, not as a claim about where your data sits.

  • Third-party services

    A payment app, a bank or a link that leaves our pages runs on someone else's notice. We cannot answer for how they store what you type there. Read their page first, then come back to us if something looks wrong on our side.

YOUR MOVES

Four Actions You Can Take Yourself

You do not need to write a formal letter to get something changed. Sign in, open your profile and correct the name, mobile number or email shown there — a payment reference that no longer matches is the usual reason a transfer query stalls. If you want to see what we hold, ask through a published support route and tell us which period you care about; the transaction records on your account already show most of it. Where a detail cannot be edited from the profile, tell us what is wrong and we will say what we can adjust. You can also ask us to close the account, and we will explain what stays on file afterwards for record-keeping under the law that applies to you. Availability of these actions depends on local law and eligible regions. Nothing on this page is a promise about timing — ask, and we will point you to the route that handles it.

  • Look through your records

    Signed in, your account lists the transfers you sent, the direction and the reference attached to each one. That is usually enough to settle a question without writing in at all. Open it before you report a missing payment, and note the date and amount.

  • Fix what you can edit

    Name, mobile number and email live in your profile, and you can change them yourself. Keep them current — a payment reference that no longer matches the profile is the common reason a query drags on. For anything you cannot edit, ask us.

  • Ask us plainly

    Write through the support page, name the period you are asking about and say what you want changed. We will tell you what we can do under the law that applies to you, and what sits with a wallet or bank instead of with us.

  • Close the account

    You can ask us to close your account, and we will explain what drops away with it. Some transaction records stay on file for the period the law in your region sets, and we will say which ones rather than leaving you to work it out.

REACHING US

Reaching the Team About a Privacy Question

Questions about this policy go through the same door as any other account question: the support page linked from our footer and from the signed-in account area. We do not run a separate privacy mailbox that nobody watches, so use that route and put the word privacy in your message so it lands with the right person. Give us the email on your account, the date you are asking about and any payment reference from a bKash, Nagad or Bank Transfer — that lets us find the record instead of trading messages. If your question is about something a wallet or bank did, tell us first, because we may only be able to point you back to their record. Reporting a login you do not recognise should come before anything else. Keep your password out of the message. We answer through the same route you wrote in on, and if we need more we will ask on that thread rather than through a link in an unexpected message.

  • Support page form

    The support page linked in our footer carries the form we answer. Put privacy in the subject line, add the email on your account and the date you are asking about, then paste any payment reference. One clear message saves a whole round of follow-up questions.

  • Signed-in account area

    Sign in and use the help route inside your account when the question touches a transfer or your profile. The page already knows which account you are on, which shortens the check on our side. Keep your password out of the message itself.

  • Payment app help desk

    If a bKash, Nagad or Bank Transfer looks wrong on the wallet side, raise it there as well. We hold our record of the reference; the money movement sits on their books. Bring both answers together and the picture is complete.

DATA HANDLING

How We Hold Records and Protect Logins

Your data handling on gd2go is deliberately plain. Cookies are used to keep you signed in and to remember the language and layout you picked, and you can clear them from your browser at any time — you will simply sign in again. Account security starts with your password and the device you use, so set one you do not reuse on a payment app, and sign out on a phone you no longer carry. We keep transaction records for as long as the law that applies to you requires, and we do not strip them early just to tidy a list. Access to those records is limited to the people answering your question. If something looks wrong on your account, report it through support before you send another transfer. Retention periods and the exact rights you hold differ by region, so ask and we will tell you what applies to you rather than quoting one blanket rule.

  • Cookies and your session

    A small cookie keeps you signed in between pages and stores the language and layout you picked. Clearing your browser wipes it, and the next visit starts with a fresh sign-in. We do not use it to build a profile you cannot see. Ask us what is set.

  • Account security steps

    Set a password you do not use on bKash, Nagad or your bank, and sign out on a phone you are handing on. If you spot a login you do not recognise, report it through the support page before you send another transfer. Change the password from the profile screen.

  • How long records stay

    Payment records and the references tied to them stay on file for the period the law in your region requires. We do not shorten that to keep a list tidy, and we do not extend it beyond what the rule asks. Ask which period applies to you.

  • Changing what we keep

    You can correct the profile fields yourself and ask us about anything you cannot edit. Requests that touch a payment record are checked against the reference you give us. Say which period and which transfer you mean, and the answer arrives faster.

COMMON QUESTIONS

Questions We Get About Account Data

The six questions below are the ones that reach our support page most often, and each answer points at a real route rather than a slogan. If your question is about a payment you already sent, keep the reference ready before you write in — it is the difference between one message and five. If it is about what we hold on file, ask plainly and say which period you mean; we can then tell you what applies under the law in your region rather than guessing. Availability of the service itself, including which payment rails work for you, depends on local law and eligible regions, so a yes for one reader is not automatically a yes for another. Anything not covered here goes to the support page linked in our footer. We update these answers when a route on the site changes name or moves, so the wording here stays aligned with the account area you actually use.

Does gd2go share my bKash number with anyone?

We use the number you register to reach you about your account and to match a payment you send. Sharing is limited to what a payment rail or the law needs in order to process a transfer, and we do not sell contact lists. Ask through support if you want to know what applies to your case.

What can I see about my own account?

Signed in, you can read your profile details and the transaction records attached to your account, including the reference on each bKash, Nagad or Bank Transfer. Anything older than the period shown there needs a support question, because retention rules decide what is still on file.

Do you keep my bank details on file?

We keep the reference that connects a Bank Transfer to your account, not your banking login. The bank holds the account relationship and its own notice covers that side. If a page ever asks for your bank password, stop and tell us through the support page.

How do I close my account, and what stays behind?

Ask through the support page and we will explain the steps before anything changes. Some transaction records have to stay for the period the law in your region sets, and we will say which ones rather than leaving you to guess at it.

Do cookies change what I see in the lobby?

A cookie remembers your sign-in, language and layout, so the lobby opens the way you left it. It does not decide which titles are available — eligible regions and local law do that. You can clear cookies from your browser whenever you like.

Who do I tell if I think someone else used my account?

Report it through the support page straight away and change your password from the profile screen. Do not send another transfer until the account has been checked. Tell us the device and the time you noticed, so the record can be matched.