Reference

hay4d Privacy Policy For Your Account

hay4d Privacy Policy explains how we collect, use and protect details connected with your account, device and wallet activity.

Account dataWallet recordsCookie choicesContact requests
hay4d hay4d Privacy Policy For Your Account
CONTACT OUR TEAM

Reach Support About Privacy Policy

A clear contact route helps when your Privacy Policy question concerns a login record, wallet reference or device session.

Account request Use the account support path when you want to ask which personal details we…
Wallet reference If your question relates to DANA, OVO, GoPay, QRIS, bank transfer or a virtual…
Device session For a mobile browser or desktop session that you do not recognise, contact us…
HOW WE HANDLE DATA

Explore hay4d Privacy Policy Controls

The Privacy Policy is applied to the account journey rather than treated as a separate page with vague promises.

Data collection

We collect details that support account access, phone verification, wallet status and security checks.

Cookie choices

Cookies and similar browser storage help keep a signed-in session connected to the page you opened.

Account security

We use phone verification and session checks to reduce the chance of an unauthorised person receiving account details.

Payment records

A DANA, OVO, GoPay or QRIS request can create a reference showing the chosen rail, amount status and time.

Retention period

We keep personal data while it is needed for account operation, security checks, payment reconciliation, disputes or legal duties.

Change request

You can ask us to correct, explain, restrict or remove eligible personal data through support.

Browse Privacy Policy Answers

These Privacy Policy answers address the searches we expect before you open an account or connect a local wallet. They explain what hay4d records, why an account step may be requested and how to contact us without exposing private credentials. If your situation is not covered, send a focused request through the support route.

The hay4d Privacy Policy covers account details, phone verification, device sessions, cookies, payment references and support requests. It explains why we use each category, how long records may remain and how you can ask for access, correction, restriction or removal where local law permits.

Phone verification helps us connect an account request to the person controlling the account and reduces mistaken disclosure. We may ask you to complete that step before discussing profile data or changing contact details. Do not send a verification code inside a support message.

Yes. The Privacy Policy covers references created when you use DANA, OVO, GoPay or QRIS, including the selected rail, request time and status. It also covers bank transfer and virtual account references used to reconcile an account request or resolve a payment question.

The policy describes cookies and browser storage used to maintain a session, remember selected settings and support security checks. Clearing browser data can sign you out or remove a stored choice. You can manage cookies through your mobile or desktop browser settings.

Contact support from the account area when possible and state that you want a copy or explanation of your account data. Include the account phone or email and the relevant date. We verify ownership before responding, and the available action depends on local law.

You can request a correction, restriction or removal of eligible data through our support path. Tell us which record is wrong or no longer needed. Some payment, security or dispute records may need to remain for a stated operational or legal reason.

Yes. The Privacy Policy applies when you access the account and lobby through a mobile browser or desktop browser. Device and session details can help protect your profile. If you clear storage, change devices or notice an unfamiliar session, contact us for an account check.