Reference

Privacy Policy for Your rgamesstore Account

Your rgamesstore Privacy Policy explains what we collect when you open an account, check DANA or QRIS status, and move between the lobby and your wallet.

Account dataWallet recordsCookie choicesRequest support
rgamesstore Privacy Policy for Your rgamesstore Account
CONTACT PATHS

Get Privacy Policy Help Beside Account Support

A clear support request helps us find the right account record without asking you to repeat sensitive details in an open message.

Account request Use the account support path for a Privacy Policy question about your name, phone…
Wallet reference For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, share the transaction…
Policy clarification If a Privacy Policy paragraph is unclear, tell us the section or wording that…
DATA PRACTICES

What We Do With Account Data

We keep the Privacy Policy practical by linking each data use to an account task: phone verification supports sign-in, device signals help us investigate unusual sessions, and payment references help match a…

Account details

We may use your name, phone detail, and sign-in identifiers to create and maintain your account. Phone verification helps us confirm that an access request belongs to the account holder before account information is shown.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference can be stored with an account event so we can match status questions. We do not need your wallet password to investigate that reference.

Cookies

Cookies can remember a session choice, maintain sign-in flow, and help us understand whether a page is functioning. You can review cookie controls in your browser, though changing them may affect account access or saved preferences.

Device signals

We may record browser type, device characteristics, IP address, and session events when you use a phone or desktop. These signals help us identify unusual access and diagnose why a login or lobby session stops.

Retention

We retain account, payment-reference, and support records only as long as needed for account operation, dispute handling, security checks, or legal duties. When a record is no longer needed, our handling follows the applicable retention process.

Your request

You can ask us to explain, correct, or review personal data connected with your account. Send the request through account support, identify the relevant phone detail or reference, and we may verify ownership before making a change.

Privacy Policy Questions About rgamesstore

These Privacy Policy answers address the searches we hear most often before account creation or a wallet check. They explain the practical data path from phone verification to browser cookies and payment references. If your situation involves a specific account record, use the support route rather than placing private details in a public message.

The rgamesstore Privacy Policy covers account details, phone verification, sign-in events, device and browser signals, cookies, support messages, and payment references. It explains how we use those records for account operation, status checks, security review, retention, and requests where local law permits.

No. We may keep a payment reference or status event connected with your account, but you should never send a wallet password or security code to support. For DANA, OVO, GoPay, and QRIS questions, provide the relevant reference only.

Device type, browser details, IP address, and session events help us recognise unusual access and investigate a failed login. The same signals can show whether a phone or desktop session reached the lobby correctly, without requiring your wallet password.

Cookies can keep a session active, remember selected preferences, and help us identify page problems. You can change cookie settings in your browser. Some changes may remove saved choices or interrupt sign-in, so check the account path again afterward.

Yes. Send a request through account support and identify the phone detail, profile field, or payment reference that needs checking. We may verify account ownership before changing data, and the available action depends on local law and retention duties.

We keep account, support, payment-reference, and security records for as long as needed for account operation, dispute handling, security checks, or legal duties. The applicable retention period can differ by record type and local requirements.

Where local law permits, you can ask us to explain or review personal data connected with your account. Use the support path, identify the account detail involved, and complete any ownership check needed before we respond.