Reference

rsnvip2 Privacy Policy for Your Account

The rsnvip2 Privacy Policy explains what we collect when you open an account, sign in on mobile, or check DANA, OVO, GoPay and QRIS status.

Clear collection rulesWallet record contextAccount access choicesCookie explanations
rsnvip2 rsnvip2 Privacy Policy for Your Account
CONTACT PATHS

Where To Ask About Privacy Policy

A privacy question should have a clear route, so we connect policy requests with the account and cashier context that created them. Use the support chat from your signed-in account when you need help identifying a data record, correcting a contact detail or checking why a wallet reference appears. If you cannot sign in, use the account access contact path shown on the site and include only the details needed to locate your request. We may ask for an account step to confirm that the request comes from you.

Team online

Account support chat

From your signed-in account, open support chat and ask about the Privacy Policy, stored contact details or a correction request. We can connect the question with your account record without asking you to place DANA, OVO, GoPay or QRIS passwords in a message.

Cashier data check

If your question concerns a wallet reference, tell us whether it relates to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. Share the visible reference and date only; we use that narrow detail to find the relevant record.

Access recovery path

When sign-in blocks a Privacy Policy request, follow the account access contact path on rsnvip2 and explain which step stopped you. We may confirm your registered contact detail before discussing stored data, helping keep another person from receiving account details.

DATA PRACTICES

Inside rsnvip2 Privacy Controls

We handle policy requests as account tasks rather than casual messages. Our process separates identity checks, wallet references and device signals so a request can be answered with the right record.

Collected account details

We may use the contact details and verification responses you enter during account creation, along with sign-in events and support messages. These records help us confirm the right account during a correction or access request and reduce confusion between similar wallet references.

Cookies and device signals

Cookies can remember selected settings and support the path from login to the lobby. Device type, browser details and timing signals may be reviewed when access looks unusual. You can manage browser cookie controls, though changing them may affect account sign-in.

Wallet and payment records

A DANA, OVO, GoPay or QRIS reference may be stored with account and cashier records so we can check a status question. Bank transfer and virtual account references may be handled in the same way, without requesting your banking password.

Account security checks

Before discussing private account details, we may ask you to complete a sign-in or phone verification step already linked to your account. This helps us avoid sending personal data to the wrong person when a device, wallet or contact detail has changed.

Retention decisions

We retain information for the period needed to operate the account, investigate a security issue, resolve a payment record or meet a legal requirement. When a record no longer serves one of those purposes, we review it for deletion or removal from active use.

Requests and corrections

Ask us to explain a stored detail, correct an error or discuss removal through the account support path. Include the request type and registered contact detail, not a wallet password. Where local law permits, we will assess the request and explain any necessary limitation.

Privacy Policy Questions About rsnvip2

These Privacy Policy answers address the account questions you are most likely to have before opening an account or contacting support. They explain what happens around sign-in, wallets, cookies, corrections and deletion without asking you to publish private details. If your situation is different, use the account support path and describe the exact policy point you want us to check.

The rsnvip2 Privacy Policy covers account details, verification responses, sign-in activity, device signals, cookies, support messages and wallet references. It explains why we use those records, how we protect account access and how you can ask about correction, access or deletion where local law permits.

We collect the contact and verification details you provide during the account path, then create records for sign-in, support and relevant cashier activity. We may also receive a DANA, OVO, GoPay or QRIS reference needed to identify a wallet status question.

Yes. The Privacy Policy explains that cookies can retain settings and support the sign-in path on a mobile browser, while device and timing signals may help identify unusual access. You can change browser cookie controls, although some account steps may then work differently.

We use wallet references to match a payment status with the correct account record, not to request your wallet password. For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share only the visible reference and date through the account support path.

You can ask what account data we hold or request a correction through support chat after signing in. We may complete a phone verification or another account step before replying. This confirms your identity and helps prevent private details being sent to someone else.

We keep records while they are needed for account operation, security checks, payment questions or legal requirements. Retention can differ by record type. We review information that no longer serves one of those purposes for deletion or removal from active use.

You may request deletion through the account support path, and we will assess it under the Privacy Policy and local requirements. Where local law permits, we remove eligible data; some records may need to remain for security, payment resolution or legal reasons.