Reference

Privacy Policy For Your hobicuan Account

Our Privacy Policy explains what we collect when you open a hobicuan account, sign in from a phone or desktop, browse the lobby, or use DANA, OVO, GoPay…

Account dataCookie choicesWallet recordsContact route
hobicuan Privacy Policy For Your hobicuan Account
HELP WITH PRIVACY

Three Ways To Ask About Your Data

A clear support route helps when you want to understand a data record rather than change a wallet action.

Account support path Use the support route attached to your account when you need help locating a phone verification record or understanding why a sign-in detail appears in our Privacy Policy process. Include the account phone number and request type so we can separate your case from another account.
Wallet receipt check For a DANA, OVO, GoPay or QRIS question, provide the payment reference, date and status shown in your account. We use that narrow information to trace the wallet event and explain which record our Privacy Policy permits us to retain.
Policy request Ask us to explain, correct or review a personal-data entry through the same account support path. We may ask for an account check before responding, because a privacy response must reach the person connected with the hobicuan account.
DATA HANDLING

Six Practical Privacy Commitments

Privacy is easier to understand when each control has a visible account purpose. We separate login protection from payment references, keep cookie activity tied to the device path you choose, and use…

Account details

We collect details needed to create and maintain your account, such as your phone number and verification state. We use them to identify the account, support sign-in questions and apply the Privacy Policy to the correct person rather than combining separate account records.

Device records

Your browser or phone can provide technical signals such as session details, language settings and connection data. We use these signals to keep a login session working, detect unusual access and investigate a support request tied to a particular device path.

Cookie choices

Cookies and similar storage can remember a session or help us understand which account page was opened. You can manage browser storage through your device settings; removing it may require another login and can change how the Privacy Policy request path appears.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount status and time record connected to your account action. Bank transfer and virtual account references follow the same matching approach, allowing us to check a receipt without storing your wallet password.

Account security

We limit privacy discussions to the account holder and may request phone verification before releasing or correcting a record. Keep your password private and sign out on shared devices; those steps reduce the chance that another person can use your session to request account data.

Retention requests

We retain records only for the account, security, support or local-law purpose described in the Privacy Policy. You can ask which category applies to a record, request a correction, or ask whether deletion is available after required account and transaction obligations are considered.

Privacy Policy Answers For hobicuan

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening an account or sending a support request. They explain the practical route for Indonesian access, including phone verification, mobile sessions and local payment references. Where a request depends on jurisdiction or eligibility, the answer remains subject to local law and the account checks needed to protect your information.

It covers account details, phone verification, device and session records, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains why we use each category, how long records may remain and how you can ask about a specific entry.

We use your phone number to create or identify your account, complete the account access step and connect a privacy request to the correct person. A verification status may also appear in support records. We do not ask you to place your password inside a Privacy Policy request.

Yes. The Privacy Policy covers the payment reference, status and timing needed to match a DANA or QRIS action with your account. OVO and GoPay references are treated in the same way. We use those details for status checks and support, not as wallet login credentials.

Cookies or similar browser storage can keep a session active and help connect the page you opened with the right account path. On a phone, clearing browser data may sign you out or remove a saved preference. Your browser settings provide the practical way to manage that storage.

Yes. Send a correction request through the account support path and identify the record, such as a phone detail, device entry or wallet receipt reference. We may ask for phone verification before changing it. We will explain any limit that applies under local law or transaction retention duties.

Use the policy request route and include your account phone number, the data category and the relevant date or receipt reference. We can explain whether it relates to login, cookies, support, security or payment matching. Do not send your password, wallet PIN or full wallet credentials.

Yes. Account access and eligibility depend on local law and apply where local law permits. Our Privacy Policy still explains how information is handled when you reach an account page from Indonesia, including Semarang or Makassar. Contact support if you need the policy applied to your specific location or account status.