JAYAKING88 Privacy Policy: Personal Data and Information Practices

1. Scope of this policy

1.1 What it covers

This draft concerns the JAYAKING88 website at jayaking88.com, account features, the site’s live chat and access through the JAYAKING88 Android app. JAYAKING is the short brand name. Payment gateways, banks, telcos, Telegram and the external app download host are separate service interfaces; their data handling and any sharing with JAYAKING88 are not fully documented here. See sections 5 and 9.

1.2 Who is responsible

JAYAKING88 is the brand under which the platform operates. The current evidence does not establish which legal entity acts as the personal-data controller. This draft therefore does not name one. Use the official support route in section 8 to ask about your information; the controller identity and privacy contact arrangements require operator approval before this becomes an effective notice.

1.3 How this policy is written

The registration and account examples below are drawn from the reviewed interfaces; the uses described follow their visible functions. Screens alone cannot establish all backend collection, storage or sharing. Retention, security, other recipients and cookies or analytics are therefore left for the operator to confirm rather than presented as facts.

2. Information collected when you register

The registration screen reviewed for this draft displayed these fields:

The reviewed registration screen did not display date-of-birth, address, nationality, identity-document, email or occupation fields. This does not establish whether the platform requests additional information elsewhere. The stated site audience is 21+; age-verification procedures have not been confirmed.

3. Account and transaction information

3.1 Profile and bank details

The reviewed account panel displayed the username, registered bank name and account number, and the balance (Baki). The brand identifies the registered bank account as the confirmed withdrawal destination, with the registered name matching the bank account name. How long these details are retained has not been established.

3.2 Transaction records

The Rekod area provides account transaction records, including deposit and withdrawal activity. The reviewed cashier screens show the selected payment channel, amount and, for applicable routes, a transfer time or gateway reference. The Online QR/ATM form also presents a bank-in-slip upload field. The exact set of fields retained in Rekod, and whether uploaded receipts remain stored, require verification.

3.3 Promotion, points and ranking records

Promotion cards, active balance targets, VIP progress, mission and mini-game points, and ranking positions appear in the site’s account and rewards interfaces. The observed deposit and withdrawal rankings operate over dated cycles. Which underlying activity records are stored and for how long remains unverified.

3.4 Referral records

The registration form includes an optional referral-code field, and the site displays referral links and a Downline feature. These interfaces connect referral activity with rewards. The exact identifying data shown to referrers, referral recipients and other users has not been verified.

3.5 Support conversations

The site provides live chat for account questions. Information you type into a chat request may be handled through that service; its provider, access controls and retention are not documented here. Do not provide your password or SMS verification codes in a support conversation.

4. What the information is used for

The observed interfaces show how the information relates to these user-facing functions; they do not establish every background processing purpose:

• Opening and operating the account — your name, phone number and password identify the account and secure the login; the SMS code verifies the phone number at registration.
• Paying withdrawals — the registered bank account, in the registered name, is the only payout destination; the name match is checked against it.
• Applying promotion conditions — claim records, balance targets, turnover and caps are applied to the account so that the Baki panel can show the active Withdraw Minimum and Withdraw Maksimal.
• Running rewards and rankings — VIP tiers, missions, mini games, redemption and the leaderboard use your deposit, points and ranking records.
• Referral rewards — the referral link ties downline accounts to the referrer for the weekly commission card.
• Answering support requests — the details you send to live chat are used to find and resolve the request.

The reviewed materials do not establish whether account data are used for advertising, profiling, marketing messages or integration with Telegram. Those processing purposes and any related choices must be confirmed by the operator before they can be described as settled practices.

5. Payment gateways and other services involved in your use

Deposits, banking, downloads and messaging may involve third-party or embedded interfaces. The screen where a field appears does not prove which organisations receive, store or process the data:

The supplied materials do not establish vendor contracts, processor/controller roles, exact data recipients, cross-border transfers or retention for these services. These matters require an operator data-flow inventory before the final privacy notice is adopted.

6. Cookies, sessions and tracking

