Reference

hohotogel Privacy Policy for Your Account Data

DANA, OVO, GoPay and QRIS details stay tied to the account steps you choose, while our Privacy Policy explains what we collect, why we use it and how…

Account dataWallet detailsCookie choicesPhone verification
hohotogel hohotogel Privacy Policy for Your Account Data
HELP WHEN NEEDED

Where to Ask About Privacy Policy

A clear contact route matters when you want to understand a record or correct an account detail.

Privacy request Use the support link beside account access to ask what personal details we hold…
Account correction If your phone number, email or verification detail needs changing, tell us which field…
Payment record query For a QRIS, bank transfer or virtual account reference, send the date and transaction…
ACCOUNT DATA PRACTICE

How hohotogel Handles Stored Account Details

We separate account access records from the payment references needed to trace a cashier event, and we limit internal handling to the purpose described in this Privacy Policy.

Collection purpose

We collect account fields, phone-verification results, device signals and payment references for stated purposes such as access control, transaction matching, security checks and responding to your privacy request.

Cookie control

Cookies can keep a mobile-browser session connected and help recognise security events. You can clear or restrict them through browser settings, but sign-in may require another account check afterward.

Account security

Phone verification is required before account access, and unusual sign-in signals may trigger an additional check. We do not need your wallet passcode to match DANA, OVO, GoPay or QRIS records.

Retention period

We retain records only while they support account operation, legal duties, dispute handling or security review. When the applicable period ends, records are deleted or changed so they no longer identify you.

Change request

You can ask us to correct incomplete or inaccurate account details through the support route beside login. We may verify account ownership before changing phone, email or identity-linked fields.

Policy access

The Privacy Policy remains available from the policy link near account access, so you can check the wording before opening an account or connecting a local wallet where local law permits.

Privacy Policy Questions About Your Account

These Privacy Policy answers address the points most often considered before account creation: collected data, wallet references, cookies, corrections, deletion requests and access checks. If your situation is specific, use the support route beside login and give us only the details needed to locate your account.

It covers account details, phone verification, device and browser signals, cookies, support messages, payment references and retention. It also explains your choices and how to request correction or deletion where local law permits.

No. Our Privacy Policy describes using transaction references, status details and account links for matching. We do not ask for or need your DANA, OVO, GoPay or QRIS wallet passcode.

Phone verification helps confirm account ownership before access and supports security checks when sign-in signals change. The result is retained according to the Privacy Policy and applicable retention needs.

Yes. Contact the support route beside login, identify the field that needs correction and provide your account identifier. We may complete an ownership check before changing your phone, email or related record.

Cookies can maintain a mobile-browser session and help detect security events. You can restrict or clear them in browser settings, but doing so may sign you out or require phone verification again.

We keep payment references while needed for account operation, reconciliation, legal duties, disputes or security checks. After the applicable period, we delete or anonymise them under the Privacy Policy.

Send a deletion request through the support link beside the login panel. We will check account ownership and explain which records can be removed, subject to legal, security and transaction-retention requirements.