Rujukan Laman

Privacy Policy for Malaysia Accounts

On rizzy, this page explains what personal data we collect, why we need it, and how we use it to run your account, confirm requests, and answer messages.

MalaysiaData useCookiesAccess
rizzy Privacy Policy for Malaysia Accounts
CONTACT PATHS READY

Where to Reach Our Privacy Team

If you want to ask about your data, the fastest path is the inbox linked to your account.

Privacy mailbox Send policy questions or a record request through the privacy mailbox linked to your account. We use it for access, correction, and removal requests, and we keep a trace so you can follow the response.
In-account message Use the message panel when you need to identify a specific session, device, or payment record. That route helps us match your query with the right record without asking you to repeat details in another thread.
Request form If you want a copy of your data or a correction, submit the form with the exact field you want changed. We reply with the next step and any extra checks that local law requires.
RETENTION AND ACCESS

How We Protect Personal Data

We treat personal data as part of account operation, not as extra material. Cookies help remember session state and settings, while device and browser details help us spot access from a new…

Collection scope

We ask for the minimum details needed to open your account, confirm your request, and keep records accurate. If a field is optional, we mark it before you submit anything.

Cookies and sessions

Cookies help keep you signed in, remember language choices, and measure repeated visits to the page. You can clear browser cookies, but some settings may need to be entered again.

Device checks

We may log device type, browser version, IP address, and time stamps to spot unusual access and protect account access. Those records are used for security and incident handling.

Retention rules

We keep personal data only for as long as needed for service, dispute handling, audit needs, or legal duty. When the retention period ends, records are removed or made non-identifying where that is suitable.

Correction requests

If a record looks wrong, ask us to correct it and send the exact field that needs updating. We may ask for a check that links the request to your account before we change anything.

Who can see it

Access inside the company is limited to staff who need the record to answer you, process a request, or maintain the service. We do not open personal data to unrelated teams.

Common Questions About This Policy

These questions cover how we collect, use, keep, and correct personal data. They are written for Malaysia accounts, so the answer can change if local law, a request type, or a retention duty requires a different step. If you do not see your situation here, send the exact record details through the privacy mailbox and we will route it.

We collect the details needed to open and maintain your account, answer requests, and keep records accurate. That can include contact details, device data, cookies, and transaction records tied to the methods you use.

Cookies help remember your session, language, and page settings, and they help us understand whether the page loads correctly on your browser. You can clear them in your browser, though some settings may reset.

Yes. Records linked to Touch 'n Go, GrabPay, Boost, or FPX can be kept with your account file so we can confirm a request, trace an error, or answer a question about a transaction.

Use the privacy mailbox, the in-account message path, or the request form. Tell us which record you want to see, and we will return the next step after any checks required by local law.

Yes. Send the field that needs changing and the corrected version. If we need to match the request to your account, we may ask for a short verification before we update the record.

We keep data only as long as needed for account handling, dispute work, audit tasks, or legal duty. After that period, it is removed or stored in a way that no longer identifies you.

Contact the privacy mailbox first if your question is about access, correction, or retention. If your message is tied to a specific account event, the in-account route helps us find the right record faster.