Reference

gading33 Privacy Policy for Your Account

Our gading33 Privacy Policy explains how we handle your account details, login activity and wallet records when you use DANA, OVO, GoPay or QRIS.

Account data explainedWallet records coveredCookie choices includedRequest path available
gading33 gading33 Privacy Policy for Your Account
CONTACT HELP

Privacy Questions Near Your Account Path

A clear contact path helps you act on this Privacy Policy without searching through unrelated pages. We can help you identify the account connected to a wallet receipt, explain a data request and check whether a login event belongs to your device. Start from the support route available beside the account or cashier area, and include enough detail for us to locate the correct record.

Team online

Account access request

Ask us to confirm which account details are linked to your phone verification step. Use the support route shown on the login path so we can match your request safely.

Wallet record question

Send the payment rail, receipt reference and approximate transaction date when asking about DANA, OVO, GoPay, QRIS, bank transfer or virtual account data.

Privacy change request

Tell us whether you want to access, correct or question a stored detail. We may ask for account checks before changing records connected to your identity.

DATA CARE PRACTICE

What We Do With Your Account Data

Our handling process follows the account actions you take, from phone verification through wallet status checks and lobby access.

Account details

We use contact and verification details to create your account, confirm account ownership and respond to requests about stored data. A clear account step helps prevent records being shown to the wrong person.

Device activity

Login time, browser signals and security events may be recorded to identify unusual access. This can apply when you move from a mobile lobby session to a desktop session.

Cookies

Cookies can keep your session active, remember basic page choices and help us understand whether a policy page loads correctly. You can manage browser cookie settings on your device.

Payment references

We retain transaction references and wallet status details needed to match receipts, resolve account questions and check payment activity. We do not need your wallet password to answer a receipt query.

Security checks

Phone verification, login signals and account matching help us protect access. If a request concerns another person’s account, we may ask for additional proof before responding.

Retention requests

You can ask why a record is held, request a correction or ask about removal. We will explain any continued retention needed for account security, payment records or legal duties.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. If your situation is specific, use the account support path with your payment reference and the device step involved.

It covers account details, phone verification, device activity, cookies, wallet references, support requests, retention and the steps available when you ask to access or correct your data.

Phone verification helps us confirm account ownership before access and before discussing stored details. It also helps us connect a support request to the correct account rather than another person’s record.

Yes. The policy includes payment references and wallet status connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity used during account support.

Use the support route beside the login or cashier area and state whether you need access, correction or clarification. Include your account contact and relevant record details so we can check ownership.

Cookies may support your session, basic page settings and technical checks on a mobile browser. You can review cookie controls in your browser settings, although some account steps may then work differently.

Retention depends on why the record exists, including account security, payment matching, support handling and legal duties. Ask us about a specific record and we will explain the applicable reason.

You can request access through the account support path, subject to identity checks and local requirements. Service access itself depends on local law, and we apply the rules relevant to your request.