Jaya9 Privacy Policy for Bangladesh Users

Privacy point	General approach
Data categories	Registration, contact, account, verification, payment, gambling, device and support information
Main purposes	Account operation, payments, verification, security, support and platform improvement
Information sources	The user, account activity, devices, payment providers and other service providers
Cookies	Essential, functional and analytical identifiers may be used
Possible recipients	Payment, hosting, verification, security and technical-service providers
Retention	Depends on account activity, transaction records, security needs and applicable requirements
Protection	Access controls, session checks, monitoring and protected submission channels may be used
User rights	Access, correction, deletion, restriction or consent withdrawal may be available
Changing details	Through account settings or a verified privacy request
Privacy requests	Submitted through the contact form with safe account-identification details

Information Covered by This Policy

This policy concerns information connected with:

• visiting public pages;
• creating and accessing an account;
• using casino games or sports-betting services;
• making deposits and withdrawal requests;
• activating promotions;
• communicating through the contact form.

The public Bangladesh page describes registration fields such as a username, password, currency, phone number and email address. It also refers to email activation and an account-verification section.

External payment services, games and linked websites may apply their own privacy terms. Users should review those policies when leaving Jaya9 or using a service operated by another provider.

Personal Information That May Be Collected

The information collected may depend on whether the person is only browsing, has registered an account or is completing a financial or verification process.

Data category	Possible examples	Why it may be needed
Registration data	Username, password, country, phone number and email	Creating and accessing an account
Profile information	Name, date of birth, address or preferred language	Maintaining accurate account details
Verification data	Identity document, photograph or proof of address	Confirming identity, age or payment ownership
Transaction data	Amount, BDT currency, method, date, status and reference	Processing and reviewing payments
Gambling activity	Games, bets, stakes, bonuses, results and history	Operating products and resolving disputes
Technical data	IP address, device, browser, operating system and page activity	Security, troubleshooting and performance
Contact-form data	Contact details, message, account ID and attachments	Reviewing and answering a request

Registration and Account Details

Users may provide profile and contact details when registering or updating an account. Not every possible field is necessarily required in every interface.

Information related to one account should belong to the account holder and remain current. When an editable field is unavailable, a correction request may be submitted through the designated contact process.

Identity Verification Information

Verification may involve an identity document, proof of address, photograph or evidence connected with a payment method. The platform’s public page describes uploading scanned documents through a Verification section in the profile.

Sensitive documents should be provided only through the protected interface specifically designated for verification.

Payment and Gambling Activity

Payment records may include the transaction amount, date, status, currency, selected method and reference number. This does not necessarily mean that Jaya9 stores complete bank-card numbers, payment passwords or other secret credentials.

Account activity may include:

1. casino games and round identifiers;
2. sports bets and accepted odds;
3. deposits and withdrawal requests;
4. bonus activation and wagering progress;
5. login and account-setting changes;
6. disputed operations and related messages.

These records may be needed to display account history, calculate results, review unusual activity and answer user enquiries.

Information Collected Automatically

When a person opens the site, technical information may be transmitted automatically. This can include an IP address, browser, device type, operating system, selected language, approximate region, visited pages, session time and referral source.

Approximate location data should not be treated as a guaranteed identification of the user’s precise physical address.

Device and Log Data

Technical logs may help identify page errors, failed login attempts, interrupted transactions, account-security risks and performance problems.

Such information may also be reviewed when an account is accessed from a new device or when activity differs significantly from the user’s normal pattern.

How Personal Data May Be Used

Personal information may be processed to:

• create, authenticate and maintain an account;
• display balances, settings and transaction history;
• provide access to games and sports markets;
• process deposits and withdrawal requests;
• confirm identity, age or payment ownership;
• investigate fraud, duplicate accounts or payment abuse;
• respond to contact-form submissions;
• apply platform rules and promotional conditions;
• diagnose errors and improve page performance.

These purposes do not imply that every category of information is used for every user.

Processing Financial Operations

Transaction and identity information may be needed to confirm that a request belongs to the account owner, check the payment details and investigate an unauthorised or disputed operation.

The Bangladesh-facing site currently lists BDT accounts and payment methods including bKash, Nagad, Rocket and bank transfer. The actual information processed may also depend on the privacy policy of the chosen provider.

Preventing Fraud and Account Abuse

Account, device, transaction and gambling data may be compared to identify suspected multiple accounts, unusual logins, fraudulent payments or attempts to avoid platform rules.

