Rujukan Laman

jinjinjin Privacy Policy for Your Account

At jinjinjin, this page explains how we collect, use, store, and share account data when you open an account, send support messages, or move funds through Touch 'n…

Account DataCookiesSupport RecordsLocal Law
jinjinjin jinjinjin Privacy Policy for Your Account
CONTACT PATHS

Where to Send Privacy Requests

If you want a copy of the data we hold, want to correct a detail, or have a question about how this policy works, send it…

Email us Send requests for data access, correction, or deletion steps to our privacy mailbox.
In-account chat Use the message box after login if you want a faster check on account…
Contact form If you cannot reach the account team, submit the form with your details and…
DATA CARE

How We Handle Your Data

We keep this policy area tight: only the data needed for registration, wallet movement, device checks, support follow-up, and legal retention. Cookies help remember your session and spot unusual access.

Data handling

We collect only the details needed to open and keep your account: name, contact details, device signals, and payment references for Touch 'n Go, GrabPay, Boost dan FPX. We keep the purpose narrow and limit access to staff who need it.

Cookies

Cookies help us remember your session, keep the page stable, and spot sign-in patterns that do not fit your usual device use. You can clear them in your browser, but some settings may need to be set again after that.

Account security

We log sign-ins, password changes, and wallet edits so we can spot unauthorised use fast. If you suspect a problem, change your password, contact support, and we will check the record before any further changes are made.

Retention

We keep records for as long as needed for support, reconciliation, dispute handling, and legal duties. When the retention period ends, we remove or mask the details that are no longer needed for the stated purpose.

Change requests

If you want a copy, correction, or removal of data where local law allows it, send the request from the account email and include enough detail for us to find the record and verify the request.

Contact route

Use the contact form, email, or in-account chat for privacy requests. We route the message to the right team, track the case, and reply with the next step instead of sending you between teams.

Privacy Questions You May Ask

These are the common questions we hear when you want to know what sits in your file, who can see it, and how to change it. We keep the answers practical: what we collect, how long we keep it, and which channel to use when you need a copy or correction. When access depends on local law, we say so plainly.

We keep the details you submit for registration, login, support, and account checks, plus device and session records that help us keep the record accurate. If you move funds, we also retain the references needed to match the entry.

Cookies remember your session, save page settings, and help us notice sign-in patterns that do not fit your usual device. They also reduce repeat prompts, so the page keeps the same state while you move around.

Yes. Send the request through support from the email linked to your account, and include enough detail for us to find the record. We will reply after checking the request under local law and our internal process.

Yes. If your name, contact detail, or account record needs a fix, contact us with the updated detail and any proof we need to match the file. We will change what we can after verification.

We keep records only for the period needed to run the account, settle entries, answer support cases, and meet legal duties. After that, we remove or mask details that are no longer needed.

Only staff who need the record for support, verification, or legal handling can access it. We do not share a request outside that path unless the law requires it or you ask us to.

Use the contact form, in-account chat, or email, and tell us what you want changed. We will direct the message to the right team and keep the response linked to your case.