App / Live
bdjji collects and uses your information only to run your account, process transactions through payment rails like bKash and Upay, and keep the platform working correctly for you. Access to this platform and its data practices depends on your local law and eligible region.
When you open an account on bdjji, we collect the information you provide during registration — your name, contact details and login credentials. When you make a deposit or withdrawal using bKash, Upay or Bank Transfer, we receive transaction reference data from the payment rail sufficient to confirm and record the movement. We do not store your full wallet PIN or bank credentials on our servers. We also collect device and session data — browser type, IP address range and navigation path — to detect unusual account activity and maintain session security. This data is not sold to third parties. It is used internally to operate your account, respond to support requests and comply with obligations that apply in your eligible region. Cookies help us remember your session preferences and keep you logged in across page loads. You can adjust cookie settings through your browser, though some functions may not work without them. If you deposit via Nagad or Rocket, the same transaction-reference approach applies. How long we retain your records depends on applicable local law and the type of data involved.
This policy covers your bdjji account and the data generated when you use it — including sports betting markets, casino categories and wallet transactions. It does not extend to third-party websites linked from our pages, and it does not govern how payment processors like bKash or Upay handle your data on their own platforms. Review each provider's own policy for that detail.
All data collected when you log in, navigate the lobby or update your profile falls inside this policy. This includes session tokens, login timestamps and any account preference you set while signed in.
Deposit and withdrawal records processed through bKash, Upay, Nagad, Rocket or Bank Transfer are covered here. We hold transaction references, not full payment credentials. The payment provider's own policy governs their side.
How we serve pages, track navigation flow and use session cookies is inside this policy's scope. We use this data to improve usability and to detect sessions that look irregular or unauthorised.
External sites, game studio platforms or payment apps you open from a bdjji link are outside this policy. Once you leave bdjji, their data terms apply. We do not control or represent those practices.
You have a set of practical options when it comes to the data bdjji holds on your account. These are not abstract entitlements — they are steps you can start from within your account or through our support channel. You can ask us to confirm what personal data we hold, request a correction if your contact details are wrong, or raise a question about how a specific piece of information was used. Deletion requests are considered where they do not conflict with record-keeping obligations that apply under local law. If you believe your account data has been handled incorrectly, the right route is to contact our support team directly with your account reference. We aim to acknowledge every written data query and respond substantively. Eligibility to exercise these rights may depend on the regulations that apply in your region. Do not share your login password when raising a data query — we will never ask for it through any support channel.
Open the account settings page to see the profile information we hold. For a fuller picture of what data is linked to your account, send a written request through our support contact.
If your name, contact number or linked payment detail is recorded incorrectly, update it in the account settings section or ask support to correct it with your account reference ready.
For questions about how a specific piece of data was collected or used, contact us via the support route listed on this page. Include your account reference so we can locate your records quickly.
If you want to understand how long we keep a particular type of record, or if you want to request deletion where that is permitted under applicable local law, send that request in writing to our support channel.
For any privacy-related question, the routes below are the ones published on this site. We do not operate undisclosed support channels, and we will not ask for your account password through any of them. Have your account reference ready when you get in touch — it helps us locate your data record without delay.
Open the chat widget visible in the bottom corner of any signed-in page to raise a privacy or data question. Keep your account reference to hand so the team can pull your record.
Send a written data query to the support email address listed in the contact section of the site. Written requests are useful for deletion queries or formal data-access requests.
The help centre on bdjji contains published answers to common privacy and account data questions. Check there first — if your question is not covered, escalate via chat or email.
Our approach to data is operational rather than promotional — we collect what is needed to run your account and no more. Here is how each area works in practice.
We use cookies to keep your session active, remember display preferences and measure which pages are visited most. You can block or clear cookies in your browser settings, though logging in and some navigation features depend on them being enabled.
Login sessions are protected with standard token-based authentication. If we detect an unusual login pattern on your account — a new device or an unfamiliar location — the account may be flagged for verification. We do not store or transmit your bKash or Nagad wallet credentials.
How long we keep your account records depends on the category of data and the obligations that apply in your eligible region under local law. Transaction records linked to bKash, Upay or Bank Transfer are held for the period required by applicable rules.
When this policy changes in a material way, we note the update on this page. Continuing to use your account after a change is posted means you have seen the updated terms. For significant changes, we may also place a notice in the signed-in account area.
These are the questions we receive most often about how bdjji handles your personal data, what rights you have and how to act on them.
We do not sell your personal data. We share limited information only with payment processors — such as bKash or Upay — to complete a transaction, and with service providers who operate systems on our behalf under confidentiality obligations. We do not share data with advertisers.
We receive a transaction reference from the payment rail to confirm the deposit and update your account wallet. We do not store your bKash or Nagad wallet PIN, full account number or banking credentials. The payment app's own privacy policy governs what they record on their side.
Yes, you can request deletion of personal data we hold. We review each request against local law obligations — some transaction records must be retained for a set period regardless. Submit your request in writing via the support email with your account reference included.
Open your account settings page to update contact details directly. If the field is locked or the correction involves identity information, contact support via live chat or email with your account reference. We will verify the change before updating the record.
Access to bdjji and the rights available under this policy depend on your local law and eligible region. If your region is not supported, you may not be able to open or maintain an account. We do not make legal representations about eligibility in specific jurisdictions.
We update the text on this page when the policy changes. For material changes, we may place a notice in the signed-in account area so you see it on next login. The continued use of your account after a posted change indicates you have reviewed the updated version.