Reference

333a Privacy Policy for your account

Our 333a Privacy Policy explains what account, device and wallet details we use when you open access, sign in and move through the lobby.

Account dataWallet recordsCookie choicesAccess requests
Explore The Lobby Read FAQ
333a 333a Privacy Policy for your account
HELP WITH PRIVACY

Get help with account data requests

A clear support path helps when you want to ask about a Privacy Policy point or correct an account detail. Contact our support route from the account area and include the phone number linked to your access, the relevant date and the transaction or device detail involved. We use those details to locate the right record without asking you to send a wallet password.

Team online

Account questions

Ask us to explain the account data connected with your phone verification or sign-in history. We may request an account step to confirm that the request comes from you.

Wallet records

For DANA, OVO, GoPay or QRIS status questions, share the payment reference and date through the support path. We use that reference to trace the record without requesting your wallet PIN.

Correction requests

If a profile detail is outdated, tell us what should change and why. We compare the request with your account record before applying an amendment or explaining any restriction.

HANDLING YOUR RECORDS

How 333a handles privacy in practice

We keep the Privacy Policy practical by linking each data use to a clear account action.

Account security

Phone verification helps us connect an access request with the right account.

Device signals

Our mobile and desktop pages may record browser type, session timing and technical signals needed to keep a session working.

Cookies

Cookies can retain session choices and help us understand whether a page loads correctly.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference lets us match a payment event with your account.

Retention

We retain account, security and transaction records for as long as needed for the stated service purpose, dispute handling and…

Policy changes

If this Privacy Policy changes in a material way, we will place the updated wording on this page and show…

Privacy Policy answers before access

These Privacy Policy answers address the questions we expect before an Indonesian account is opened or used. They explain the records behind phone verification, mobile access and local payment references, while keeping the route to a specific request straightforward.

It covers account and phone verification details, device and browser signals, cookies, support messages, payment references and activity needed to provide account access where local law permits.

We use phone verification to connect an access request with your account and reduce mistaken or unauthorised changes. It also helps us investigate login problems without exposing another account's details.

Yes. The Privacy Policy covers transaction references linked to DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account references used to match an account event.

We may receive browser type, device signals, session timing and technical error details needed for login security and page operation. We use these signals for account access and troubleshooting, not wallet PIN collection.

Use the account support path and identify the phone number connected with your access, the request type and relevant date. We may confirm your identity before providing details or changing a record.

We keep records for the service purpose, security checks, dispute handling and applicable legal duties. Retention can differ by record type; when no longer needed, data is removed or anonymised.

Yes. Contact our support route with the section or data use you want clarified. We can explain the policy and access conditions, which depend on local law, before you continue.

Related Pages

333a Indonesia Access guide Mahjong Panda About Us E-Sports Arena