Slots / Casino
6jeta9 collects only the account data needed to run your sessions, process wallet transactions through Nagad and Rocket, and keep your account secure. What we collect, why we keep it, and how you can act on it — this page covers all of that, with access subject to your local law and eligible regions.
When you create an account on 6jeta9, we collect the details you enter directly — your name, contact information, and the wallet identifiers you use to transact, such as your Nagad or Rocket mobile number. We also collect session data automatically: device type, browser version, pages visited, and interaction timestamps. This data is used strictly to operate your account, process your wallet activity, and detect any unusual access patterns that could put your account at risk. We do not sell your personal information to third parties. Data shared with payment processors — including Nagad and Rocket — is limited to what those processors need to complete your transaction and nothing beyond that. Retention periods follow what is operationally necessary and what applicable law in eligible regions may require. If you are accessing this site from Bangladesh, local legal requirements may govern how your data is handled alongside our own policy. Where those requirements are stricter, we apply the stricter standard. This policy applies to all interactions with 6jeta9 through browser or mobile access. It does not extend to any third-party sites linked from our pages.
This policy governs data collected directly through your 6jeta9 account — from registration through active sessions. It does not extend to any site or service that 6jeta9 does not operate, even if you reach that service through a link on our pages. Understanding the boundary helps you know exactly where our obligations to you begin and end.
Covers all data you submit when creating or updating your 6jeta9 account, including login credentials, contact details and wallet references linked to Nagad or Rocket transactions.
Transaction records processed through supported local payment methods are held within your account history. We share only the minimum required fields with the payment processor to complete each transfer.
Browsing behaviour, game session data and device identifiers collected while you use 6jeta9 fall inside this policy. This data informs account security checks and session continuity — not third-party advertising.
Any external site, app or service not operated by 6jeta9 sits outside this policy. If you follow a link away from our pages, the destination's own privacy terms apply from that point forward.
You have practical options for how your data is managed on 6jeta9, and each one is accessible through your account or through our support route. Reviewing what we hold is the starting point: your account area shows the contact details, wallet references and session history tied to your profile. If something is incorrect — a contact number, a wallet ID linked to Nagad or Rocket, or a name field — you can request a correction by contacting support with the specific detail and the change you need. If you want to understand why a particular piece of data is held, or how long it will be kept, that question goes to the same support route and we will respond with the relevant context. Account closure requests are also handled through support; we will confirm what is deleted, what is retained for legal or operational reasons, and the timeline for each. Eligibility for some of these actions may depend on your location and applicable local law in Bangladesh or the eligible region you access from.
Your account area displays stored contact details, wallet references and recent session activity. Check there first before raising a data query with support.
If your Nagad number, Rocket wallet reference or contact information is wrong, contact support with the current value and the correct one. We process corrections once identity is confirmed.
Questions about why data is held, how long it is retained, or who it is shared with can be sent to support. We aim to give a clear, specific answer based on your account context.
Support handles account closure requests. We will tell you what is removed, what must be kept under applicable rules, and the timeline — so there are no surprises after the request is made.
If this policy raises a question you cannot answer from your account area, our support team is the right next step. Use the channel that suits how you prefer to communicate — all three routes below reach the same team responsible for account and privacy queries.
Open the chat widget from any page while signed in. State that your query is about account data or this privacy policy so it is routed to the right team from the start.
Send your privacy or data query to our published support email address. Include your registered contact detail — not your password — so we can locate the correct account record.
The help section inside your signed-in account area contains published policy routes and common answers. Check there first; if your question is not covered, escalate through live chat or email.
Our data practices are shaped around what your account actually needs — not broad data collection for its own sake. Cookies are used to maintain your session state and remember your signed-in status across pages; they are not used to build advertising profiles. Account security checks run against session metadata to flag access patterns that do not match your usual behaviour, such as a new device or an unfamiliar network. Retention follows a practical rule: we keep data for as long as your account is active and for whatever period applicable law in eligible regions requires after closure. We do not retain data beyond those boundaries. If our handling practices change in a material way, we update this page and the change date is visible at the top of the policy.
Session cookies keep you signed in and preserve your account state between pages. We do not deploy advertising or behavioural tracking cookies that share your data with external ad networks.
Session metadata — device type, login timestamps, access location — is checked against your account history. Unusual patterns trigger an additional verification step before access continues.
Your data is held for the duration of your active account plus any period required by law in eligible regions after closure. Once those periods pass, account data is deleted or anonymised.
When this policy changes in a way that affects your rights or how your data is used, we update this page. The revision date at the top of the policy tells you when it was last changed.
These are the questions we hear most often about data handling on 6jeta9. If your question is not here, the support routes listed earlier on this page are the right next step.
We collect the contact details you enter at registration — name, email or phone number — along with the wallet references you link, such as your Nagad or Rocket mobile number. We also collect session data automatically, including your device type and browser version.
Your wallet number is shared only with the relevant payment processor — Nagad or Rocket — to the extent needed to complete your transaction. It is not passed to any other third party, and it is not used for advertising or profiling purposes.
After your account is closed, we retain only what applicable law in eligible regions requires us to keep. Data that is not covered by a legal retention requirement is deleted or anonymised. We will tell you the specifics when you make a closure request through support.
Yes. Contact support with the detail that needs correcting — for example, a phone number or wallet reference — and the correct value. We will update the record once we have confirmed your identity through the standard account verification step.
Yes, and if local law in Bangladesh sets stricter requirements for how your data is handled, we apply those stricter requirements. Access and eligibility remain subject to your local law and the eligible regions this service covers.
Use live chat from any signed-in page, or send an email to our published support address. State clearly that your query relates to your data or this privacy policy so it reaches the right team without delay.