Reference

Privacy Policy for Your maskot33 Account

maskot33 Privacy Policy shows what we collect when you open an account, use DANA or QRIS, and move between the lobby and wallet pages.

Account data explainedWallet records coveredMobile and desktop access
maskot33 Privacy Policy for Your maskot33 Account
CONTACT ROUTE

Where to Ask About Account Data

A clear support route helps when you need to understand a record rather than guess what happened.

Privacy questions Use the support route linked from your account area to ask which personal details we hold, why a record is needed, or how the Privacy Policy applies to your maskot33 access.
Wallet references For DANA, OVO, GoPay or QRIS questions, share the payment reference and approximate time, not a wallet PIN. We can compare the reference with the account record while keeping secret credentials out of support.
Account corrections If your phone number, device record or account detail is inaccurate, tell us what needs changing and why. We may ask for an account step that confirms the request belongs to you.
SECURITY PRACTICE

How maskot33 Handles Your Account Records

Privacy work is part of the account path, not a separate promise hidden from the cashier page.

Data collection

During account opening, we collect details needed for phone verification and access. Browsing Live Roulette Wheel or Fishing War Quick Arena can also create technical logs such as browser type, session time and device signals.

Wallet handling

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us reconcile an account action. We do not ask support to collect your wallet PIN, full password or other secret access code.

Cookie choices

Cookies can keep a signed-in session working and remember selected settings. You can review cookie controls in your browser, although blocking necessary cookies may interrupt phone verification or the account path.

Account security

A new device, unusual login time or repeated verification attempt may create a security signal. We use that signal to protect the account and may ask you to confirm ownership before changing sensitive details.

Record retention

We keep account, payment-reference and support records for the period needed to operate services, resolve disputes, protect access or meet applicable obligations. When that purpose ends, we delete or anonymise the record where practical.

Policy requests

Ask us to access, correct or explain your personal data through the account support route. State the request clearly and include a safe account identifier; we may verify ownership before releasing or changing records.

Privacy Policy Answers for Indonesia Accounts

These Privacy Policy answers focus on the records you are most likely to notice while opening or using an account from Indonesia. We keep the request path practical: identify the account, describe the record and tell us the change or explanation you need. Where access or eligibility is discussed, it depends on local law.

It covers information connected with your account, phone verification, sign-ins, device signals, cookies, support messages and payment references. It also explains retention, security, access requests and how DANA, OVO, GoPay or QRIS records may be matched to an account.

Phone verification helps us confirm that an account request belongs to you and supports account recovery or sensitive changes. We record the verification result and related technical details, not a replacement for your password or wallet PIN.

Yes. The Privacy Policy covers references showing an account action through DANA, QRIS, OVO, GoPay, bank transfer or a virtual account. These references help us reconcile status and investigate support questions without requesting secret wallet credentials.

Use the support route beside your account area and ask for a personal-data access request. Include a safe account identifier, the email or phone detail connected to the account, and the records you want us to locate. We may verify ownership first.

Yes. Tell support which detail is inaccurate, what the correct detail should be and why the change is needed. For a phone number or identity-related field, we may require an account verification step before applying the correction.

We retain records for operational needs, account security, dispute handling or applicable legal purposes. The period depends on the record and its purpose. When retention is no longer needed, we delete or anonymise the data where practical.

Contact us through the account support route and name the page, device and approximate time involved. You can also adjust cookie settings in your browser. Necessary cookies may be required for sign-in, phone verification and account security.