Reference

Privacy Policy for djarumtoto Accounts

Your account details, phone verification record and wallet activity are handled under the djarumtoto Privacy Policy, so you can understand what we collect before opening an account.

Clear data purposesWallet activity recordsMobile browser accessPolicy request path
djarumtoto Privacy Policy for djarumtoto Accounts
HELP ROUTES

Privacy Questions Near Your Cashier Path

A clear support route helps when you need to ask why a phone check, wallet reference or cookie setting appears in your account records. From Yogyakarta or elsewhere in Indonesia, open the account support path shown near the cashier area and state the exact issue, date and account phone number. We use those details to locate the relevant record without asking you to post private credentials in a message.

Team online

Account data request

Ask the account support route for a copy, correction or explanation of personal data connected with your djarumtoto account, where local law permits.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, share its date and status through support so we can trace the account record.

Access concern

For an unexpected sign-in or phone verification issue, use the account help path beside the cashier area and avoid sending your password or wallet PIN.

DATA PRACTICE

How We Handle Account Data

We keep this policy practical by linking each data category to an account action you recognise: phone verification, mobile sign-in, wallet matching or support contact.

Account details

We use the phone number and verification status you provide to identify your account and help prevent an unrelated person from changing its privacy settings.

Cookies and sessions

Cookies and session records can keep your mobile browser connected after sign-in. You can manage browser cookie controls, although changing them may affect account access.

Wallet references

Payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account help us match a status record without treating that reference as your wallet password.

Security events

Sign-in time, device signals and verification events may be retained to investigate unusual access, protect your account and respond to a specific security question.

Retention choices

We retain records only as needed for the stated account, security or legal purpose, with the period depending on the record and applicable requirements where local law permits.

Change requests

To request access, correction or removal of eligible data, contact the support route with your account phone number and the precise record you want changed.

Privacy Policy Questions for djarumtoto

These Privacy Policy answers address the account and wallet questions you may search before opening access. We keep the wording specific to djarumtoto records, mobile sessions and Indonesia payment references, while any eligibility or access decision depends on local law.

It covers account details, phone verification, mobile session data, cookies, security events, support messages and payment references linked to DANA, OVO, GoPay, QRIS or bank activity.

We use phone verification to connect you with the correct account and help prevent unauthorised changes. The account path may require this step where local law permits.

Yes. The policy explains that DANA, OVO, GoPay and QRIS references may be retained to match a wallet status or account transaction record, without requesting your wallet PIN.

Use the support route beside the account or cashier area, provide your account phone number and identify the records requested. We handle eligible requests where local law permits.

Yes, send a correction request through account support and describe the inaccurate field, such as a phone detail or account preference. We may need verification before making a change.

Retention depends on the record, its security or account purpose and applicable requirements. The Privacy Policy explains the category involved, while a specific request can ask for clarification.

Contact the account support path with the sign-in date, device detail and phone number linked to your account. Do not send your password or wallet PIN in the request.