Reference

rans551 Privacy Policy for Your Account

Our Privacy Policy explains how rans551 handles the details you provide when you open an account, check wallet status, or access the lobby from Indonesia.

Account dataWallet recordsCookie choicesAccess requests
rans551 rans551 Privacy Policy for Your Account
CONTACT ROUTES

Get Privacy Help Beside Account Support

A clear contact path matters when you want to ask about a Privacy Policy request rather than a wallet transaction. We separate account access questions from requests to see, correct, or remove personal details, so your message can reach the right handling route. Include the phone number linked to your account and the subject of your request, but do not send a password or wallet PIN. You can begin from the support route connected to your account area while access remains available.

Team online

Account access

If you cannot sign in, tell us the phone number attached to your account and the device path you used. We can first check the access issue, then help you direct a separate Privacy Policy request without asking you to disclose a password.

Wallet records

For a DANA, OVO, GoPay or QRIS record, include the payment rail and the approximate transaction reference shown to you. We use that context to distinguish a wallet-status question from a request about the personal data held in your account.

Privacy requests

Ask to access, correct, or question the handling of your personal data through the account support path. We may request account verification before discussing records, because a privacy response must reach the person connected with the account.

DATA PRACTICES

How We Handle Your Account Data

Privacy work follows the same account steps you see when moving from login to the lobby: we identify the account, record the action, and restrict sensitive changes until…

Account details

We use your phone number and submitted account details to identify the correct account, send access-related messages, and handle requests…

Payment matching

A DANA, OVO, GoPay or QRIS reference can help us match a wallet action to your account.

Cookies and devices

Cookies and device signals can help maintain your signed-in path and identify unusual access.

Account security

We limit sensitive account changes until the relevant account details are checked.

Retention choices

We keep personal data only for the operational, security, dispute, or legal need described in the Privacy Policy.

Changes and contact

You can ask what personal data we hold, request a correction, or question its use through the privacy route in…

Privacy Policy Questions for rans551

These answers address the questions we expect before you open an account or send a privacy request. They cover the data linked to login, wallet records, mobile access, cookies, retention, and the checks we may need before replying. If your situation is not listed, use the account support path and describe the specific record or action you want us to examine.

It covers personal details linked to your account, login and device signals, cookies, support messages, and payment records connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account steps. It also explains why we use those records, retention, security handling, and your request options.

We use the phone number attached to your account to identify your account, support access checks, and connect a privacy request with the correct record. If you ask about data, we may verify account details before discussing it so personal information is not disclosed to another person.

Yes. The Privacy Policy addresses records showing whether DANA, OVO, GoPay, or QRIS activity was started or matched to your account. Bank transfer and virtual account references may also be used for payment reconciliation, receipt checks, and resolving a wallet status question.

Use the privacy contact route connected to your account support area and ask to access your personal data. Provide the linked phone number and enough detail to locate the request, but do not send a password or wallet PIN. We may complete an account check before replying.

You can request a correction when an account detail is inaccurate or out of date. Contact us through the account support route, identify the field that needs changing, and provide the requested verification. The Privacy Policy explains how we assess and record that change.

Cookies and browser storage can maintain a signed-in path and remember limited session preferences. Clearing them may sign you out of the mobile browser and trigger account verification again. The Privacy Policy explains their role, while your browser settings control whether cookies remain on your device.

Yes. Account access and eligibility depends on local law, including the rules that apply where you are located. The Privacy Policy explains our data handling, but it does not change local requirements. Where local law permits, you can use the stated account and privacy contact paths.