Jaya9 Privacy Policy for Bangladesh Users
| Area | What May Be Involved |
| Details provided by the visitor | Registration, contact and profile details |
| Account activity | Sign-ins, settings, games, bets and transaction history |
| Technical records | Device, browser, IP address and page activity |
| Main purposes | Account operation, payments, support and security |
| Cookies | Session, preference and performance-related technologies |
| External recipients | Payment, hosting, verification or technical providers where needed |
| Storage | Depends on the record, purpose and applicable requirements |
| Protection | Access controls, monitoring and other technical measures |
| Individual rights | Access, correction, deletion or restriction where applicable |
| Requests | Submitted through the available contact form |
What This Notice Covers
Different types of interaction can involve different records.
Simply opening a page may generate technical logs. Registering can involve profile details. Deposits and withdrawals create transaction records, while a message sent to support contains whatever the sender chooses to include.
The same applies when someone:
- signs in to an existing profile;
- uses casino or sports sections;
- changes available settings;
- completes a financial operation;
- sends a question or complaint.
An outside payment service, embedded feature or linked website can have its own rules. Once a visitor moves to another provider, that provider’s notice may also apply.
Details That May Be Provided Directly
Not every visitor provides the same information. What is requested depends on the action being completed and the current interface.
Registration and Profile Details
When creating or maintaining a profile, a person may be asked for details such as a name, date of birth, phone number, email address, username, country or other profile fields.
This does not mean every field is required in every case. The registration form shown at the time should be treated as the relevant source.
Accuracy matters. Incorrect contact details, for example, can make later account recovery or verification more difficult.
Identity Checks
In some situations, additional verification may be requested to confirm identity, age, address or ownership of a payment method.
Depending on the circumstances, this could involve:
- an identity document;
- a photograph or other identity check;
- proof of address;
- evidence connected with the chosen payment route.
Such material should only be sent through the secure process specifically provided for verification. A password or one-time security code should never be placed in an ordinary message simply because someone asks for it.
Payments and Transactions
Financial activity creates records of its own. These can include the amount, BDT or another currency shown for the profile, date, status, chosen payment route and transaction reference.
A payment provider may process additional details under its own privacy rules.
It should not be assumed that the platform itself stores a complete bank-card number, CVV or secret payment credentials merely because a transaction takes place.
Gaming and Account Activity
Use of casino or sports sections can create an activity history.
Examples may include bets or games played, stake amounts, promotional activity, account access, settings changes and records related to disputed transactions.
Such records can be relevant when maintaining an account, checking a payment or reviewing suspected misuse.
Technical Details Collected During a Visit
Some records can be created automatically when a browser or mobile device connects to an online service.
They may include:
- IP address;
- browser and operating system;
- device type;
- selected language;
- pages visited;
- approximate location derived from technical signals;
- time of access;
- source that led to the page.
An IP address or similar technical signal does not always reveal someone’s exact physical location.
Logs and Troubleshooting
Technical logs are useful for more than visitor statistics.
They may help investigate a page that repeatedly fails to load, identify unusual access attempts or understand why a particular feature is not working properly.
They can also support fraud and security reviews without requiring every technical check to be performed manually.
Why Personal Details May Be Used
The reason for processing depends on what the person is trying to do.
| Purpose | Why It May Be Needed |
| Create and maintain a profile | To recognise the account and retain relevant settings |
| Provide core functions | To make available the sections linked to that profile |
| Process transactions | To record and verify deposits or withdrawals |
| Verify identity | To check age, identity or payment ownership where required |
| Answer enquiries | To understand a question and provide a response |
| Prevent misuse | To review suspicious behaviour or rule violations |
| Maintain the service | To diagnose faults and improve page performance |
Account Services
Profile details can be used to recognise a returning visitor, keep available preferences and display account-related records such as transaction history or balance information.
The precise functions depend on the current service.
Deposits and Withdrawals
A financial request normally needs enough detail to identify the transaction and confirm where it belongs.
Verification may also be necessary when an operation looks unusual or when ownership of a payment route needs to be checked.
Fraud and Abuse Checks
Technical and account records may help identify suspicious sign-ins, duplicate profiles, unusual payment behaviour or attempts to bypass platform rules.
Automated tools can assist with these checks, but their use should not be taken to mean that every final account decision is necessarily made by a machine.
Cookies and Similar Technologies
Cookies are small files or identifiers that help a website remember a browser or session.
Some are needed for basic operation. Others may help retain preferences or understand whether pages are working as expected.
Typical categories can include:
- essential cookies for sessions and core functions;
- functional cookies that remember selected preferences;
- analytics or performance technologies used to understand page behaviour.
Specific advertising technologies should not be assumed unless the current service confirms their use.
Managing Cookies
Most browsers allow people to delete existing cookies or limit new ones.
Blocking them can have practical consequences. A visitor may need to sign in again, saved settings can disappear, and some pages may stop working correctly.
There should be no assumption that a separate cookie-control centre exists unless one is actually available.
Service Providers and Outside Companies
Running an online platform can involve outside companies.
Depending on the task, a limited amount of relevant information may be processed by providers involved in:
- payments;
- hosting or infrastructure;
- technical support;
- identity checks;
- analytics;
- fraud prevention or security.
Only what is needed for the relevant function should be shared.
Payment Providers
When a person selects an external payment method, that provider may receive and process transaction details under its own conditions.
Before making a payment, it is worth reading the provider’s privacy notice rather than assuming that the rules are identical to those of the platform.
Verification and Security Services
External systems can sometimes assist with identity, age or document checks and with reviewing suspicious activity.
That does not mean the same provider or check is necessarily used for every account.
Disclosure for Legal or Security Reasons
There are circumstances in which records may have to be disclosed outside normal service operations.
For example, disclosure may be required following a valid request from an authorised body or when necessary to investigate fraud, protect users or defend legal rights.
For that reason, no responsible privacy notice should promise that personal details will never be disclosed to authorities under any circumstances.
Processing Across Borders
Technical companies involved in hosting, payments or support may operate from different locations.
As a result, some processing can potentially take place outside the country where the visitor lives. Appropriate safeguards should be used where cross-border handling requires them.
No particular country or legal transfer mechanism should be assumed unless the current service identifies it.
How Long Records May Remain
There is rarely one suitable retention period for everything.
A short-lived technical log and a record connected with a disputed financial transaction serve very different purposes.
Retention may depend on:
- the type of record;
- whether the profile remains active;
- transaction history;
- security concerns;
- an unresolved complaint;
- applicable obligations.
Closing an account therefore does not necessarily mean every associated record disappears immediately. Some material may need to remain available for fraud prevention, dispute handling or another legitimate requirement.
Keeping Personal Details Safer
No online service can reasonably promise that security risk is zero.
Possible protective measures can include restricted access, account checks, session monitoring and safeguards around the transmission of sensitive material.
Users also have a role.
Do not share a password or one-time code. Keep the device protected, sign out when using a shared computer and pay attention to unexpected changes to the profile.
If an unfamiliar sign-in or account change appears, report it through the available contact route as soon as practical.
Privacy Rights
Depending on the circumstances and applicable requirements, an individual may be able to request access to personal records or ask for them to be corrected.
Other possible rights can include:
- requesting deletion of certain records;
- asking for processing to be limited;
- withdrawing consent where consent was the basis for an optional activity;
- requesting clarification about how personal details are handled.
The availability of a particular right can depend on the situation.
Correcting Details
Some profile fields may be editable directly through account settings.
If a field cannot be changed there, a request can be submitted using the contact form. Verification of ownership may be required before a change is made.
Deletion Requests
A person can ask whether certain records can be removed or whether an account can be closed.
Deletion is not always immediate or absolute. Records connected with security, fraud prevention, financial disputes or other applicable obligations may still need to be retained.
Withdrawing Consent
Consent given for an optional activity, such as some promotional messages, may be withdrawn where that option is available.
Withdrawal does not undo processing that was already legitimately completed before the request.
Marketing Messages
Promotional or informational messages may be sent where the individual has selected the relevant option or otherwise provided the required permission.
Available settings or the contact form can be used to request that optional communications stop.
Opting out of marketing should not automatically be interpreted as a request to close an account.
Minors
Gambling services are not intended for people below the applicable minimum age.
If an account is found to belong to someone who does not meet the required age conditions, access may be restricted and the associated records handled according to the platform rules and applicable requirements.
A specific age should not be assumed unless it is stated in the current service conditions.
Links and Embedded Services
A page may contain links or components supplied by another company.
Once a visitor moves to an external resource, its own privacy notice can determine how information is handled there. The presence of a link does not mean that Jaya9 or this informational site controls the outside provider’s practices.
Messages Sent Through the Contact Form
When someone submits an enquiry, the information entered in that form may be used to understand and answer the request.
A message could contain a name, contact details, subject, account identifier, description of the problem or an attachment supplied by the sender.
Do not place the following in an ordinary text field:
- passwords;
- one-time authentication codes;
- CVV numbers;
- complete payment-card details;
- credentials for a bank or payment account.
If documents are genuinely required for verification, follow only the instructions provided through the appropriate protected process.
Privacy Requests
Questions about personal records, correction or deletion can be submitted through the contact form.
A useful request should explain what the person wants reviewed and provide enough information to locate the relevant profile. This might include the registered contact detail or account identifier where appropriate.
Before releasing or changing personal records, verification may be necessary. This helps prevent somebody else from requesting access to an account they do not own.
A password or security code should never be submitted in the message simply to prove ownership.
Changes to This Page
Privacy practices and site functions can change. This document may therefore be revised when processing methods, available features or applicable requirements change.
Visitors who return after some time should review the current version rather than rely indefinitely on a saved copy.
Last updated: September 2, 2026