Reference

Privacy Policy for Indonesia accounts

Your account data, DANA, OVO, GoPay, and QRIS payment references, and cookie choices are handled under this Privacy Policy before you open the lobby.

DANA contextOVO contextGoPay contextQRIS contextCookie choices
sboagen Privacy Policy for Indonesia accounts
CONTACT PATHS

Ask us about your privacy data

Privacy questions need a direct route, not a generic inbox. You can reach us through live chat inside the account area, WhatsApp during Indonesia service hours, or email for requests that need identity checks and written replies. We may ask for your username, registered phone number, recent payment reference, or a screenshot of the privacy issue so we can handle your request without exposing another account.

Team online

Live chat

Use live chat from the account menu when you need a quick privacy check on cookies, login records, or payment matching. Our chat desk is available 24/7 and may ask you to confirm your registered phone number.

WhatsApp

Message our WhatsApp line between 09:00 and 23:00 WIB for privacy questions tied to DANA, OVO, GoPay, or QRIS references. We use account questions before discussing personal data in the chat thread.

Email desk

Send longer privacy requests to [email protected] when you want account data corrected, exported, or removed where available. Email lets us confirm identity, track the request, and reply with a written record.

DATA HANDLING

How we manage account privacy

We run privacy controls through the same account flow you use for login, wallet checks, and support.

Data we collect

We collect the data needed to create and maintain your account: username, phone number, email address, password status, login time…

Payment records

DANA, OVO, GoPay, and QRIS references are stored as transaction records so deposits and withdrawals can be matched to your…

Cookie choices

Cookies help keep your session active, remember language settings, and detect repeated failed logins.

Account security

Check Menu > Account > Security after changing phones or browsers.

Retention periods

We keep account, payment, and support records for as long as needed to manage your account, settle disputes, and meet…

Change requests

Ask us to correct a typo, update your phone number, or check stored account data through live chat or email.

Common privacy questions before joining

These answers focus on how our Privacy Policy works when you create an account, use cookies, send payment references, or contact support. If your request involves access, eligibility, or account closure, we check it against local law and your verified account details before acting. For anything personal, contact us from the registered account so we can confirm it is really you.

We ask for account data such as username, password, phone number, and contact details. We may also record login time, device signals, payment references, and support messages so your account can be verified and maintained.

We use payment references to match deposits and withdrawal requests to your account. The Privacy Policy covers amount, time, reference status, and support proof, but we do not access your wallet PIN or app password.

Yes. Contact live chat or [email protected] from your registered account and explain what is wrong. We may ask for your username, phone number, and a recent payment reference before making the correction.

Our cookies are used for session access, language settings, basic analytics, and security checks. You can remove them in your browser settings, but clearing cookies may sign you out and reset saved preferences.

Only staff who need the record for support, payment matching, account checks, or privacy handling can access it. We limit access by role and may mask data when a full record is not needed.

Email [email protected] with your username and registered phone number, then follow the identity check we send back. We will explain what account, payment, cookie, and support records can be shared.

We restrict access where possible, then keep records needed for payment checks, disputes, security, or lawful requests. When retention is no longer needed, records may be deleted, anonymised, or separated from active account access.