Reference

ziatogel login Privacy Policy For Your Account

ziatogel login Privacy Policy explains what we collect when you open an account, check your phone, enter the lobby and use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet record detailCookie choicesAccount contact path
ziatogel login ziatogel login Privacy Policy For Your Account
POLICY HELP ROUTES

Browse Support Paths For Privacy Questions

A clear contact route helps when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record.

Account contact form Use the contact form after signing in when you want to ask about your Privacy Policy rights, correct a phone detail or request a copy of the account data connected to your profile.
Cashier data question If a DANA, OVO, GoPay or QRIS receipt appears incorrectly, tell us the wallet name, date and account step. We can trace the status without asking you to share a password or security code.
Access issue route When a privacy request is blocked by a sign-in problem, start with the account help route beside the cashier area. We use the available account checks to confirm your request before discussing protected details.
DATA HANDLING PRACTICE

Explore How We Protect Policy Choices

We keep Privacy Policy choices tied to practical account controls rather than vague statements. Our process separates necessary security records from optional cookie activity, limits internal access to account details and checks…

Account details

We use details such as your contact number, verification state and sign-in history to open, secure and maintain your account. We do not ask you to place a password or one-time security code inside a privacy request.

Wallet records

Payment references help us match a requested account action with DANA, OVO, GoPay, QRIS, bank transfer or virtual account status. We retain the minimum record needed for reconciliation, security and a clear response.

Cookies

Cookies can keep a sign-in session working, remember a language or device setting and help us understand a page error. You can manage browser cookie controls, though some account functions may then need another sign-in.

Security checks

Before we discuss protected account data or accept a correction request, we may ask you to complete the account step linked to phone verification. This helps prevent another person from changing your privacy choices.

Retention period

We keep account, security and payment-status records for as long as they serve account administration, dispute handling or a legal requirement. When a record is no longer needed, our process removes or de-identifies it.

Change requests

You can ask us to correct eligible details, explain a processing purpose or remove data that no longer needs to remain. Send the request through the signed-in contact route so we can verify ownership first.

Check Common Privacy Policy Questions

These Privacy Policy answers cover the questions we expect you to ask before opening an account or connecting a local wallet. We explain the practical path for access, correction, cookies, retention and contact so you can decide what to share. Where a request involves legal eligibility or account access, the outcome depends on local law and the checks attached to your profile.

It covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment-status references. It also explains why we use these details, how we protect them, when we retain them and how you can ask about eligible access or correction.

Phone verification helps us connect an account request to the person making it and helps protect changes to profile or wallet records. We may use that check before discussing protected data, restoring access or processing a Privacy Policy request.

Yes. The policy explains that DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can be recorded when needed to match an account action or receipt status. We do not need your password or security code for that record.

You can send a correction request through the signed-in account contact form. Tell us which detail is wrong and why. We may complete a phone or account check first, then update eligible data or explain why a record must remain.

Cookies may keep your sign-in session active, remember a device setting or help us identify a page problem. You can change cookie controls in your phone or computer browser. Removing certain cookies may require you to sign in again.

We retain each category only while it supports account administration, security, payment reconciliation, dispute handling or a legal requirement. When the purpose ends, our process removes or de-identifies the record, subject to any remaining legal need.

Use the signed-in account contact route and describe your request without including a password or security code. For a wallet record, name the rail such as QRIS or DANA and the relevant date. Access depends on local law and account verification.