A technical warning or unusual pattern may lead to additional verification. It should not be presented as proof of wrongdoing without review.

Cookies and Similar Technologies

Cookies are small files or identifiers stored through a browser. They may help maintain a login session, remember settings and understand how pages operate.

Possible categories include:

• essential cookies, required for login, security and core functions;
• functional cookies, used to remember language or interface choices;
• analytical cookies, used to evaluate traffic and technical performance.

No specific advertising or analytics provider should be named unless its use is confirmed.

Managing Cookies

Users can usually remove or restrict cookies through browser settings. Blocking essential cookies may cause the site to forget the session, require another login or prevent certain pages from operating correctly.

The existence of a separate Jaya9 cookie-management centre should not be assumed unless one appears in the current interface.

Sharing Information with Service Providers

Limited information may be shared with companies that provide:

1. payment processing;
2. website hosting and technical infrastructure;
3. identity or document verification;
4. account security and fraud detection;
5. customer-support systems;
6. analytics and performance tools.

Only information reasonably required for the relevant task should be provided. A payment provider may process transaction details under its own privacy policy.

Data may also be disclosed when required by a valid request from an authorised body, when investigating suspected fraud or when necessary to protect users, accounts or platform rights.

International Processing and Data Retention

Technical or operational providers may be located outside Bangladesh. Information could therefore be processed in another country, subject to the safeguards and requirements applicable to the arrangement.

The storage period may depend on:

• whether the account remains active;
• the type and status of financial transactions;
• outstanding disputes or support requests;
• security and fraud-prevention requirements;
• obligations that continue after account closure.

Closing an account does not necessarily require the immediate deletion of every record. Some information may remain necessary for transaction review, dispute handling or prevention of repeated abuse.

Protecting User Information

Possible protective measures include restricted staff access, account verification, session control, activity monitoring and protected channels for documents or transactions.

No online system can promise complete security. Users also have an important role in protecting their information.

User Security Responsibilities

Users should:

• choose a unique password;
• keep one-time codes and recovery links private;
• use a secured and updated device;
• avoid logging in through unknown links;
• log out on shared computers or phones;
• report an unfamiliar login or profile change promptly.

The Jaya9 support page asks users to provide a username and a detailed description when reporting an account or platform issue. Passwords and verification codes should not be included.

User Privacy Rights

Depending on the circumstances and applicable requirements, a person may be able to request:

• access to personal information;
• correction of inaccurate data;
• deletion of certain information;
• restriction of particular processing;
• withdrawal of previously provided consent;
• cessation of optional marketing messages.

These rights may not apply in the same way to every record. For example, deletion may be limited where transaction or security information must still be retained.

Accessing, Correcting or Deleting Information

Some profile information may be available directly in account settings. When it cannot be edited, the user may submit a contact-form request and confirm ownership of the account.

A deletion request should clearly identify the information concerned. It may also be treated as an account-closure request when continued operation is impossible without that data.

Marketing Communications

A user may request that optional bonus, promotional or informational messages stop. Removing marketing consent does not automatically close the account or delete transaction records.

Minors and Account Eligibility

The service is intended only for users who satisfy the platform’s current adult-age requirement and applicable local rules.

If an account appears to belong to someone below the required age, access may be restricted while the situation is reviewed. No specific numerical age should be inserted unless it is clearly confirmed in the current platform terms.

Contact-Form Data

A privacy request may contain a name, registered contact, account identifier, request topic, explanation and supporting attachment. This information should be used to identify the account, review the issue and provide a response.

Do not submit through an ordinary text field:

• a full password;
• a one-time verification code;
• a CVV or complete card number;
• an email or mobile-wallet password;
• unrestricted payment-account access.

When documents are required, follow only the instructions provided through the protected verification interface.

Changes to This Privacy Policy

This policy may be updated when platform functions, data practices or applicable requirements change. A visible “Last Updated” date should appear at the beginning or end of the published document.

Users should periodically review the current version, particularly before providing new information or using a newly introduced payment, verification or mobile function.

How to Submit a Privacy Request

Use the contact form and include:

1. the privacy-related topic;
2. the registered contact information;
3. the username or account ID;
4. a clear request for access, correction, deletion or restriction;
5. relevant dates or transaction references;
6. a safe screenshot when necessary.

Before releasing or changing information, the platform may need to verify that the requester owns the account. This protects personal data from being disclosed to another person. A password or one-time code should never be requested through the general message field.