Account login and navigation are available, but the reviewed materials do not identify which session technologies the site uses. A login interface alone cannot establish whether browser cookies, local storage, server-side sessions or third-party scripts are involved. Analytics, advertising tags, app SDKs, consent choices and tracking practices have not been audited. The operator must supply a current CMS/browser script and cookie inventory before this section can state the actual technologies, purposes and user controls.

7. Display, sharing and storage

7.1 What other members can see

• Leaderboard — the reviewed ranking view showed an identifier such as AA****78 alongside the ranked amount. This example does not establish a consistent masking policy for all rankings or users.
• Transaction feed — a homepage component displays identifiers and amounts. The reviewed example does not establish whether entries come from real member transactions, how identifiers are selected, or whether a production masking rule applies.
• Referral — the Downline interface displays linked referral activity. The full set of fields visible to each participant, including any information about the referrer, has not been confirmed.

7.2 Sharing with other companies

JAYAKING88 is associated with the confirmed sister-brand network. The supplied records do not establish whether personal data are shared across that network, with payment providers, or with other recipients. This draft does not assert that sharing takes place or that it never takes place; the operator must verify actual data flows and disclosures.

7.3 Storage and security

The current source set does not establish storage locations, retention or deletion periods, access controls, encryption, backup practices or handling after account inactivity. These details require operational confirmation. The reviewed site interface alone cannot establish whether an account-closure process exists.

8. Your choices and requests

8.1 Seeing and updating your information

The account panel displays your username, registered bank details and balance, and Rekod provides transaction information. The login screen has a Reset PW entry, but its completed recovery workflow has not been tested. For questions or a request concerning registered name or bank details, contact live chat; whether a change can be made and what verification is needed must be confirmed in that session.

8.2 Asking about your information

Use the live chat or the routes on Contact Us to ask what information the platform has about your account or to request a correction. You may also ask whether an account pause or closure is available; this draft does not promise either facility. Describe your request using your registered name, but never include your password or SMS codes. Identity checks, request-handling steps, available choices and response times still require operator confirmation.

8.3 Promotional messages

The Promotion page and the confirmed Telegram channel display promotion information. Telegram subscriptions are managed through Telegram. Whether JAYAKING88 uses registration phone numbers or other account data for direct marketing, and what messaging choices are provided, has not been established; ask official live chat about a message or privacy concern.

9. External links and the app

• App download page — the official download link opens a page at xj72.startuppage.xyz, outside jayaking88.com. The external download host and installed Android app may present their own information requests or permissions. Their actual data collection, SDKs and any sharing with JAYAKING88 have not been reviewed. See the App page for the official access route.
• Payment gateways and banks — some deposit steps open payment-service or banking interfaces. Follow the verified payment flow, and do not submit bank passwords or one-time codes to live chat. Which information is shared between providers and JAYAKING88 requires confirmation.
• Telegram — the official channel at t.me/JAYAKING88 runs on Telegram.
• Partner and sister-brand sites — links to partner brands lead to their own websites and policies.

10. Age and privacy

JAYAKING88 is for people aged 21 and above in Malaysia. The registration screen reviewed did not display a date-of-birth or identity-document field. This does not establish what other age checks may occur or what happens to age-related information elsewhere. The 21+ audience rule should not be mistaken for proof that age was verified. Do not register on behalf of, or share an account with, anyone under 21. See Responsible Gambling for protecting younger people in your household.

11. Policy version and updates

11.1 Version

This is version R1.1 (Controller-reviewed draft), based on the observed registration, account, cashier, records and support interfaces. It was revised on 23 October 2026 and remains an English-language draft. An approved effective privacy notice, including any applicable Bahasa Malaysia language requirement, remains subject to operator and legal review.

11.2 Effective date

No operator-approved effective date has been provided. This draft summarises selected first-party interfaces and unresolved data practices; it must not be presented as the effective privacy notice until the responsible entity and actual processing terms have been confirmed.

11.3 Changes

After operator approval, the notice should be maintained when relevant data practices change. Each published update must use its real review and effective dates; this editorial draft version is not the operator's policy adoption record.