Reference

234togel Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and contact support about wallet status.

Clear data purposesWallet record detailsDirect request path
234togel 234togel Privacy Policy for Your Account
REQUEST SUPPORT

Contact Us About Privacy Policy

A privacy request should include enough detail for us to locate the right account without exposing another person’s records. Use the support link inside your account when you need a copy, correction or explanation, and mention whether the matter concerns login data, a DANA receipt or a QRIS reference. We will use the details you provide only to assess the request and respond through the available account contact route.

Team online

Account request

Open the account support path and ask to access, correct or clarify personal data held under your account. Include your registered phone number so we can match the request.

Wallet question

For DANA, OVO, GoPay or QRIS records, attach the payment reference and date rather than a wallet password. This helps us check status while limiting sensitive details.

Login concern

If a device or sign-in record looks unfamiliar, contact us through the account support route and describe the device path. We can review the relevant access record with you.

DATA CONTROL

Account Data Beside Wallet Checks

We keep this Privacy Policy practical by linking each data use to an account action you can recognise.

Account details

We may hold your phone number, verification result, login identifiers and selected account settings. These details help us connect a request to the correct account before discussing private records.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be stored with its status and timestamp. We use it to reconcile account activity and answer receipt questions.

Cookie choices

Cookies and similar session tools can remember sign-in continuity and basic preferences. Your browser settings can remove them, although some account steps may then need to be repeated.

Device security

Browser, operating system, IP address and session details may support checks when an account signs in from an unfamiliar device. We use these signals to investigate access concerns.

Retention period

We retain account, payment and security records only as long as needed for support, dispute checks, security work and applicable legal duties. A request can ask us to explain the period.

Change requests

Send a correction, access or deletion question through the account support path. We may ask for phone verification before changing records, helping prevent an unauthorised request.

Privacy Policy Questions for Your Account

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet record is queried. Each answer points to a practical account step, from checking cookies on a mobile browser to requesting a correction through support. If your situation is not listed, contact us with the smallest useful set of details.

It covers account details, phone verification, cookies, device and session records, payment references, support messages, retention and requests to access or correct information connected with your account.

No. We use transaction references, status, amount and timing to match DANA activity with your account. Your wallet password should remain with DANA and should not be sent to support.

We may record the QRIS reference, amount, timestamp and result so we can match a receipt, investigate a pending status or answer an account query without needing your wallet credentials.

Yes. Use the account support path and ask for an access request. Include your registered phone number, then complete any identity check needed before we discuss or release account records.

Send a correction request through support and identify the field that needs changing. We may confirm your phone number or account step first, then assess the requested amendment.

Device, browser, IP and session details help us examine unfamiliar sign-ins and protect account access. They may also help support connect a login concern to the correct session.

Retention depends on the record and the reason it is needed, such as support, payment matching, security checks or legal duties. Ask through support for a record-specific explanation.