Reference

Privacy Policy For Your hose88 Account

Our Privacy Policy explains what we collect when you open a hose88 account, sign in from a phone or desktop, use DANA, OVO, GoPay or QRIS, and contact…

Account clarityWallet recordsCookie choicesContact access
hose88 Privacy Policy For Your hose88 Account
CONTACT YOUR WAY

Ask About Privacy Policy Changes

You can contact us when a Privacy Policy question concerns your account, a wallet reference or a device used for sign-in. Start with the account support path and include the email or phone detail connected to your profile, plus the subject of your request. Do not send a password, one-time code or full payment credential. For a Bandung account holder checking a QRIS receipt, this gives our team enough context to locate the right status without copying unnecessary personal data.

Team online

Account request

Use the signed-in account support path to ask what personal data is linked to your profile. We may ask you to complete a phone check before discussing account details, so the request is handled with the correct account holder.

Wallet question

If DANA, OVO or GoPay status appears beside a cashier event, send the transaction reference and date through support. We use the smallest useful set of details to check the record and avoid requesting your wallet password.

Correction path

Ask support to correct a name, contact detail or account record that is no longer accurate. Include the old and new value where safe, and we will explain any identity check needed before changing the profile.

HANDLING DETAILS

What We Keep And How We Protect It

Privacy Policy controls are connected to ordinary account operations: phone verification, login security, cashier status and support follow-up.

Account data

We may hold your name, contact route, verification result and account activity so we can provide access and respond to a support request. We do not need your wallet password to check a DANA, OVO, GoPay or QRIS reference.

Device signals

A phone or desktop can send session, browser and security signals when you sign in. These details help us spot an unusual access pattern and keep a support conversation connected to the right account.

Cookies

Cookies may remember a session or preserve a setting between pages. You can manage cookie controls in your browser, although blocking some cookies may interrupt sign-in, account checks or the path to the lobby.

Account security

Phone verification can be required before account access or a sensitive change. Never share a password or one-time code in a support message; our checks are designed to confirm the account without asking for those secrets.

Retention

We keep records for the period needed for account operation, payment matching, security review and legal duties. When a record is no longer needed for those purposes, our handling follows the retention process that applies to that record.

Your request

You can ask what data is linked to your profile, seek a correction or ask about deletion and processing. Contact us through account support with a clear subject; we may verify your identity before releasing or changing data.

Privacy Policy Answers For hose88

These Privacy Policy answers cover the account and payment situations you are most likely to meet on hose88. They explain access, records, cookies and contact steps without asking you to disclose more than needed. If your question concerns eligibility, access depends on local law; use the account support path for a case-specific response.

It covers account and contact details, phone verification, login and device signals, cookies, wallet references, payment status and support messages. It also explains why we use those records, how retention is considered and how you can request access or a correction.

Your phone detail can support account creation, verification and sign-in protection. Before discussing sensitive account data or changing a profile, we may ask for a verification step. We use the contact detail for account operations and support rather than requesting your wallet password.

No wallet password or one-time code should be sent to support. The policy allows us to handle a payment reference, status and related account record for DANA, OVO, GoPay or QRIS, so a cashier question can be checked without copying your private wallet credential.

Use the signed-in account support path and state which profile detail needs correction. Include the relevant email or phone route and the accurate replacement where safe. We may complete an identity check before changing the record, then explain the next step for your request.

You may contact support to ask whether deletion is available for a particular record. Some account, payment, security or legal records may need to remain for a defined purpose. We will identify the relevant limitation and explain what can happen to the request.

Cookies can keep a session active, remember a setting or help recognise a repeated login pattern. Browser controls let you manage them, but blocking required cookies may affect phone verification, sign-in or the route from your account to the lobby.

Where local law permits, contact us through account support with a request to access, correct or ask about processing of your personal data. Give a clear subject and avoid passwords or one-time codes. We may verify the account before providing a response.