Reference

maya4d Privacy Policy, Made Clear

Your account details, phone verification record and wallet references have a clear place in the maya4d Privacy Policy.

Account dataWallet recordsCookie choicesPrivacy requests
maya4d maya4d Privacy Policy, Made Clear
PRIVACY HELP

Get Privacy Help Through Your Account

A clear request path helps when you need to ask about a record, cookie choice or payment reference.

Account data request Use the account help route to ask what personal details are linked to your…
Wallet record check For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the payment…
Cookie choice request Tell us if you want help with browser cookies or saved sign-in settings.
DATA CONTROL

Keep Your Account Records Understandable

Our privacy handling follows the actual steps you take: account creation, phone verification, sign-in, wallet selection and support contact.

Account creation

When you open an account where local law permits, we collect the details needed to set up your profile and connect it to your chosen sign-in route. We do not ask you to place wallet passwords in account messages or privacy requests.

Phone verification

Before account access, the phone verification step helps us connect a request to the right profile. We may keep the verification result and related event time so we can investigate repeated sign-in questions without storing the message content longer than needed.

Payment references

DANA, OVO, GoPay and QRIS can return a reference, status and amount linked to your account request. Bank transfer and virtual account checks use their supplied references. These records help us reconcile a payment without needing your private wallet credentials.

Cookies on devices

Our mobile browser path may use session cookies to keep you signed in during the move from account page to lobby. Preference cookies can remember settings. You can clear browser data through your device settings, although sign-in may be requested again.

Retention and removal

We keep account, verification and transaction records only for operational, dispute-handling or legal needs that apply to the request. Ask us which category concerns you, and we will explain available correction or removal steps where local law permits.

Request ownership

To protect your account, we may ask for a registered phone number, account detail or transaction reference before releasing a copy or changing a record. Never send a wallet password, one-time code or full payment credential in a privacy request.

Privacy Policy Answers For Your Account

These answers focus on the searches we hear around the maya4d Privacy Policy: account records, Indonesian wallet references, cookies, verification and requests for change. If your situation is not covered, use the account help route where local law permits and include only the details needed to identify the issue.

The maya4d Privacy Policy covers account details, phone verification, sign-in cookies, payment references and privacy requests. It explains why we use each category, how we protect account-linked records, how long certain records may be needed, and how you can ask about correction or removal where local law permits.

We use the phone verification result to connect account access and privacy requests to the correct profile. Keeping the result and event time can help us investigate sign-in problems or an ownership question. We do not need your wallet password to complete this account check.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, including a status, amount and transaction reference supplied for reconciliation. Bank transfer and virtual account references may be handled in the same way. Wallet passwords are not needed for this process.

We may use session cookies to keep your sign-in active while you move through the account path where local law permits. Preference cookies can retain selected settings. You can clear cookies through your mobile browser or device settings, but doing so may sign you out and remove saved preferences.

You can request a correction through the account help route where local law permits. State which detail appears wrong and provide your registered phone number or another account reference. We may verify ownership first, then explain whether the record can be corrected and what step follows.

Ask us about removal of a specific account, cookie or payment record through the privacy request path. We assess the request against operational, dispute-handling and legal needs. Where local law permits removal, we explain the available step; some transaction records may need to remain for a defined purpose.

Open the help route connected to your account where local law permits and choose the privacy subject. Include a concise description plus the relevant account or transaction reference. Do not send a wallet password or one-time code. We will use the supplied details to locate and address your request.