Reference

Open ht66 Privacy Policy Clearly

Our ht66 Privacy Policy explains what we collect when you create an account, verify your phone, open the lobby on mobile, or use DANA and QRIS.

Account dataWallet recordsDevice choicesContact rights

Browse Our Lobby Read FAQ

Browse Privacy Rules For Your Account

ht66 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Your Privacy Policy details the records needed to operate account access, including your contact details, phone verification result, login activity, device signals, wallet status and support messages. Payment references can appear when you choose DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, while the

1
policy explains why those references help us match a request. We use this information for account administration, payment checks, fraud detection and required service records. Access or eligibility depends on local law, and the applicable wording is shown with your account flow. If you use the
2
mobile browser in Denpasar or elsewhere in Indonesia, device and session data may be recorded to keep the policy controls connected to your sign-in.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Check Privacy Help Beside Account Support

A clear contact route matters when you want to question a record, correct a phone detail, or understand a wallet reference.

Account request Use the account support path to ask what personal details are linked to your phone verification, sign-in record or saved contact information. We may ask for account details to confirm the request belongs to you.

Wallet record For a DANA, OVO, GoPay or QRIS reference, include the date, amount reference shown in your account and the payment rail used. Do not send wallet passwords, card secrets or one-time codes.

Policy question If a section of this Privacy Policy is unclear, contact us through the displayed support route and name the section. We can explain collection, retention, cookies or correction steps without asking for unnecessary data.

DATA PRACTICES

Explore How We Handle Your Records

We keep the policy practical by linking each data category to an account action you can recognise.

Account details

We may hold the name, contact details and phone verification status you provide during account creation. These records help us identify your account and respond when you request access, correction or deletion where applicable.

Device sessions

When you sign in from a phone or desktop browser, we may record device type, session time and basic connection signals. This helps us identify unusual access and keep your account journey connected across screens.

Cookie choices

Cookies and similar browser storage can remember session settings and support account continuity. Your browser controls can remove or block them, although some sign-in or policy preference functions may then need to be repeated.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create reference records. We use those references to match account requests and status checks, not to request your private wallet password.

Retention periods

We keep records for as long as needed for the purpose described, account administration, dispute handling or applicable legal duties. When a record is no longer needed, our handling process removes or separates it.

Change requests

You can ask us to access, correct or clarify personal data through the support route shown in your account. Include the account contact and requested action; we may verify identity before making a change.

Browse Privacy Policy Answers Before Opening

These Privacy Policy answers cover the account, device and wallet questions we expect you to ask before opening an account. They explain the practical route for requests and the limits around access, verification and local rules, while the full policy remains the controlling text for your ht66 account.

It covers account details, phone verification, device sessions, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect your account to the contact detail you provide and supports account recovery or access checks. We use it for those account purposes and may verify a request before changing records.

Yes. The policy covers basic device and session signals when you use a mobile browser, including sign-in timing and device type, so we can connect your session and investigate unusual access.

Use the support route displayed in your account and ask for data access. Include your account contact and describe the records you need; we may confirm identity before responding to the request.

Yes. Send a correction request through the account support path, identify the inaccurate field and provide the replacement detail. We may request account verification before updating contact or profile records.

We retain payment references needed to match account activity and status checks. The Privacy Policy does not require you to send a wallet password or one-time code through support.

Yes. Access or eligibility depends on local law. The Privacy Policy applies to the account flow shown for your region, and you should check the displayed terms before creating or using an account.

Open ht66 Privacy Policy Clearly

Check Privacy Help Beside Account Support

Explore How We Handle Your Records

Account details

Device sessions

Cookie choices

Payment references

Retention periods

Change requests

Browse Privacy Policy Answers Before Opening

01 What does the ht66 Privacy Policy cover?

02 Why does ht66 need phone verification data?

03 Does the Privacy Policy cover mobile browser data?

04 How can I request a copy of my ht66 data?

05 Can I ask ht66 to correct my personal data?

06 How are DANA and QRIS records handled under this policy?

07 Does access to ht66 depend on local law?

Related Pages