Reference

Privacy Policy for rina 4d Accounts

Our Privacy Policy explains how rina 4d handles the account details, wallet records and device data you provide when you open an account.

Account clarityWallet recordsMobile access

Explore Our Lobby Read FAQ

How Wallet And Account Data Moves

rina 4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

When you create an account, we collect the details needed to identify the account, confirm phone access and keep sign-in activity connected to the right profile. Payment records can show the rail you selected, such as DANA, OVO, GoPay, QRIS, bank transfer or a virtual account,

1
along with status details needed to match a deposit or withdrawal request. We use device and browser signals to help detect unusual access, while cookies can remember settings for the lobby. We retain records for the period needed for account service, security checks and legal duties
2
where local law permits. If you are in Denpasar, Yogyakarta or elsewhere in Indonesia, the same request path applies. The Privacy Policy may change when our data practices change; we will present the current wording on this page. Access depends on local law.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH REQUESTS

Get Help With Privacy Policy Requests

A clear request path helps you ask about the data connected to your account without explaining the same issue repeatedly.

DATA HANDLING DETAILS

What We Keep Clear About Privacy

Privacy work is part of the account path, not a separate message shown after a payment issue.

Account details

We use account details to create your profile, support phone verification and connect sign-in activity with the correct account. You can ask us to clarify a stored detail or request a correction where local law permits.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry may be retained with its status so we can match account activity to a payment request. We do not need your wallet password to check that record.

Cookies

Cookies can remember selected settings and help the lobby load consistently on your device. You can manage cookie settings through your browser, though changing them may affect sign-in continuity or saved preferences.

Security signals

We may examine browser, device and sign-in signals when access does not match the account pattern. These checks help us ask for the right account step without treating every mobile or desktop change as a problem.

Retention

We keep data only while it supports account service, payment reconciliation, security checks or a legal requirement that applies where local law permits. Retention can differ by record type and does not mean every detail is kept forever.

Change requests

To request a change, describe the specific field, record or cookie concern and identify the account route involved. We may need an account check before acting, so your details are not changed from an unverified request.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the records you create through account access, wallet activity and device use. We keep the wording tied to rina 4d and the Indonesia account path so you know what to ask before opening an account or requesting a data change.

The Privacy Policy covers account details, phone verification, wallet and payment records, cookies, device signals, retention and requests to access or correct data. It applies to the account path where local law permits, and access depends on local law.

Phone verification helps connect account access to the person using the sign-in route and can reduce confusion when a device changes. We use the verification step for account handling, not as a reason to request your wallet password.

Yes. The Privacy Policy includes payment records linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. These records can include the selected rail and status needed to match an account request.

Describe the exact account field or record that needs correction and identify the sign-in route connected to it. We may ask for an account check before changing anything, and requests are handled where local law permits.

Cookies may remember settings and help your mobile browser keep the account path consistent. You can adjust them through browser controls. If you remove or block cookies, sign-in continuity and saved lobby preferences may change.

We retain payment data for the period needed for account service, payment matching, security checks or legal duties that apply where local law permits. The period can vary by record type, so you can ask about a specific entry.

Yes. You can ask us to clarify the device or browser signals connected with an account access concern. Include the device path and approximate sign-in time, but do not send a password or full payment credentials.

Privacy Policy for rina 4d Accounts

Get Help With Privacy Policy Requests

What We Keep Clear About Privacy

Account details

Payment records

Cookies

Security signals

Retention

Change requests

Privacy Policy Answers For Your Account

01 What does the rina 4d Privacy Policy cover?

02 Why does rina 4d need my phone verification?

03 Does the Privacy Policy include DANA and QRIS records?

04 How can I request a correction to my account data?

05 Does rina 4d use cookies on mobile devices?

06 How long does rina 4d keep my payment data?

07 Can I ask what device data is linked to my account?

Related Pages