Rujukan Laman

hokiraja Privacy Policy in Malaysia

hokiraja keeps your account, wallet, cookie, and support data rules in one Privacy Policy, so you can see how we collect, use, share, and retain data before you…

Malaysia account dataCookie choicesTouch 'n Go record careAccess request paths
hokiraja hokiraja Privacy Policy in Malaysia
CONTACT ROUTES

3 Ways To Reach Privacy Support

If you want to ask about your data, correct account details, or check how long a record is kept, contact us through the route that fits the matter. We may ask for account proof before we discuss private records, because privacy support must confirm that the request comes from you. Keep screenshots clear, remove unrelated details, and tell us which payment or session record you mean.

Team online

Live chat privacy queue

Use live chat for quick privacy questions about account access, cookie settings, or a recent payment reference. Our team may move the chat to email if identity checks or longer record searches are needed.

Email data request

Send email when you need a copy, correction, or deletion request considered under applicable law. Include your registered phone or email, the record type, and a short reason so we can route it properly.

Account security help

Contact account security if you notice a login you do not recognise, a changed wallet detail, or a device session that looks wrong. We can lock access while the privacy check is handled.

DATA HANDLING

6 Privacy Controls Around Your Account

We write this policy from the way our account, wallet, and support systems work day to day.

Account data collection

We collect account details such as name, contact route, login credentials, and verification status so your profile can be created, protected, and recovered. We avoid asking for unrelated personal data during normal account setup.

Cookie and device signals

Cookies and device signals help us keep your session active, remember language choice, detect repeated failed logins, and reduce account misuse. You can clear browser cookies, though some account functions may need them again.

Payment record handling

For Touch 'n Go, GrabPay, Boost dan FPX, we keep transaction references, status messages, and reconciliation records. These help us match deposits, check withdrawals, and answer payment disputes without storing full wallet passwords.

Access controls

Private records are limited to team roles that need them for support, wallet checks, security work, or compliance tasks. We use login controls and internal activity records to reduce unnecessary viewing.

Retention periods

Some records are kept while your account is active; others stay longer where law, disputes, fraud checks, or accounting duties require it. When retention ends, we delete, anonymise, or archive the data.

Change requests

You can ask us to correct details, consider deletion, or explain a processing purpose. We may refuse or limit a request where identity cannot be confirmed or a legal duty requires retention.

Privacy Policy Questions Before Joining

These answers focus only on how this Privacy Policy works for your account and data. They explain what we collect, why payment records are kept, how cookies support access, and how you can reach us about privacy choices. If your request involves local law, we will assess it based on the rules that apply to your account and region.

We collect the details needed to create, protect, and recover your account, such as name, contact route, login data, and verification status. We may also keep device and session records for security checks.

Payment records help us match deposits, check withdrawals, and respond to disputes involving Touch 'n Go, GrabPay, Boost dan FPX. We keep references and status data, not full wallet passwords.

Yes. You can contact privacy support and ask for access to data linked to your account. We may need to confirm your identity before sharing private records or explaining any limits.

You can ask us to correct inaccurate profile details. We may request proof where the change affects withdrawals, account recovery, or identity checks, because those records protect your account and wallet activity.

Cookies help keep your session active, remember basic preferences, and detect unusual login behaviour. You can clear them in your browser, but some account functions may ask you to log in again.

Access is limited to team roles that need the records for support, wallet checks, security work, or required administration. We aim to keep viewing narrow and tied to a clear work reason.

Retention depends on the record type, account status, legal duties, disputes, fraud checks, and accounting needs. When a valid reason ends, we delete, anonymise, or archive the relevant data.