Rujukan Laman

Privacy Control Before You Join

Your privacy choices, account records, cookie settings and local wallet details are set out clearly before you open an account with agn88a.

Malaysia account dataCookie choicesWallet record handlingContact requests
agn88a Privacy Control Before You Join
CONTACT ROUTES

Privacy Help Without Account Guesswork

Privacy requests work better when we can match you to the correct account without asking for more data than needed.

Live chat privacy desk Use live chat when you need a quick check on cookie settings, login alerts or wallet record status. Our team may verify account ownership, then route the privacy matter to the right queue.
Email data request Send email when you want access, correction, deletion or retention details in writing. Include the account email and a clear request so we can respond without asking for unrelated personal data.
Account security contact Reach the security contact if you notice unknown logins, changed contact details or wallet activity you do not recognise. We can freeze selected privacy-sensitive actions while we verify ownership.
ACCOUNT CARE

How agn88a Keeps Privacy Practical

We keep privacy controls close to the places where your data is created: account access, wallet checks, game-session records and contact requests.

Data we collect

We collect account identifiers, contact details, device signals, wallet references and session records when you use the lobby. Game titles such as Speed Roulette or Crazy Time may create session logs linked to security and dispute checks.

Why we use it

Your data helps us maintain account access, match Touch 'n Go, GrabPay, Boost dan FPX records, respond to requests and investigate unusual activity. We limit use to account operation, safety checks and required record keeping.

Cookie choices

Cookies help keep you signed in, remember language choices and measure whether privacy screens load correctly. You can adjust browser settings, though blocking some cookies may affect secure login and wallet confirmation flows.

Account security

We use password controls, session checks and verification prompts when account details change. If a login pattern looks unusual, we may ask for extra confirmation before showing wallet records or changing personal data.

Retention periods

We keep data only for as long as it is needed for account operation, legal duties, payment checks, dispute handling or security audits. When a record is no longer needed, we delete or anonymise it.

Request handling

You can ask to access, correct or delete data where the request fits legal and operational rules. We may need proof that you control the account before making privacy-related changes.

Privacy Answers Before You Start

These answers focus on how the Privacy Policy works in daily account use. They explain what data we collect, why wallet records matter, how cookies fit in, and how you can reach us if something needs changing. The policy may update as our services, partners or legal duties change, so check this page again when you manage your account.

We collect details needed to create and protect your account, such as name, contact details, login credentials, device data and wallet references. We may also keep verification records used to confirm ownership or handle disputes.

We keep wallet references and transaction records to match payments through Touch 'n Go, GrabPay, Boost dan FPX, confirm account balances and handle queries. We do not need your full banking password or one-time security codes.

Yes. Contact us through live chat or email and state that you want account data access. We will verify ownership first, then provide data that can be shared under applicable law and operational rules.

Send the correct detail through the privacy contact path and include enough account identifiers for matching. We may ask for proof before changing names, phone numbers, email addresses or wallet details linked to your account.

We may share limited data with partners that handle hosting, payment routing, security screening, messaging or customer contact. They are expected to use the data only for the task we assign and protect it appropriately.

Cookies support secure login, remember selected settings and help us check whether policy pages and account screens load properly. You can adjust browser controls, but some settings may reduce login or verification functions.

Send a deletion request through email or chat and identify the account clearly. Some records may need to remain for legal duties, payment reconciliation, security checks or dispute handling before they can be removed.