Rujukan Laman

Privacy Policy for your megahh5 account

Your account data, wallet records and cookie choices stay mapped to clear purposes in this Privacy Policy.

Account data useCookie choicesPayment record handlingPrivacy request channels
megahh5 Privacy Policy for your megahh5 account
CONTACT ROUTES

Three ways to reach our privacy team

Privacy questions should reach the people who can check account records, wallet entries, cookie settings, and support transcripts without moving your data through unnecessary channels.

Live chat privacy queue Use live chat when you need a quick privacy check while logged in. We may ask for account identifiers, recent login time, or wallet activity to confirm that the request belongs to you.
Email privacy desk Email works better for access, correction, deletion, or retention questions that need written context. Include your account name and the data category involved, but avoid sending passwords or full banking details.
Account request form For structured requests, the account form helps us capture the right fields in one pass. We use it to route privacy matters to staff who can check records and reply with clear next steps.
ACCOUNT CARE

Six privacy controls inside your account

We treat this policy as a working account document, not a static legal page. The controls below explain how data is collected, used, limited, and changed when you move through login, game…

Account data collected

We collect details you give us during account setup, login, wallet checks, and support contact. This can include identifiers, contact data, device signals, session records, and messages needed to operate your account safely.

Payment record handling

Wallet activity through Touch 'n Go, GrabPay, Boost dan FPX creates transaction records tied to your account. We use them for payment matching, withdrawal checks, fraud prevention, and support replies about disputed entries.

Cookie and device choices

Cookies help keep your session active, remember language settings, measure page errors, and protect login attempts. You can adjust browser settings, though some account or wallet features may not work as intended without them.

Access and login safeguards

We monitor login patterns, device changes, and repeated failed attempts to protect your account data. When a risk signal appears, we may request verification before showing wallet records or changing personal details.

Retention and deletion

We keep personal data only for account operation, payment records, security checks, legal duties, and dispute handling. When retention is no longer needed, we delete, anonymise, or isolate the data according to its category.

Corrections and requests

You can ask us to correct inaccurate account data, provide a copy, or explain how a category is used. We will verify ownership before acting so your privacy request stays tied to you.

Privacy Policy questions before you join

Before you open an account, you should know how your data is handled across registration, login, wallet activity, game launch, and support contact. These answers focus on privacy rights, collection purposes, cookies, retention, payment records, and access limits. If a question is specific to your account, contact us after logging in so we can verify ownership first.

It covers data you provide, records created through your account, device and cookie signals, wallet entries, support messages, and security logs. We use these records for account operation, privacy support, payment matching, and protection against misuse.

Yes, game launch activity can create session records, device signals, time stamps, and account identifiers. We use them to keep your session linked correctly, investigate technical issues, and protect account and wallet records.

Cookies help maintain login sessions, remember selected settings, measure errors, and detect unusual access patterns. You can manage cookies in your browser, but some account, lobby, or wallet functions may need them to work properly.

Yes, you can ask for access to personal data linked to your account. We will verify your identity first, then provide the relevant categories or explain if a legal or security reason limits disclosure.

Payment records are kept for wallet operation, withdrawal verification, dispute handling, security checks, and legal duties. The exact period depends on the record type, after which data may be deleted, anonymised, or separated from active systems.

Only staff roles that need the request for privacy handling, account verification, payment checks, or security assessment can access it. We keep routing narrow so your personal data is not shared across unrelated teams.

Access and eligibility depend on local law and are available where local law permits. If a legal limit affects your account, we may restrict features while still handling privacy requests through verified support channels.