Reference

rina 4d Privacy Policy For Your Account

The rina 4d Privacy Policy explains what we collect, why we use it and how you can ask about your details before opening an account.

Account clarityWallet dataCookie choicesPhone verification
rina 4d rina 4d Privacy Policy For Your Account
CONTACT YOUR WAY

Get Privacy Policy Help Before Access

A clear contact route helps you understand the Privacy Policy before you finish the account path. Tell us whether your question concerns phone verification, a cookie choice, a wallet reference or a request to change personal details. Include the account phone number only through the secure support route, and do not send a wallet PIN. We can use the payment receipt or status reference for DANA, OVO, GoPay or QRIS to locate the relevant record without asking for private wallet credentials.

Team online

Account questions

Ask us to explain which account details support phone verification, login protection or a request connected with your Privacy Policy rights. We will use the account path to identify the relevant record and may ask for a confirmation step before discussing personal data.

Wallet records

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the receipt reference through our support path. We can check the matching status and explain which payment details are retained, while avoiding requests for your wallet PIN or full private wallet credentials.

Access concerns

When you cannot reach your account or policy page, tell us the device path you used, such as mobile browser or desktop browser, plus the visible error. We use that context to separate a security event from a local access issue where local law permits.

DATA HANDLING

How We Apply This Privacy Policy

We keep the Privacy Policy practical by connecting each data use to an account or support task.

Data we receive

We may receive your phone number, account identifiers, verification results, browser details, device signals and support messages. For a payment, the record may include a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference used to match status with your account.

Cookie controls

Necessary cookies help maintain a signed-in session and remember choices made on the Privacy Policy page. Other cookie signals may help us understand page loading and security patterns. You can manage available browser cookie controls, although disabling necessary cookies may interrupt account access.

Account security

We use phone verification and session checks to reduce account misuse. If a login looks unusual, we may pause a step and ask you to confirm account control. Never share your password, verification code or wallet PIN with another person or through a support message.

Record retention

We retain account, verification, support and transaction references only for the operational, security and legal purposes connected with the service. Retention can differ by record type. Ask through the support path if you need us to explain why a specific record remains available.

Correction requests

You can ask us to correct an inaccurate phone number, account detail or support record. Give enough context for us to locate the entry, then complete any identity check we require. We will explain if a transaction or security record must remain unchanged for a valid reason.

Third-party services

Wallet and banking rails may process their own transaction details under their own terms. Our Privacy Policy concerns the references and status signals connected with your account, while DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI manage their own banking or wallet systems.

Privacy Policy Answers For rina 4d

These Privacy Policy answers address the questions we expect before account access: what data is collected, how wallet references are used, how cookies work and how you can request a change. We keep the answers tied to the account path rather than describing unrelated lobby functions. If your case involves a specific payment receipt, device or verification event, include that detail through the support path so we can respond to the correct record.

It explains how we handle account details, phone verification records, device and session signals, cookies, support messages and payment references. The Privacy Policy also describes why we use those details, how we protect account access and how you can ask for clarification or correction.

No. Our account record may contain a DANA or QRIS transaction reference and status needed for matching, but we do not ask for your wallet PIN. Do not send a PIN or verification code to support. Wallet providers manage their own private credentials.

Device and browser signals help us maintain a session and identify unusual login behaviour. They can show whether you used a mobile browser or desktop browser and help diagnose a failed account step. These signals support security and access handling rather than replacing phone verification.

Use our support path and state which account detail appears wrong, such as a phone number or profile entry. We may request an account confirmation step before making a change. For a payment record, include the DANA, OVO, GoPay or QRIS reference without sharing private wallet credentials.

Yes. Ask through support for a description or copy of the personal data connected with your account. Include the account phone number only through the secure route. We may need to confirm account control, and some security or transaction records may remain for a valid operational purpose.

Necessary cookies help keep your signed-in session and remember choices made while you read the Privacy Policy. Browser settings can restrict cookies, but disabling necessary ones may prevent a login step or policy page from working correctly. We explain available choices when you contact support.

Yes. Account access and eligibility depends on local law. We apply the Privacy Policy to the data connected with your account and will explain an access-related question through support where local law permits. You should check the rules that apply to your location before completing account access.