Reference

Privacy Policy for r34xyz Accounts

The r34xyz Privacy Policy explains what account, device and payment details we use when you open an account or access the lobby.

Account dataWallet detailsCookie choicesAccess requests
r34xyz Privacy Policy for r34xyz Accounts
POLICY HELP DESK

Get Clear Answers About Your Data

A direct support path helps when a Privacy Policy question concerns a sign-in, wallet reference or account record. Start from the account help route and include the email or phone detail attached to your account, without sending a password or one-time code. We use the details you provide only to identify the request and return a useful answer.

Team online

Account access

If you cannot complete phone verification, tell us which account step stopped and the device path you used. We can explain what account data is needed to check access while keeping your password and one-time code private.

Wallet status

For a DANA, OVO, GoPay or QRIS question, include the payment reference and approximate time shown in your account. Do not send wallet passwords or card credentials; we use the reference to locate the related record.

Privacy request

To ask for access, correction or deletion of eligible personal data, state the request clearly through account support. We may ask for account details that help confirm identity before changing or disclosing a record.

DATA CONTROL ROOM

What We Do With Account Records

Privacy choices work better when each data use has a clear reason. We connect account records to sign-in protection, payment matching and support handling rather than treating every detail as permanent.

Account details

We use the registration details you provide to create your account, send account-related messages and identify the correct record when you ask about Privacy Policy rights. Phone verification can be required before account access or a data request is completed.

Payment references

A wallet name such as DANA or GoPay, a QRIS reference, or a bank transfer record can help us match a payment status to your account. We do not need your wallet password to investigate a reference.

Cookies

Cookies can keep a sign-in session connected to the page, remember a selected setting and support security checks. You can manage browser cookie controls, though turning needed cookies off may interrupt account access or payment status display.

Device signals

We may receive browser, device and connection signals used to detect unusual sign-in activity and keep sessions safer. The same checks can appear when you move from a mobile browser to desktop and request account access.

Retention

We retain records only for the period needed for account operation, payment matching, security checks, dispute handling and legal duties. When a record is no longer needed for those purposes, our process addresses deletion or secure restriction.

Your request

You can ask what personal data we hold, request a correction, or ask whether deletion is available through account support. We first confirm the account context, explain any legal or security reason for a limit, then record the outcome.

Privacy Policy Questions About r34xyz

These Privacy Policy answers address the account and payment questions Indonesian customers commonly raise before opening an account. Each answer stays focused on personal data, access, cookies and requests rather than general lobby features. If your situation is not covered, use the policy support path with the relevant account or payment reference.

The r34xyz Privacy Policy covers data connected with registration, phone verification, sign-in, device activity, cookies, support requests and payment references. That includes records associated with DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps when they connect to your account.

We use your phone number to create and identify the account, support phone verification and help protect sign-in access. If you ask us to change or disclose account data, the phone detail can also help confirm that the request concerns your account.

Yes. The Privacy Policy covers payment references and status details that connect DANA, OVO, GoPay or QRIS activity with your account. We use those references to match a payment question, while you should never send a wallet password or one-time code.

Use the account support route and state that you want access to your personal data under the Privacy Policy. Include the account phone or email detail, but exclude passwords and codes. We may confirm identity before explaining which records can be provided.

You can request a correction when your account record is inaccurate or incomplete. Send the specific field and the corrected detail through account support. We may verify the request first, then update the record or explain why a record must remain unchanged.

Cookies can maintain a sign-in session, remember a setting and support security checks on your browser. Your browser controls can restrict them, but needed cookies may be required for account access or for a DANA, OVO, GoPay or QRIS status page to work.

You can ask whether deletion is available for a specific account record through the Privacy Policy support route. We assess the request against account security, payment matching, dispute handling and legal duties, then explain what can be deleted, restricted or retained.