Reference

Legal access for your rsnvip1 account

rsnvip1 sets out its Legal position in plain English so you can check access, account duties and privacy handling before opening an account.

Local law appliesPhone verificationPrivacy controlsWallet records
rsnvip1 Legal access for your rsnvip1 account
CONTACT ROUTES

Get Legal help beside account support

A clear contact path matters when a Legal question affects your account, wallet status or access request.

Account policy route Use the support path beside your account controls when you need clarification about phone verification, duplicate account concerns or a request to correct account details. We use the registered phone number to match your message and keep the Legal question attached to the right record.
Wallet record check For a Legal question involving DANA, OVO, GoPay or QRIS, include the payment reference and approximate time rather than your wallet password. We can compare the receipt with the account record and explain which policy step applies to a pending or disputed transaction.
Access clarification If a page is unavailable in your location, contact support through the account route and state your country or region. We will explain that access depends on local law and point you to the applicable wording instead of suggesting a workaround around a location rule.
DATA PRACTICE

How our Legal controls handle records

Our Legal process is tied to practical account controls rather than broad statements. We use phone verification before account access, review transaction references when a wallet record needs matching, and keep policy…

Account identity

Phone verification gives us an account reference before access is completed. If your phone number changes, request an update through the account contact route and provide the details needed to confirm ownership. We do not treat an unverified message as authority to alter account records.

Payment matching

DANA, OVO, GoPay and QRIS references can help us investigate a Legal or transaction question. We compare the payment reference with the account record, while asking you to hide passwords, wallet PINs and unrelated personal details from any receipt you share.

Cookie choices

Necessary cookies help keep an authenticated browser session connected to the correct account. You can manage optional cookie permissions in your browser settings, although removing necessary cookies may interrupt the policy page, phone verification flow or return to the lobby.

Account security

We keep password and phone details within the account process and ask you to use the registered contact route for Legal requests. Never place a password, wallet PIN or full security code in a support message, even when the question concerns access or payment records.

Record retention

Some account, policy and transaction records may need to remain available for operational, dispute or legal reasons. If you ask how long a particular record is kept, identify the account and record type through support; we will respond according to the applicable Legal wording.

Change requests

To request a correction to your name, phone detail or account record, use the support route connected to your account. We may ask for a verification step before making a change, because Legal requests must be linked to the account holder rather than an unrelated contact.

Legal answers before account access

These Legal answers address the questions we expect you to ask before opening an rsnvip1 account in Indonesia. They cover local access, personal data, wallet evidence, cookies, corrections and contact steps. Read the relevant answer first, then use the account support route if your circumstances require a policy response tied to your own record.

It means access and eligibility depend on local law and your location. Our Legal page explains the account, privacy and payment-record rules that apply to the service. Check the wording before phone verification, and do not rely on access from another region as a way around local requirements.

Phone verification connects the account request to a contact detail you control before access is completed. It also helps us handle account corrections and Legal questions without exposing records to an unrelated person. Use the registered number through the account route, and never send your security code in a message.

A DANA or QRIS reference can help us match a payment question to the correct account record. We may ask for the reference, amount and approximate time, but you should hide wallet PINs and passwords. The record is used to investigate the stated issue, not to request secret access details.

Yes, send a correction request through the support route connected to your account. Tell us which field is wrong and provide the registered phone detail so we can verify the request. We may ask for additional proof before changing a record, especially where the change affects account ownership.

Necessary cookies can keep your browser session connected to the correct account and support the phone verification path. Your browser usually lets you manage optional cookies. If you remove necessary cookies, some account or policy functions may stop working until the required session setting is restored.

Use the account support route and identify the type of record, such as a profile detail, policy request or QRIS transaction reference. We will explain the applicable retention wording. Some records may need to remain available for operational, dispute or legal reasons under the relevant rules.

Support can explain the Legal wording and help with an account record, but eligibility depends on local law. Tell us your location through the account contact route, and we will direct you to the applicable policy page. We cannot suggest a workaround when a regional rule restricts access.