Reference

han555 Privacy Policy for Your Account

The han555 Privacy Policy explains how we collect, use and protect details connected with your account, device and wallet activity in Indonesia.

Account dataWallet recordsCookie choicesPolicy requests
han555 han555 Privacy Policy for Your Account
CONTACT THE TEAM

Privacy Policy Help Through Your Account

A clear contact route matters when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record. We ask you to contact us through the signed-in support path where possible, because that lets us connect the request with the correct account without asking you to send sensitive details in an open message. If you cannot access your account, use the available account contact route and include the email or phone detail connected with your access. We respond to policy questions about data, cookies, retention and correction.

Team online

Account contact

Use the support path connected to your han555 account for a Privacy Policy request. We can check your account identity, locate the relevant phone verification record and explain which data is held for account access.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference appears in your account, send its date and reference through support. We use those details to locate the transaction record without requesting your wallet password or private security code.

Access assistance

When login access stalls, tell us the device path you used, such as mobile browser or desktop browser, and the time of the attempt. We use that context to separate an access issue from a Privacy Policy request.

DATA HANDLING

Privacy Policy Details You Can Check

We keep the Privacy Policy practical by tying each data use to an account action you can recognise. Phone verification supports account access, cookie settings help remember selected preferences, and transaction references…

Data collection

We collect details you submit for an account, including contact data and phone verification status. We also create service records when you sign in, contact support or use a wallet route, so we can provide access and answer account questions.

Cookie controls

Cookies can support sign-in continuity, preference storage and basic page operation on your mobile or desktop browser. Your browser settings can limit cookies, although some account functions may then require another sign-in or may not retain your selected preferences.

Account security

We examine sign-in and device signals to help identify unusual account access. A new mobile browser, repeated verification attempt or changed access pattern may lead to an extra account check before we discuss private details.

Transaction records

A payment route can create a reference, amount and status record for reconciliation. This applies to DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests, while wallet passwords and private security codes should never be sent to support.

Retention requests

We retain account and transaction records for the period needed to operate the service, protect accounts or meet applicable obligations. Ask through support for the retention reason connected with a particular record, and we will explain what can be changed or removed.

Correction path

If your phone number, contact detail or account record is inaccurate, contact us from the signed-in support path. We may verify the request before changing it, so another person cannot alter the data attached to your account.

Privacy Policy Answers for han555

These Privacy Policy answers address the account and access questions you are most likely to ask before opening or continuing an account. We keep the wording tied to the actual paths used on han555, including phone verification, mobile browser access and local wallet records. If your situation is not covered, contact support with the smallest useful detail and we will identify the right request path. Eligibility and access depends on local law, so the result of a request can vary by location.

The han555 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages and transaction references. It explains why we use each category, how we protect account access, how long records may be retained and how you can request correction or clarification.

We use phone verification to connect your account with the contact detail supplied during access and to reduce unauthorised account changes. The verification status can also help support confirm that a request comes from the account holder before private account or wallet details are discussed.

Yes. The Privacy Policy covers transaction references and status records created when you select DANA, OVO, GoPay or QRIS. We use those records to match an account request with its payment state. Do not send wallet passwords, PINs or private security codes to us.

You can contact support through your signed-in account and ask what data is held or request a correction. Include the affected detail, such as a phone number or contact record, without sending unnecessary credentials. We may verify your identity before releasing or changing private account data.

On a mobile browser, cookies may keep sign-in preferences and selected settings available between pages. You can manage them through your browser controls. Limiting cookies may require another sign-in or prevent some preferences from being retained, while the policy still applies to account records created during access.

We keep records for the time needed to provide account access, trace wallet status, protect against unusual activity or meet applicable obligations. The period can differ by record type. Ask support about a specific account or transaction record, and we will explain the reason for its retention.

Where local law permits, you can ask support whether a particular account or data record can be removed. We first verify the request and check whether the record is still needed for account security, transaction reconciliation or an applicable legal obligation before explaining the available result.