| Privacy Area | Information That May Be Involved |
| Registration data | Username, phone number, email, currency and other profile details |
| Verification | Identity documents or other supporting information where requested |
| Payments | Transaction amount, date, currency, method and status |
| Account activity | Logins, games, bets, bonuses and account changes |
| Technical data | IP address, browser, device and usage information |
| Cookies | Session, preference and possible performance identifiers |
| Data recipients | Payment, hosting, verification, security or support providers where required |
| Retention | Depends on the type of information and operational requirements |
| User rights | Access, correction, deletion or restriction where applicable |
| Requests | Submitted through the available contact or support route |
Information Covered by This Privacy Policy
Personal information may be involved when a user:
- visits Jaya9-related pages;
- registers or signs in to an account;
- uses casino or sports betting sections;
- makes a deposit or withdrawal;
- completes identity verification;
- changes account information;
- sends a support or privacy-related request.
The current Jaya9 registration page identifies username, password, currency, phone number and email as account information used during sign-up. Jaya9 also describes a verification section where scanned documents can be submitted.
External payment providers, linked websites or embedded services may apply their own privacy rules.
Personal Information That May Be Collected
The information involved depends on how a person uses the platform. Not every category necessarily applies to every visitor or account.
Registration and Account Details
Current Jaya9 registration information includes:
- username;
- password;
- account currency;
- phone number;
- email address.
Additional profile information may be requested when necessary for account management, verification or another platform function. Information that is not explicitly shown as mandatory should not automatically be described as a required registration field.
Identity Verification Information
Jaya9 currently describes a verification process through the account Profile area where users may be asked to upload scanned documents.
Verification materials may include identity, age, address or payment-ownership information where relevant. Sensitive documents should be submitted only through the designated verification interface or another clearly identified secure process.
Payment and Transaction Data
Deposits and withdrawals can generate information such as:
- transaction amount;
- BDT or another applicable currency record;
- date and time;
- payment method;
- transaction status;
- reference or transaction identifier.
This does not mean that Jaya9 necessarily stores complete card numbers, CVV codes or login credentials belonging to an external payment service.
Gambling and Account Activity
Account activity may create records of games, sports bets, bonus use, account logins, settings changes and disputed transactions.
Such information may be relevant to account operation, reviewing transactions, enforcing applicable platform rules or investigating suspicious activity.
Information Collected Automatically
Technical information can be transmitted when a website or mobile service is used.
This may include IP address, device type, browser, operating system, interface language, approximate location, visited pages, visit time and referral source.
Technical location information should not automatically be treated as a precise record of a user’s physical position.
Device and Log Data
Technical logs may help with:
- diagnosing page or application errors;
- protecting accounts against suspicious access;
- reviewing unusual technical activity;
- maintaining service stability;
- understanding how pages perform.
A detailed public list of every log field used by Jaya9 is not currently available, so specific tracking data should not be assumed.
How Personal Data May Be Used
Personal information may support several account and operational functions.
| Purpose | Why Data May Be Needed |
| Account services | Registration, login and profile operation |
| Payments | Reviewing deposits and withdrawals |
| Verification | Confirming identity or account ownership |
| Support | Investigating questions or account problems |
| Security | Detecting suspicious access or possible fraud |
| Rules enforcement | Reviewing possible abuse or multiple accounts |
| Technical operation | Identifying errors and improving service stability |
Providing Account Services
Data may be used to register an account, authenticate login attempts, retain available profile settings and provide access to account functions.
Jaya9’s current login information states that account access uses a username and password.
Processing Deposits and Withdrawals
Transaction data may be required to associate a payment with the correct account, confirm its status and review possible unauthorised activity.
A payment provider may independently process some information according to its own privacy terms.
Preventing Fraud and Account Abuse
Jaya9 states that it permits one account per player and conducts security checks.
Account and technical information may therefore be reviewed where there are concerns about duplicate accounts, suspicious login activity, payment abuse or possible rule violations. This should not be interpreted as a claim that automated or manual checks detect every problem accurately.
Cookies and Similar Technologies
Cookies are small files or identifiers that websites can use to maintain sessions, remember preferences and support page functionality.
Depending on the current implementation, cookies may include:
- essential session cookies;
- functional or preference cookies;
- analytics or performance cookies.
The currently reviewed public Jaya9 pages do not provide enough detail to name a specific analytics provider or confirm every cookie category in use.
Essential Cookies
Essential cookies may support login sessions, account security and basic website operation.
Blocking them can cause a user to be signed out or prevent some account functions from loading properly.
Analytics and Performance Cookies
Analytics technologies may be used to measure page activity or technical performance where implemented.
No particular analytics service should be attributed to Jaya9 without current confirmation.
Managing Cookie Preferences
Users can normally manage cookies through browser settings.
Blocking or deleting cookies may result in:
- being logged out;
- losing saved preferences;
- needing to repeat certain settings;
- some pages functioning differently.
A separate Jaya9 cookie-management centre should not be assumed unless one is available in the current interface.
Legal and Operational Reasons for Data Processing
Information may be processed where it is necessary to provide requested account functions, perform transactions, apply platform rules, protect security or comply with applicable obligations.
Consent may also be relevant to optional activities such as certain communications.
The exact legal basis depends on the activity and applicable requirements, so this overview does not assign a specific statutory basis to every type of processing.
Sharing Information With Service Providers
Some data may need to be processed by external providers supporting services such as:
- payments;
- hosting and infrastructure;
- identity verification;
- technical support;
- security;
- analytics where used.
Only information necessary for the relevant task should be involved where appropriate. No specific partner should be named unless its role is confirmed.
Payment Providers
When a user selects a payment service, transaction-related information may also be handled by that provider under its own privacy policy.
Users should review the current provider terms before submitting payment information.
Identity and Security Services
External services may potentially assist with document, age, identity or security checks.
This does not mean a particular provider is used for every account or every verification.
Disclosure Required by Law or Security Needs
Information may need to be disclosed where a valid legal request applies or where disclosure is reasonably necessary to investigate fraud, protect users, address a security incident or defend legal rights.
A privacy notice should therefore not promise that personal information can never be disclosed to an authorised public body.
International Data Processing
Technical, payment or security providers can operate across different countries.
As a result, information may potentially be processed outside Bangladesh. Where international processing occurs, appropriate safeguards should apply according to the relevant circumstances and legal requirements.
Specific destination countries or transfer mechanisms should not be stated without confirmation.
How Long Personal Data May Be Stored
A single retention period should not be assumed for every type of information.
Retention may depend on:
- account status;
- transaction records;
- security needs;
- disputes;
- fraud prevention;
- applicable obligations.
Some information may need to remain after an account is closed where it is required to investigate a dispute, preserve transaction records or address security concerns.
No fixed number of years is publicly confirmed in the reviewed Jaya9 material.
How User Information Is Protected
Security measures may include restricted access, account verification, session controls and technical monitoring.
Jaya9 publicly states that it performs security checks and provides account verification procedures.
No online service should be described as providing absolute or 100% protection against every possible security incident.
User Responsibilities for Data Security
Users should:
- keep their password private;
- never send one-time codes to another person;
- use a protected personal device where possible;
- log out after using a shared computer;
- report unexpected account changes or suspicious access promptly.
User Privacy Rights
Depending on applicable requirements and individual circumstances, a user may be able to request access to personal information, correction of inaccurate data, deletion, restriction of processing or withdrawal of consent.
The availability of each right can depend on the type of information and why it is being retained.
Accessing or Correcting Personal Data
Some information may be available through account settings.
If a detail cannot be changed directly, the user can submit a request through the current support or contact channel and may need to confirm ownership of the account.
Requesting Data Deletion
A user may request deletion of certain information or account closure where available.
Some records may still need to be retained for security, fraud prevention, transaction disputes or other applicable requirements.
Withdrawing Consent
Where processing depends on optional consent, that consent may generally be withdrawn for future activity.
Withdrawal does not automatically undo processing that was already completed on a valid basis.
Marketing and Promotional Communications
Users may receive promotional or informational communications where they have agreed to them or enabled the relevant notification option.
Where an opt-out mechanism is provided, users can use it to stop optional promotional messages. Stopping marketing messages does not automatically close or delete an account.
Privacy of Minors
The platform is not intended for people who do not meet the applicable minimum age requirement.
Where an underage account is identified, access may be restricted and related information handled according to current platform rules and applicable requirements.
A specific age should not be stated unless confirmed in the current terms.
Third-Party Websites and Embedded Services
Jaya9-related pages may contain external links or services.
After moving to an external website, that provider’s privacy policy can govern the information submitted there. Jaya9 should not be presented as controlling the independent privacy practices of every external provider.
Data Related to Contact and Support Requests
Jaya9’s current support page asks users to provide their username and a detailed description of the problem when contacting support.
A support or privacy request may therefore contain contact information, account identifiers, the subject of the enquiry, message text and supporting attachments where appropriate.
Sensitive Information That Should Not Be Submitted
Do not place the following information in an ordinary message:
- account passwords;
- one-time authentication codes;
- card CVV codes;
- full payment-card details;
- payment-service login credentials.
If identity documents are required, follow the instructions provided through the appropriate verification process.
Automated Checks and Account Decisions
Technical systems may identify unusual logins, suspicious transactions or potential breaches of platform rules.
Such a signal can result in additional verification or a temporary restriction while the matter is reviewed. It should not be assumed that every final decision is made entirely automatically.
Changes to This Privacy Policy
Privacy information can change as account features, technical systems or applicable requirements develop.
Users should periodically check the latest version. A privacy page should clearly display a review or update date so readers can determine how current the information is.
How to Submit a Privacy Request
A privacy-related request can be submitted through the current contact or support route available on the website.
A useful request should include:
- a clear privacy-related subject;
- the registered contact detail;
- the relevant username or account identifier;
- a precise description of the information or action requested.
Do not include a password or authentication code.
Verifying the Account Owner
Before releasing, changing or deleting personal data, verification of account ownership may be required.
This protects information from being disclosed or changed at the request of an unrelated person. Verification should use an appropriate account or security procedure rather than requiring the user to place a password or one-time security code in an ordinary text message.