Rujukan Laman

Privacy Policy for Your j2j3 Account

j2j3 links your account details, game session data, cookie choices and payment records to one privacy policy, so you can see what we collect before you open an…

Malaysia account dataCookie choicesTouch 'n Go contextGrabPay records
j2j3 Privacy Policy for Your j2j3 Account
CONTACT ROUTES

Reach Us About Privacy Requests

Privacy requests need a clear path, especially when they involve account access, payment receipts or identity checks. Use the contact route that matches your concern and include enough detail for us to locate your account without asking you to repeat the same point. We may need to confirm that the request comes from you before changing, exporting or restricting account data.

Team online

Account inbox

Use the message area inside your account for privacy questions tied to wallet history, login changes or payment receipts. This route lets us match the request to your profile with less back-and-forth.

Live chat handoff

If your privacy concern starts in chat, ask the agent to mark it as a data request. We then move the matter to the privacy queue so the reply stays accurate and traceable.

Email form

For longer requests, send the form with your account name, contact email and the data topic involved. Do not attach full payment screenshots unless we ask for a specific reference.

POLICY PRACTICE

Six Ways We Handle Your Data

Our privacy work follows the account journey: sign-in, lobby access, payment checks, support contact and data retention.

Account data

We collect details you submit during account creation and profile updates, such as contact fields, login identifiers and security prompts. The policy explains why each category is used and how it supports account access.

Payment references

Touch 'n Go, GrabPay, Boost dan FPX transactions create status messages, receipt numbers and wallet references. We use these records to match requests, trace failed payments and answer privacy questions about payment history.

Cookie choices

Cookies help keep your session open, remember language settings and measure page performance. You can change browser settings, though blocking some cookies may affect sign-in, wallet display or support chat behaviour.

Security checks

Login alerts, device signals and repeated access attempts may be logged to protect your account. These checks help us spot unusual activity before payment records or profile details are changed.

Retention periods

Some records are kept only while your account stays active, while payment and dispute records may stay longer due to legal or operational needs. We explain the reason when a privacy request is limited.

Change requests

You can ask us to correct contact details, update consent choices, export account data or delete eligible records. We verify ownership first so another person cannot change your privacy settings.

Privacy Questions Before You Join

These answers explain how the Privacy Policy applies when you open an account, use Malaysia payment methods, enter the lobby or speak with support. They are written for account decisions, not for legal jargon. If your request needs action on a live account, contact us through the account inbox or privacy form.

We collect the details needed to create and protect your account, such as contact fields, login identifiers, device signals and consent choices. Extra checks may apply when payment activity or account access needs verification.

Those Malaysia payment options can create receipt numbers, bank status messages and wallet references. We use that data to match payments, respond to account questions and keep records required for service operation.

Yes. Send a privacy request through the account inbox or email form and state the data range you need. We verify ownership before sharing any file or account history extract.

Cookies support sign-in, session memory, language settings and page measurement. You can adjust browser settings, but some account functions may not load correctly if essential session cookies are blocked.

You can request correction of eligible account details, including contact fields that are no longer accurate. We may ask for verification before making the change, especially where payment records are connected.

Deletion depends on the record type and any legal or operational reason to keep it. If a record must remain for a set period, we will explain why and limit use where possible.

Only teams assigned to support, account checks, payment tracing or privacy handling can view the request. Access is limited by role, and sensitive attachments should be sent only when we ask for them.