Reference

Open Our Privacy Policy Before Your Account

Your account details, device path and wallet records are explained clearly in the himalaya4d Privacy Policy before you open an account.

Account dataWallet recordsCookie choicesContact path

Browse the lobby Read FAQ

Explore How Your Account Data Is Used

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

Our Privacy Policy explains the account details we collect when you create an account, confirm your phone number and sign in to the lobby. It also covers records linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, such as a payment reference or

1
status check, rather than the contents of your private wallet. We use these details to process account access, identify a transaction, answer a support request and protect the account from unusual sign-in activity. A mobile browser may provide device and session details needed to keep your
2
login active, while cookies help remember selected settings. We retain records only for the period needed for these purposes or where local law permits, and access to the service depends on local law. If you ask us to change or remove details, we will explain the
3
steps and any records we must keep.

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

CONTACT ROUTES

Switch To The Right Privacy Support Path

A clear contact route helps when your account record, cookie choice or wallet reference needs attention.

HANDLING DETAILS

Browse Our Data Handling Commitments

We keep the Privacy Policy practical by connecting each data use to an account action you can recognise.

Phone verification

Before account access, we use the phone-verification step to connect the sign-in request with the account record. Keep your number current through the account path, and contact us if the displayed verification detail is not yours.

Mobile sessions

When you move from login to a lobby on a mobile browser, session details may be stored so the account remains connected. Clearing browser data can sign you out and remove saved privacy choices from that device.

Cookie controls

Cookies can remember a session and selected settings, but they do not replace your account password. You can adjust browser cookie controls, although disabling them may require you to repeat the login and privacy choice steps.

Account security

We use sign-in and device signals to identify unusual access and protect account records. We will not ask you to send a password, wallet PIN or full payment credential through a support message.

Retention period

We keep account, support and payment-reference records for the time needed to provide the requested service, resolve a query or meet a legal requirement. The exact retention need can differ by record type and request.

Change requests

You can ask us to correct account details, explain a stored record or request removal where permitted. We may verify ownership through the registered phone step before changing data linked to your himalaya4d account.

Check Privacy Policy Answers Before Signing In

These Privacy Policy answers cover the questions we expect before an account is opened or a wallet is connected. Each answer points back to a practical step, from checking cookies on your device to requesting a correction through account support. If your question concerns local eligibility, access depends on local law and the policy wording for your region.

It covers account details, phone verification, mobile sessions, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security checks and how to request access or correction where local law permits.

We use your phone number for the account access and verification step, helping connect a sign-in request with the correct record. It can also help support locate your account. Do not send your password, wallet PIN or full payment credential in a message.

Yes. The Privacy Policy covers payment references and displayed status connected with DANA, QRIS, OVO and GoPay, plus bank transfer and virtual account records. We ask for a date or reference when checking a receipt, not your wallet PIN or private wallet balance.

Cookies may keep a sign-in session active and remember selected settings on your mobile browser. They do not replace your account password. You can change cookie controls in the browser, though clearing or blocking them may sign you out or reset saved choices.

Use the account support path and describe the detail that needs correction, such as a phone record or displayed account name. We may verify ownership through the registered phone step before making a change, and we will explain any record that must remain.

We retain each record for the time needed to provide account support, check a payment reference, protect access or meet a legal requirement. Retention can differ between a login record, support message and transaction reference, so contact us for a record-specific explanation.

You can request removal of eligible account details through support. We first verify that you control the account, then check whether a record must remain for security, dispute handling or legal reasons. Access to any service still depends on local law and regional eligibility.

Open Our Privacy Policy Before Your Account

Switch To The Right Privacy Support Path

Browse Our Data Handling Commitments

Phone verification

Mobile sessions

Cookie controls

Account security

Retention period

Change requests

Check Privacy Policy Answers Before Signing In

01 What does the himalaya4d Privacy Policy cover?

02 Why does himalaya4d need my phone number?

03 Does the Privacy Policy cover DANA and QRIS details?

04 What cookies does himalaya4d use on mobile?

05 How can I request a correction to my account data?

06 How long does himalaya4d keep my personal details?

07 Can I ask for deletion under the Privacy Policy?

Related Pages