Reference

Privacy Policy For Your Account

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

Account clarityWallet data contextCookie choicesAccess depends on local law
ziatogel 133 Privacy Policy For Your Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support route helps when you want to understand a Privacy Policy record rather than guess what a status means. We can connect your question to the account step, a wallet reference or a cookie setting. Keep the phone number linked to your account available, but do not send a password or full payment credentials. Our support path sits close to login and cashier status so your privacy request can be matched carefully.

Team online

Account data request

Ask us which account details are associated with your phone verification step. We can explain the request path and help you identify an inaccurate name, number or account record without asking you to disclose your password.

Wallet reference check

If a DANA, OVO, GoPay or QRIS reference appears in a Privacy Policy question, share only the limited receipt detail we request. We use that reference to locate the relevant status without seeking your wallet PIN.

Cookie and access help

Tell us if a mobile browser keeps an old session or cookie setting after you sign out. We can explain the clearing path for your device and clarify which preference affects account access where local law permits.

DATA HANDLING DETAIL

What Your Privacy Choices Cover

We keep this Privacy Policy tied to actions you can recognise: opening an account, using a phone check, returning on mobile and asking about a wallet record.

Account records

When you open an account, we record the details needed to create and maintain that account. A clear phone verification step helps us connect access requests to the right record, reducing the chance that another person receives account data.

Payment references

We may retain a payment reference, amount status and selected rail such as QRIS or bank transfer so we can answer a receipt question. We do not ask for your wallet PIN, card password or full banking credentials.

Mobile device signals

Your mobile browser may send device, browser and session details that help us identify repeated sign-in patterns or an interrupted session. These signals support account security; they are not a request for contacts, photos or unrelated files.

Cookies and settings

Cookies can keep a language choice, session state or policy acknowledgement available during your visit. You can manage browser cookies through your device settings, although clearing them may require you to repeat the phone verification or sign-in step.

Retention periods

We retain account and support records for as long as needed for the stated service purpose, security checks or duties that apply where local law permits. When a record no longer has a valid purpose, our process is to remove or restrict it.

Changes and questions

For a copy, correction, deletion question or explanation of use, contact the support path linked to your account area. Include the request type and phone number, but exclude passwords and wallet PINs so we can review the matter safely.

Privacy Policy Answers Before Access

These Privacy Policy answers cover the searches we hear before an account is opened or a mobile session is resumed. They explain the data behind phone verification, wallet references, cookies and access requests for Indonesian accounts. If your situation is not listed, use the support path and describe the specific record or setting you want us to check.

It covers account details, phone verification, device and browser signals, cookies, payment references and support records connected with your use of ziatogel 133. It also explains your options to ask about access, correction, retention and deletion where local law permits.

Phone verification connects an account access request to the correct account record and helps us detect unusual sign-in activity. We use the phone detail for that account purpose; you should never send us your password, wallet PIN or full banking credentials.

Yes. The Privacy Policy covers payment references and status details associated with DANA, OVO, GoPay and QRIS. We use limited transaction information to match a receipt or status question, while your wallet PIN remains with the relevant payment provider.

Use the support path linked to your account and state that you want a data correction. Include the phone number connected to the account and describe the inaccurate field. Do not attach a password or wallet PIN; we will explain the next verification step.

Cookies can retain session settings and a policy acknowledgement in your mobile browser. Clearing them may sign you out or require another phone verification step. You can manage cookies in browser settings, then contact support if an old session still appears.

Yes. Send a data access question through the account support path and identify the phone number connected with your account. We will explain the records held, their purpose and any limits that apply where local law permits before responding.

Account access and eligibility depends on local law. Our Privacy Policy does not change those local requirements. If you are unsure whether access applies in your area, contact support before submitting personal details or payment information through the account path.