Rujukan Laman

bmw2u Privacy Policy for Malaysia

We keep your account data, device signals and payment references under one privacy framework, so you can see exactly how bmw2u handles each record.

Account DataCookie UsePayment RecordsLocal Law
bmw2u bmw2u Privacy Policy for Malaysia
REQUEST ROUTES

Where to Send Privacy Requests

If you want to ask about access, correction, deletion or a copy of the records we hold, start from the channel linked to your account so we can confirm it is really you. We answer privacy requests in English for Malaysian customers and may ask for a matching payment reference if your request touches a Touch 'n Go, GrabPay, Boost or FPX entry. That keeps the wrong person out of your records.

Team online

Account message

Send the request from your logged-in account dashboard so we can confirm ownership before we act. Use it for access, correction or deletion, and include any deadline you need us to meet.

Email channel

If email suits you better, write from the address tied to the account and say exactly what you want changed. We may ask one follow-up question to keep the record safe.

Payment trace

For Touch 'n Go, GrabPay, Boost or FPX records, share the date, amount and reference code. Those details help us find the right entry without exposing other account data.

DATA CONTROLS

Cookies, Security and Record Handling

We treat privacy requests as part of account care, not a side form. The same controls that guard logins also help us check who can see, change or remove stored records.

Data handling

We collect only what is needed to open and service your account: contact details, login activity, device signals and payment references. Any extra use must fit the purpose we tell you here or the law that applies.

Cookie choices

Cookies remember your session, language and screen state, and some also help us flag unusual access. You can clear them in your browser, though that may make you sign in again on the next visit.

Login security

Access logs, password resets and failed sign-in attempts help us spot unauthorised use. If a device looks unfamiliar, we may ask for extra checks before we let you change sensitive account settings.

Record retention

We keep records for support, tax, dispute handling and legal duties, then delete or anonymise them when that period ends. If a record must stay longer, local law or a live dispute is usually the reason.

Change requests

You can ask to correct details, limit certain uses or request deletion where local law allows. We will confirm identity first, then tell you what can be changed and what must remain on file.

Contact path

Use the account email or inbox tied to your profile so we can match the request to the right record. If a payment trace is involved, add the date, amount and reference for faster handling.

Common Privacy Questions From You

These questions cover the records we keep, why we keep them and how you can ask us to change them. The answers apply to your account, device and payment records, and any request depends on local law and is available where local law permits. If your request touches a Touch 'n Go, GrabPay, Boost or FPX entry, a matching reference helps us find it faster.

It covers account setup details, login logs, device signals, cookies, support messages and payment references. We use those records to run the account, protect access and answer requests that come through the correct channel.

We keep records for verification, security, disputes, tax and legal duties. Some details stay only for a short period, while others must remain longer if a payment trace or account case is still open.

Yes. Send a request from the account tied to the record, then tell us what should change. We will check ownership first, make the update where local law allows, and confirm what we changed.

Cookies help hold your login, remember language choices and keep security checks in place. If you clear them, the session may end and some settings can disappear until you sign in again.

Only when needed for payment processing, hosting, security or messaging, and only under instructions we set. Those parties should handle the data for that task alone and should not use it for anything else.

Include the date, amount, reference code and the payment route you used, such as Touch 'n Go, GrabPay, Boost or FPX. That helps us find the exact entry without exposing other records.

Use the in-account channel or email tied to your profile and say whether you want access, correction, deletion or a copy of a record. We may ask for a short check before acting.