Rujukan Laman

ironman66 Privacy Policy for Your Account

At ironman66, we set out our privacy policy in plain English so you can see what account details, cookie records and support messages we keep, and why each…

Account dataCookie choicesSupport recordsLocal law

Browse Lobby Read FAQ

How We Handle Your Data

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

This policy applies to account data collected when you open, use, or ask us to close a profile. Depending on the law that applies to your location, we may collect contact details, login records, device signals, payment references, and the messages you send to support. We

1
use those details to verify identity, process requests, keep the account secure, and meet recordkeeping duties. If local law gives you a right to see, correct, or remove certain data, we will handle the request after identity checks and only share what the law allows. When
2
a rule in your jurisdiction conflicts with this policy, the local rule wins. Our handling for Malaysia accounts follows the same standard wherever 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 need a privacy change, we keep the route simple. Send the request from the contact path tied to your account, describe what you want…

CARE AND RETENTION

How We Keep Data in Check

We treat privacy handling as part of account operations. That means we limit collection to what we need, tie cookies to login sessions and language choice, and protect account changes with verification…

Collection scope

We collect only the details needed to open and run your account: name, contact route, login history, device data, payment references, and messages you send to us. We do not ask for extra fields unless the law or a clear account need requires them.

Cookie use

Cookies help us keep you signed in, remember language settings, and save form choices while you move between pages. If you clear them, some settings reset and you may need to sign in again.

Account security

We protect access with password checks, session expiry, and risk flags for unusual logins or change requests. If a request looks risky, we may pause it until you confirm through the contact route on file.

Retention rules

We keep records for the time needed for account support, dispute handling, fraud checks, audit duties, and legal duty periods. After that, we delete, anonymise, or archive the data according to the reason it was stored.

Access and correction

You can ask to see or correct selected data by sending a request from your registered route. We may ask for proof of identity before we release a copy or update the record.

Privacy contact

If a record looks wrong, incomplete, or out of date, tell us exactly what should change and attach any proof you have. We use that to process the request and update the file in a controlled way.

Common Privacy Questions for Your Account

This section answers the questions we hear before you send a privacy request or open an account. Each answer stays tied to data use, cookies, security, retention, and the routes you can use to contact us. If your case depends on country rules, we follow the law that applies where you access the account, and we only share what those rules allow.

It covers account sign-up details, login records, device signals, payment references, support messages, and cookie choices tied to your session. If local law sets a different rule, we follow the rule that applies where you access the account.

We collect the details needed to handle your account and requests: contact route, identity checks, device data, browser data, and the message history you send to support. We do not collect extra data without a clear reason.

Cookies help us keep you signed in, remember language settings, and make form fields work the way you left them. They also help us spot unusual activity that could affect account security.

We keep records only as long as needed for account handling, dispute checks, fraud screening, audit duties, and other legal duties. When that reason ends, the record is deleted, anonymised, or archived.

Yes. Send the detail you want changed, explain what is wrong, and add proof if you have it. We may verify your identity first, then update the record if the request is valid.

Yes, you can ask for a copy of selected account data from your registered contact route. We may redact details that belong to another person or that the law says we must keep private.

Use the contact path linked to your account and describe the issue in clear terms. If the request is about access, correction, or deletion, we route it to the team that handles privacy matters.

ironman66 Privacy Policy for Your Account

Where to Send Privacy Requests

How We Keep Data in Check

Collection scope

Cookie use

Account security

Retention rules

Access and correction

Privacy contact

Common Privacy Questions for Your Account

01 What does this privacy policy cover?

02 Which details do you collect from me?

03 Why do you use cookies?

04 How long do you keep my data?

05 Can I ask for a correction?

06 Can I ask for a copy of my data?

07 Who do I contact about privacy?

Related Pages