Casino / App
At 33 ayat, this Privacy Policy sets out exactly what account and transaction data we collect, how we use it, and what choices you have over it. Access to and use of this site depends on your local law and eligible regions.
This policy applies to personal information you provide when you open an account, make a deposit or withdrawal, or contact us for support. The categories of data we may hold include your registered name, contact details, account login credentials, and transaction records — including payment activity processed through bKash, Upay, and Bank Transfer. We collect this information to operate your account, process transactions, verify your identity where required, and respond to support requests. We do not sell your personal data to third parties for marketing purposes. Where we share data with payment processors or technical service providers, we do so only to the extent needed for those specific functions. We retain transaction records for as long as required to fulfil our obligations and respond to account queries — the specific retention period applicable to your account is visible in your account settings. Your use of this site and the scope of applicable data rights depends on your local law and the eligible regions from which the site can be accessed. If you access this site from outside an eligible region, we cannot confirm that local data-protection law applies in the same way.
Not every data interaction on the site falls under the same rules. Some parts of your experience involve third-party services — payment processors, game content studios — that operate under their own policies. Understanding the boundary helps you know when to look here and when to check elsewhere.
This policy covers all data collected when you register, log in, or update your account on 33 ayat. That includes the contact details, credentials and preferences stored against your account profile in our system.
Deposit and withdrawal records processed through bKash, Upay or Bank Transfer fall within this policy. We hold transaction references for account management purposes; the payment provider's own policy governs data on their side of the transfer.
Pages and game content you browse on the site generate session and usage data that we handle under this policy. We use this to keep the site functioning correctly — not to build marketing profiles sold to external parties.
Game studios and external payment processors are not covered by this policy. When you interact with a third-party service — such as completing a bKash transaction on their interface — that provider's own privacy terms apply to data they receive.
Your account gives you several concrete paths to act on this policy — not just read it. To review what information we hold, log in and open the account details section; your profile data, registered payment methods and transaction history are displayed there. If any account detail is incorrect — a name spelling, a contact number, a payment reference — you can correct it from the same section or raise a correction request through the support route below. Transaction records tied to bKash, Upay and Bank Transfer activity are listed in your account history and can be referenced when you contact support. If you have a question about how a specific data item is used, or you want to request that we close your account and handle your data accordingly, submit that request in writing through the published contact path. We aim to acknowledge written data requests and provide a substantive response within a reasonable period, though the exact timeframe may depend on the nature of the request and applicable regional requirements.
Log in and open the account details page to see your stored profile information and transaction history, including payment records from bKash, Upay or Bank Transfer.
Update an incorrect name, phone number or contact email directly in account settings. For records you cannot edit yourself, submit a correction request through the support contact route.
If you are unsure how a particular piece of information is being used, put your question in writing and send it via the published support contact. We will respond with a specific answer, not a generic acknowledgement.
A written closure request submitted through the support contact initiates the account review process. We will confirm what happens to your data upon closure and any retention obligations that apply under this policy.
If this policy raises a question you cannot resolve by reading it, use one of the contact routes below. Describe the specific data or account item your question concerns so we can give you a direct answer rather than a general response. All privacy-related requests are handled through the same routes we use for account support.
Open the chat widget on the site to raise a privacy question in real time. Reference the specific account detail or transaction record your question concerns.
Send a written data or privacy request to the support email address published in the site's contact section. Written requests create a documented record for your query.
Log in and navigate to the help section inside your account to find the published contact form and links to privacy-related policy documents.
We approach data handling as a practical account obligation, not a formality. Every policy measure described here is designed to keep your information accurate and accessible to you while limiting unnecessary data exposure.
We use cookies to keep your session active and to remember account preferences between visits. You can review and adjust cookie permissions through your browser settings; disabling certain cookies may affect how parts of the site function.
Access to your account data is controlled by your login credentials. We recommend keeping your password confidential and not sharing account access. If you suspect unauthorised access, contact support through the published route immediately.
We retain account and transaction records — including bKash, Upay and Bank Transfer history — for as long as needed to operate your account and meet applicable obligations. The retention period for your account is visible in your account settings.
When this policy changes in a material way, we will note the update date on this page. Continued use of your account after a policy update indicates that you have read the revised version. Check this page periodically if you want to stay current.
These questions come up most often when account holders read through the policy. If your question is not covered here, use the support contact routes listed above to submit it in writing.
We collect the details you enter during registration — name, contact information and login credentials — plus transaction data generated when you use bKash, Upay or Bank Transfer. We do not collect data beyond what is needed to run your account and process your transactions.
Yes. Log in and open the account details section to view your profile information and transaction history. If something is missing or looks incorrect, raise it through the support contact route and we will check the underlying records.
We share data only with payment processors and technical service providers who need it to perform specific functions — such as completing a bKash or Bank Transfer transaction. We do not sell account data to external parties for marketing use.
Open account settings while logged in and update the field directly. For details you cannot edit yourself — such as a transaction reference — submit a written correction request through live chat or the support email. We will confirm the correction once it is applied.
Retention periods depend on the type of record and applicable regional requirements. Your account history section shows the records currently held. For a specific retention question about a payment processed via bKash, Upay or Bank Transfer, submit a written query through the published support contact.
Submit a written closure request through the support contact. We will confirm which records are deleted, which are retained under applicable obligations, and the timeline for each. Retention of transaction records may be required regardless of closure, depending on your eligible region.