Reference

maya4d Privacy Policy for Your Account

maya4d Privacy Policy explains how we handle the details you provide when opening an account, signing in from a mobile browser, and using DANA, OVO, GoPay or QRIS.

Account data clarityWallet record contextCookie choices
maya4d maya4d Privacy Policy for Your Account
CONTACT PATHS

Get Privacy Help Beside Account Support

A clear contact route helps when you want to ask what we hold, correct an account detail or question a wallet record.

Account privacy request Ask us to access, correct or explain personal details linked with your maya4d account.
Wallet record question For a DANA, OVO, GoPay or QRIS reference, send the visible transaction date and…
Sign-in data concern If a mobile login shows an unfamiliar device or account event, contact us from…
DATA PRACTICES

Six Privacy Controls We Keep Visible

Privacy is easier to manage when each data use has a practical reason. We separate account identity, wallet references, device activity and cookie signals so you can ask a precise question.

Account details

We use your submitted contact and verification details to create, secure and maintain account access. You can ask us to correct a spelling, phone detail or other personal field through the account support route.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us reconcile payment status. They are handled as transaction records, separate from your wallet password or private wallet credentials.

Device signals

When you move from mobile login to the lobby, we may process browser, device and security signals to recognise unusual access. These signals help protect the account rather than describe your personal interests.

Cookie settings

Cookies can remember a session and support page functions, including returning from the account screen to the lobby. Your browser settings can remove or restrict cookies, although some account actions may then need another sign-in.

Retention handling

We keep account, security and transaction records only as long as needed for the stated service, account protection or legal duties. When a record is no longer needed, our handling follows the applicable retention process.

Change requests

To request access, correction or deletion where available, contact us with your registered account detail and the specific record. We may ask for an account check before changing or disclosing personal data.

Privacy Policy Answers For Indonesia Accounts

These Privacy Policy answers address the practical questions you may have before opening an account or checking a wallet status. We keep the response tied to your account path, device behaviour and payment reference, with access handled where local law permits.

The maya4d Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies and transaction references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We collect the contact and verification details you submit, plus technical sign-in data needed for account security. We do not need your DANA, OVO, GoPay or QRIS wallet password to match a payment record.

Yes, you can send an access request through the account support route. Include the registered contact detail and specify the records you want checked; we verify the request before releasing account-specific data.

Contact us through the support path attached to your account and identify the field that needs correction. We may confirm your phone or email detail before changing the account record.

Yes. Cookies may keep a mobile browser session active and help the path from login to the lobby work correctly. You can restrict them in your browser, though another sign-in may be required.

We retain payment references only for the period needed for account support, security checks, transaction reconciliation or legal duties. The period can vary by record type and applicable local requirements.

You can request deletion through the account support route, and we will assess which records can be removed. Some security, account or transaction records may need to remain for legal or operational reasons.