Reference

rans4d Privacy Policy for Indonesia Accounts

Our Privacy Policy explains what data we collect when you open an account, use DANA or QRIS, and move between the lobby and Mobile App.

Account dataWallet recordsDevice controls
rans4d rans4d Privacy Policy for Indonesia Accounts
CONTACT THE TEAM

Privacy Help Beside Your Account

A clear contact route matters when a privacy request and a wallet record meet.

Account privacy request Use the support link after login to ask what account data we hold, why it is used, or which details need correction. We may verify your identity first.
Wallet record check For a DANA, OVO, GoPay or QRIS question, include the transaction reference and date. We use that detail to locate the relevant payment record without requesting your wallet password.
Device access concern If Mobile App or browser access shows an unfamiliar session, contact us through account help and tell us the device type. We can review the session path and request account verification.
HOW WE HANDLE DATA

Account Security From Login To Lobby

We handle privacy as an account process rather than a hidden setting. Before access, we may ask for phone verification; during a session, we use device and login signals to identify unusual…

Phone verification

A clear phone verification step connects your account to the contact detail you provide. We use it to confirm access and help distinguish your request from an unknown sign-in.

Session cookies

Cookies can preserve login state and record technical preferences. You can manage cookies through your browser settings, though changing them may affect the account path into Mobile App or the lobby.

Device signals

Browser, device and session signals help us identify unusual access around areas such as Speed Baccarat. They are used for account protection and technical checks, not as a wallet password.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references let us match a payment status with your account. We do not need your wallet password to perform that check.

Retention periods

We retain account, payment and support records only as long as needed for their stated purpose, legal duties or dispute handling. When a record is no longer needed, our process removes it.

Change requests

Send a correction, access or deletion request through the signed-in support path. We may request account details to confirm ownership before changing records or responding about stored data.

Privacy Policy Answers For rans4d

These Privacy Policy answers focus on the account steps you are most likely to question before opening an account. We explain wallet references, cookies, device checks, retention and contact routes in plain terms, while access remains subject to local law and the policy applies where local law permits.

It covers account details, phone verification, payment references, cookies, device signals, session records and support messages created when you use rans4d services where local law permits.

No. We use DANA or QRIS payment references and status details to match activity with your account. We do not need your wallet password for that matching step.

Device type, browser details, IP address and session time help us identify unusual login activity, investigate technical errors and protect the account path before lobby access.

Use the signed-in support link and ask for an account data access request. Include the phone or email connected to your account so we can confirm ownership first.

Yes. Send a correction request through account support and describe the field that needs changing. We may verify your identity before updating the stored account record.

We keep payment references for the period needed for their stated purpose, legal duties and dispute handling. Once no longer needed, the applicable record follows our removal process.

Contact us through the signed-in help path and identify the device or browser you do not recognise. We can review the session details and ask for account verification.