Casino / Slots
gh6681 collects only the account and transaction data needed to keep your session secure and your wallet activity accurate. This policy tells you exactly what we hold, why we hold it, and how you can review or correct it — with access subject to your local law and eligible regions.
When you open an account, we collect the registration details you enter — name, contact address and the mobile wallet identifier you use for transactions such as bKash, Rocket or Upay. We also record session data: the device type, browser version and IP address associated with each login. This helps us recognise your device on a return visit and flag any access that looks out of place. Transaction records — amounts moved through your wallet, timestamps and reference numbers — are retained for account accuracy and dispute handling. We do not sell or rent this data to third parties for marketing. Cookies placed on your browser track navigation within the site only; they do not follow you to external domains. Where you use a local payment rail like Rocket or Upay, the wallet provider operates under its own privacy terms, which are separate from ours. Your use of this site and its data practices depends on your local law and the eligible regions in which access is permitted. If you are unsure whether access is lawful for you, check the terms applicable in your location before proceeding.
This policy covers activity that takes place directly on gh6681. It does not extend to third-party services you reach through links on the site, and it does not govern how payment providers such as bKash or Rocket handle data on their own platforms. Review each section below to understand what sits inside and outside our responsibility.
Login credentials, session tokens and device identifiers collected when you sign in are covered fully by this policy. We control how that data is stored, how long it is kept and who within our systems can view it.
Transaction reference numbers and wallet activity routed through your gh6681 account fall within our records. The mobile wallet provider — bKash, Rocket or Upay — maintains its own data record under its own published terms, which operate independently of ours.
Pages you visit, game lobbies you open and search terms you enter within the site are logged as navigation data. This data is used only to improve account flow and is not shared externally for advertising or profiling purposes.
External links, game studio platforms and any services you access outside gh6681 are outside the scope of this policy. Those services operate under their own privacy frameworks, and we do not control or represent them.
Your account area is where most data interactions start. You can view the registration details we hold by opening the account settings page after you log in. If a name, contact address or mobile wallet number is recorded incorrectly, the correction request goes through our support channel — not self-edited directly, so that changes are logged and confirmed. You can ask us what data categories we hold on your account, and we will provide a plain summary through the same support route. For questions about retention periods or a request to have data removed where permitted by applicable law, contact us in writing through the published email route. Response timing depends on the volume of requests we receive and the verification steps required to confirm your identity before we action anything. We do not action data requests from unverified contacts. Availability of these rights depends on your local law and the eligible region you access the site from.
Open account settings after login to see the registration data and wallet identifiers we hold. This view is read-only; submit a support request to flag anything that needs correction.
Name or contact errors are corrected through our support channel. Submit the request with your account reference so the change can be verified before it is applied.
You can request a plain summary of the data categories linked to your account. Send the request via the published email route and include your registered mobile wallet identifier for faster verification.
Where permitted by your local law, you may request deletion of account data. We will confirm receipt, verify your identity and explain which records can be removed and which must be retained for legal or operational reasons.
If you have a question about this privacy policy, a correction to request or a data query to raise, use the contact routes published on the site. We handle policy questions separately from general account support, so noting that your message relates to privacy will help us direct it correctly.
Send your privacy query to the support email address published in the site footer. Include your account reference and the specific data question so we can respond accurately without unnecessary back-and-forth.
The live chat widget on the site can be used to ask a policy question or to get the correct email address for a formal data request. Chat is not the channel for data deletion requests — those require written submission.
The Help section of your signed-in account lists the published contact routes for privacy and data queries. Start there to confirm which route applies to your question before submitting a request.
We apply access controls so that account data is visible only to the internal functions that need it. Session data is tied to your login and expires when you sign out or when the session times out on an inactive device. Cookie settings can be adjusted in your browser; disabling certain cookies may affect how the site navigates but will not block account login.
Account registration data and transaction records are kept for as long as your account is active and for a period after closure as required by applicable rules. We do not keep data longer than necessary for operational or legal purposes.
We use session cookies for login continuity and analytics cookies to understand how the site is navigated. You can review and adjust cookie permissions through your browser settings at any time without losing account access.
Each login creates a session tied to your registered device and wallet identifier. If we detect a login from an unrecognised device, we may ask you to confirm your identity through the verification step shown at that screen.
When this policy changes in a way that affects your rights or how we use your data, we publish the updated version on this page. Continuing to use the account after a change is posted means you have seen the revised terms.
Below are the questions we receive most often about data, account records and your rights under this policy. If your question is not covered here, use the support email route published in the footer.
We collect the name, contact details and mobile wallet identifier — such as your bKash or Rocket number — that you enter during registration. We also log the device type and browser associated with each login session for security purposes.
We do not sell or rent your data for marketing. Data may be shared only where required by applicable law or to process your wallet transactions through providers like Rocket or Upay, who operate under their own published terms.
Open account settings after you log in to view your registered details. For a full summary of the data categories we hold, send a request through the support email published in the site footer, including your account reference for verification.
Where permitted by your local law and eligible region, you can request data removal in writing via the published email route. We will verify your identity before actioning the request and explain which records must be retained for legal or operational reasons.
We place session cookies for login continuity and analytics cookies to track navigation within the site only. You can adjust or disable cookies through your browser settings; this will not prevent you from logging in to your account.
Transaction references routed through your gh6681 account are covered here. The wallet provider — bKash, Rocket or Upay — holds its own data record under its own privacy terms, which are separate from and independent of this policy.