Rujukan Laman

Privacy policy for your account

This page explains how we collect, use, store, and protect your account details at mkt4d.

Account dataCookiesLocal lawRetention

What this policy covers

mkt4d Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

Our policy covers the details you give when you open an account, the device signals that help us secure logins, and the records created when you send a support message or move money through Touch 'n Go, GrabPay, Boost, or FPX. We use that data to

1
confirm your identity, process requests, detect unusual activity, and keep a trace of actions linked to your account. Some records stay for a set period so we can meet audit, tax, dispute, and security needs; others are removed or archived once the purpose ends. Cookie settings
2
sit with your browser, so you can change them on your device at any time, although some page functions may change. If you want access, correction, or deletion of a record, send the request through support and we will act where local law permits.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

REQUEST CHANNELS

Where to send privacy requests

If you want a copy of your data, need a correction, or think a record was used in the wrong way, start with support.

Email request Send your privacy request from the email tied to your account. Include the detail you want to access, correct, or remove, and we will reply with the next step after we verify it.

Account message Use the message form for questions about cookies, retention, or transaction records. We keep the thread attached to your case so the reply stays aligned with the record you asked about.

Identity check If a change affects contact details or security settings, we may ask for a fresh check before acting. That protects the account from unwanted edits and keeps the request trace clear.

DATA CARE

How we protect your records

We keep the policy focused on what we actually handle: account records, login signals, payment references, support threads, and browser cookies.

Data minimisation

We ask for the fields needed to open, secure, and service your account, plus the records needed for payment reconciliation and dispute handling. Extra fields are not collected without a clear reason.

Cookie control

Browser cookies keep you signed in and remember basic settings. You can block or clear them in your browser, and some pages may ask you to log in again after that.

Security review

Unusual login attempts, device changes, and request patterns may trigger an extra check before we act. That helps reduce misuse and keeps account changes tied to the right person.

Retention rules

Some records must stay longer for tax, audit, fraud, or dispute purposes. After the purpose ends, we remove or archive them according to the rule that applies to that record.

Change requests

If your phone number, email address, or mailing address changes, send the new details through support. We will update the profile after verifying the request and note the change for audit.

Access and correction

You can ask what we hold, ask for a correction, or ask us to pause using a record when local law allows it. We will explain the result in plain English.

Privacy policy questions and answers

These questions cover the records we keep, the reasons we keep them, and the choices you can make about your account data. If you need a copy, correction, or change, start with support and give the detail that helps us find the record. We keep the process simple, but we still check the request against the policy and the law that applies.

We may collect your name, contact details, login credentials, device signals, and the records needed to verify the account. If you send us a support message or transaction reference, we keep that too so we can answer it properly.

Yes. Cookies help us keep you signed in, remember basic settings, and recognise repeat visits on the same browser. You can control them through your browser settings, although some functions may change if you block them.

We keep payment references, timestamps, and related entries so we can reconcile account activity, answer disputes, and meet audit or tax duties. For supported Malaysia rails, the record stays only as long as that purpose needs it.

Only staff and systems that need it for account service, security, or legal duties can see it. We do not open records for unrelated use, and we restrict access by role so the right team sees only what they need.

We keep data for the period needed for the reason it was collected, then remove or archive it when that reason ends. Some records stay longer if a rule on audit, tax, dispute handling, or fraud checks applies.

Yes. Send the request through support with enough detail to find the record, and we will check it against the account and the law that applies. Where local law permits, we will carry out the change.

Use the support channel with the account email, the record you want checked, and a short note on the problem. We will check it, reply with the next step, and keep the case tied to your request.

Privacy policy for your account

Where to send privacy requests

How we protect your records

Data minimisation

Cookie control

Security review

Retention rules

Change requests

Access and correction

Privacy policy questions and answers

01 What details do you collect when I open an account?

02 Do you use cookies on my device?

03 Why do you keep transaction records?

04 Who can see my account data?

05 How long do you keep my data?

06 Can I ask for a copy or correction?

07 How do I raise a privacy concern?

Related Pages