Live / Slots
At 29h, your account data belongs to you — and this policy sets out exactly how we collect it, how we store it, and what choices you have over it. Access to this platform and its services depends on your local law and eligible regions.
When you open an account with us, we collect the details you submit during registration — your name, contact information, and the payment identifiers linked to your wallet or bank. If you transact through bKash, Upay or Bank Transfer, the reference data from those transactions is retained as part of your account ledger. We do not share that ledger with third parties for advertising purposes. Cookies and session tokens are used to keep you signed in and to track how pages load on your device — not to build a profile for sale. You can clear cookies from your browser at any time; doing so will sign you out of the current session. Data we hold is stored with access controls in place. Staff access to your account record is limited to what is needed to answer a support query or verify a transaction. We do not retain payment credential details such as full card numbers or wallet PINs. This policy applies where use of 29h is permitted under local law. If you are in a region where access is restricted, your eligibility to use the platform — and the rights described here — depend on the rules that apply in your location. For questions about how your data is held, use the contact route listed in the support section below.
This policy covers data 29h collects and processes directly. It does not govern third-party services linked from our platform, and it does not override local law in your region. Review each area below to understand what falls inside and outside our data obligations.
Data you enter when logging in or registering — email, contact details, password hash — is covered. We process this to authenticate your session and maintain your account record.
Payment references from bKash, Upay and Bank Transfer are stored within your account wallet history. These records are covered by this policy and are not shared with unrelated third parties.
Page-load analytics and session behaviour on 29h are collected to improve site performance. This data is aggregated and does not identify you individually in our reporting.
External links, payment gateways and game content studios operate under their own data terms. Once you leave 29h or interact with an embedded third-party frame, this policy no longer applies.
You have real actions available to you — not just abstract rights listed in a document. If you want to see what data we hold on your account, you can submit a data access request through our support contact route. We will respond with a summary of the account record we hold, including your registration details and the transaction references linked to your wallet history. If any detail is incorrect — a contact number, an email address, a name mismatch — you can raise a correction request through the same route. We will update the record once we have confirmed your identity through the verification step shown in your account. You can also ask us to delete data that is no longer required, subject to any retention obligation we hold under applicable law. What we are required to keep for financial record purposes — such as bKash or Bank Transfer references — stays in the ledger until the retention period expires. For everything else, a deletion request is handled through support.
Submit a data access request via the support contact route to receive a summary of what we hold on your account, including registration and transaction reference data.
If your name, contact number or email on file is wrong, raise a correction request. Identity verification through your account is required before we update the record.
You can ask us to remove data that is no longer necessary. Retention obligations for financial records such as bKash and Bank Transfer references may delay or limit full deletion.
Any question about how this policy applies to your account can be directed to our support team. We aim to respond with a clear, specific answer rather than a generic acknowledgement.
If you have a question about this policy, a data request or a concern about how your information is handled, use the contact routes published on this site. We do not publish contact details that are not actively monitored.
Open the chat window from any page on 29h. Describe your privacy query and a support agent will handle it directly — this is the route for urgent account data questions.
Send your data access, correction or deletion request to the support email address listed in your account dashboard. Include your registered contact detail so we can verify your identity.
The account help section inside your signed-in profile lists the policy contact path and shows the current status of any open support query you have submitted.
Data security on this platform is handled through access controls, session management and limited staff visibility into account records. Here is what that means in practice for your account.
Session cookies keep you authenticated during your visit. They expire when you log out or close the browser. You can clear them at any time through your browser settings without losing your account data.
bKash, Upay and Bank Transfer reference numbers are stored in your account ledger for record-keeping. Full wallet credentials and bank account numbers are never stored on our side.
Account records are only accessible to staff responding to a specific support query. Access is not open across the team. Any access to your record is tied to an active query or verification step.
When this policy changes in a material way, we post a notice in the account area. Continuing to use the platform after a notice is posted means you have seen it — check the account section regularly.
These are the questions we hear most often about how 29h handles your account data. If your question is not here, use the support contact route described above.
We collect the name, email address and contact number you provide at registration. If you add a payment method such as bKash or Bank Transfer, the reference identifier for that method is linked to your account record — not the full credential.
We do not share your account data with third parties for advertising or marketing. Data may be shared only where required by applicable law or to process a transaction through a payment rail you have chosen, such as bKash or Upay.
Submit a data access request through the support email or live chat route published on the site. Include your registered contact detail so we can confirm your identity before sending the account record summary.
Yes, for data that is not subject to a retention obligation. Transaction references from bKash and Bank Transfer are kept for a period required by financial record rules. For other data, raise a deletion request via support and we will confirm what can be removed.
Availability and your data rights under this policy depend on your local law and eligible regions. If access to the platform is restricted where you are, that restriction also affects the scope of rights described in this policy.
Contact support via the chat or email route and raise a correction request. You will need to pass the identity verification step shown in your account before we can update the detail — this protects your record from unauthorised changes.