Reference

Open glo33 Privacy Policy before account access

glo33 Privacy Policy explains what we collect when you create an account, sign in, use DANA or QRIS, and browse titles such as Auto Roulette Live.

Account dataWallet recordsDevice securityCookie choices
glo33 Open glo33 Privacy Policy before account access
CONTACT PATHS

Ask about account or wallet records

A clear contact path helps when you want to ask what the Privacy Policy means for your account.

Account data request Use the account support link to ask which personal details are connected with your…
Wallet record question For a DANA, OVO, GoPay or QRIS record, share the date, payment route and…
Policy change request If a detail is outdated, ask through the same support path and state the…
HANDLING PRACTICES

See how device and cookie data works

The Privacy Policy is applied through practical account controls rather than a single broad collection rule.

Account details

We handle the details you provide during account creation and phone verification, such as contact data needed for access.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create transaction references.

Device signals

When you sign in from a phone or desktop browser, we may record technical signals such as session timing and…

Cookie settings

Cookies can keep a selected language, session setting or security state available while you move through the account path.

Retention approach

We retain account, payment and support records for the period needed for account operation, security checks, dispute handling or legal…

Your request route

You can ask for access, correction or clarification through the account support link.

Find Privacy Policy answers for your account

These Privacy Policy questions cover the account steps most relevant to Indonesia access: phone verification, wallet references, cookies, device checks and requests for changes. We keep the answers tied to glo33 records so you can decide what to provide before opening an account. If your question concerns a specific DANA, OVO, GoPay or QRIS reference, use the account support path with the visible transaction details.

It covers account details, phone verification, device and session signals, cookies, payment references, support messages and related activity records. It explains why we handle each category, how retention works and how you can ask about access or correction where local law permits.

We may collect the contact details you submit, the result of a phone verification step, login and session records, device context and support correspondence. Payment routes can add a transaction reference, but you should not send us a wallet password or one-time code.

Yes. The policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match wallet status and account history, while the payment provider remains responsible for its own handling practices.

Use the support link available through your account and ask for an access request. Include your registered phone or email, but omit passwords and one-time codes. We may complete an identity check before sharing records connected with your Privacy Policy request.

You can request a correction through the account support path and describe the exact field that needs updating. We may verify your phone or email first. If a payment record must remain unchanged for reconciliation or legal reasons, we will explain that distinction.

On a mobile browser, cookies may remember a session, selected setting or security state. You can adjust them through your browser controls. Blocking required cookies may interrupt sign-in or account requests, while optional cookies can be managed according to your device settings.

We keep records for as long as they support account operation, security review, payment reconciliation, dispute handling or legal duties. Retention can differ by record type. When those purposes end, we move applicable data toward deletion or secure removal under our handling process.