Reference

34R Privacy Policy For Your Account Data

Our 34R Privacy Policy explains what we collect when you open an account, verify your phone and use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet detail controlsDevice access choicesSupport-led requests
34R 34R Privacy Policy For Your Account Data
REQUEST SUPPORT

Browse Your Privacy Support Routes

A clear support route helps when a privacy question is separate from a wallet status check. We direct you to the account help path beside the cashier area, where you can identify the relevant account step and send a focused request. Keep your phone verification details ready, but never send a password or wallet PIN.

Team online

Account access

If you cannot reach your account after phone verification, use the support path beside the cashier area. We can help identify the access record involved without asking for your wallet password.

Data request

Ask us to explain, correct or provide account data connected with your Privacy Policy request. Include the contact detail used on 34R so we can match the request safely.

Wallet reference

For DANA, OVO, GoPay or QRIS questions, share the transaction reference rather than private wallet credentials. This lets our support route check the relevant record while limiting exposure.

DATA PRACTICES

Explore How We Handle Privacy Requests

Privacy choices should be understandable at the same point where your account is used. We separate account identity, payment references and device signals for practical service tasks, then limit access to the…

Account data

When you open an account, we use the contact detail and phone verification record needed to recognise your account. We do not ask you to place a wallet password into our support messages.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us reconcile an account action. We use the reference for that task rather than collecting your banking login.

Device signals

We may record device and connection signals when you sign in or move between pages. These signals help identify unusual access and keep a phone-verified account linked to the right session.

Cookies

Cookies can keep your selected session and account pages connected while you move from login to the lobby. You can manage cookies in your browser, with some access steps affected if they are refused.

Retention

We retain records for the period needed to provide account support, resolve a payment query, protect against misuse or meet a legal duty. Older records are removed or separated when those needs end.

Change requests

To request a correction, access copy or clarification, contact us through the account support route and state the Privacy Policy request. We may ask for account details to prevent changes to the wrong record.

Browse Privacy Policy Questions Before Joining

These answers address the searches we hear most often about the 34R Privacy Policy. They cover account records, local wallets, cookies, device access and the practical route for asking us to change or explain personal data.

It covers data connected with opening an account, phone verification, sign-in, wallet references, device access, cookies and support requests. It also explains retention, security steps and how to ask about your records.

We may handle contact and verification details, account activity, payment references, device or connection signals and support messages. The exact data depends on the account step or wallet action you choose.

Yes. The Privacy Policy covers references linked with DANA, OVO, GoPay, QRIS, bank transfer and virtual account actions. We use those references to connect an account event without requesting your wallet login.

Use the support route shown beside the account and cashier areas, then state that you want a Privacy Policy data request. Include your account contact detail so we can verify which record to address.

You can request a correction through account support. Tell us which detail is wrong and provide the matching account contact. We may complete an account check before changing a phone verification or identity record.

Cookies can preserve your sign-in session and page continuity when you move from a mobile login to the lobby. Browser controls let you manage them, but refusing cookies may interrupt account access.

The policy is written for access from Indonesia, including locations such as Yogyakarta, where local law permits. Eligibility and available account actions depend on local law and the details shown during access.