Rujukan Laman

Privacy Policy for your gj99 account

Your account data, cookie choices and payment references are handled under this Privacy Policy before you open an account with gj99.

Account data useCookie choicesTouch 'n Go recordsPrivacy requests
gj99 Privacy Policy for your gj99 account
CONTACT ROUTES

Three ways to reach privacy support

Privacy questions should reach the team that can act on account records, not a general inbox with no context. Use the contact path that matches your issue, and include your account name, masked phone number, and the data request you want us to check. For safety, we may ask you to confirm account access before we discuss private records.

Team online

Privacy mailbox

Email us through the privacy contact shown inside your account centre. Use this route for data export, correction, deletion, cookie concerns, or questions about how payment references are linked to your wallet.

Live chat request

Start chat from your logged-in account when you need quick routing. The team can record your privacy request, confirm which department owns it, and tell you what identity check may be needed next.

Account security help

Use the security contact path if you see an unknown login, changed phone number, or wallet action you did not make. We prioritise access control first, then handle the privacy record after verification.

DATA CONTROLS

Six controls behind your account data

We handle privacy as an operating duty, not a footer link. Account fields, cookie records, wallet references and contact transcripts are separated by purpose so staff see only what they need.

Collection by purpose

We collect account details, device signals, wallet references and contact messages for defined reasons: account creation, access checks, payment matching, support handling, risk screening and legal record keeping where required.

Cookie choices

Cookies help keep your session active, remember language settings and measure whether pages load correctly. You can adjust browser settings, but some account actions may not work if essential cookies are blocked.

Security checks

Login attempts, password changes and wallet edits may trigger extra checks. These records help us detect account takeover attempts and protect your profile before private data or payment records are exposed.

Payment privacy

For Touch 'n Go, GrabPay, Boost dan FPX, we store references needed to match wallet actions and resolve disputes. We do not store full banking credentials inside your account profile.

Retention periods

Different records are kept for different lengths of time. Contact messages may be shorter-lived, while transaction and access records may need longer retention for dispute handling, fraud checks and legal duties.

Change requests

You can ask to correct inaccurate details, receive a copy of stored account data, or request deletion. We explain any record we cannot remove because of safety, transaction, or legal requirements.

Privacy questions before opening your account

These answers explain the Privacy Policy in plain terms before you share account details. They focus on what we collect, how we use it, who may receive it, and how you can contact us about your rights. If your question involves a live account, use the privacy contact path after logging in.

We collect account details such as name, phone number, login records, device signals, wallet references and support messages. We use them to create access, protect your account, match payments and respond to your privacy requests.

Payment references let us match Touch 'n Go, GrabPay, Boost dan FPX actions to your wallet. They help resolve missing credits, duplicated attempts, withdrawal checks and disputes without exposing full banking credentials.

We share limited data with service providers only when needed for hosting, payment processing, fraud screening, messaging, account security or legal requests. Each provider receives only the data needed for the task assigned.

Send a request through the privacy mailbox inside your account centre. We may verify your identity first, then prepare the account data we can release without exposing security controls or another person’s records.

Yes, you can ask us to correct inaccurate profile details. Some fields may need verification, especially phone numbers and wallet-linked data, because changes can affect account access and payment matching.

Retention depends on the record type. We may keep transaction logs, access records and security events longer than chat messages because they support dispute checks, account protection and legal duties that may apply.

If access or eligibility is affected by local law, we handle the account according to where local law permits. Privacy requests still receive attention, but some account actions may be restricted by legal requirements.