Reference

mayora4d Privacy Policy for Your Account Data

mayora4d Privacy Policy explains what we collect when you create an account, sign in from a phone, search Andar Bahar or use DANA and QRIS.

Account clarityWallet contextDevice awarenessIndonesia access
mayora4d mayora4d Privacy Policy for Your Account Data
CONTACT FOR PRIVACY

Get Help With a Privacy Request

A clear contact path helps when your account record, wallet status or device history needs attention. Start from the account help route and describe the specific Privacy Policy request, such as a data copy, correction or deletion question. Include the phone or email linked to your account, but never send a password or full wallet credential. We may ask for an account step that confirms identity before changing a record. This keeps a request from being attached to the wrong person in Medan, Bandung or another supported Indonesian location.

Team online

Account data request

Tell us whether you want a copy, correction or deletion review, then provide the contact detail linked to your account so we can match the request safely.

Wallet record check

If DANA, OVO, GoPay or QRIS activity appears unfamiliar, share the payment reference and date through our support path; keep passwords and full wallet credentials private.

Sign-in concern

When a phone or desktop sign-in looks unusual, contact account help with the affected device and approximate time. We can check access records before discussing account changes.

DATA HANDLING DETAILS

What You Can Expect From Our Privacy Process

We handle Privacy Policy requests as account matters, not as public conversations. Our process separates identity checks, wallet references, device events and game-lobby activity so a request can be answered with the…

Account records

We collect details you enter during account creation and verification, then connect them with sign-in history so we can distinguish your account from another account using the same device.

Wallet references

A DANA, OVO, GoPay or QRIS reference helps us reconcile payment status. We use the reference and outcome needed for the account record, not a public display of your wallet details.

Cookie controls

Cookies can keep an account step connected between pages and remember limited browser state. If you block them, login or policy-request steps may require another verification check.

Security checks

Before we disclose, correct or remove account data, we compare the request with the contact detail already held. This reduces the chance of sending private records to the wrong person.

Retention timing

We retain records while they support account security, payment reconciliation or a legal need. Once those purposes finish, records are deleted or changed so they no longer identify you.

Change requests

Use the account help contact path to ask about access, correction, deletion or a concern about device activity. Describe one request clearly and we will explain the next account step.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers focus on the questions you may have before opening an account with mayora4d. They cover account creation, wallet references, cookies, device access, data requests and local eligibility. If your situation is not listed, use the account help route with the contact detail connected to your account. For every access question, where local law permits, we will explain which step applies and why an identity check may be needed.

It covers account details, verification information, sign-in events, cookies, device activity and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

A phone or browser can create sign-in and security records. We use those records to identify unusual access, protect your account and investigate a request connected with your device.

We may store payment references, status and reconciliation details for DANA or QRIS activity. We use them to connect a receipt with your account, not to publish wallet credentials.

Use the account help contact path and ask for a data copy. Include the contact detail linked to your account; we may complete an identity check before releasing private records.

Yes. Describe the inaccurate field and provide the account contact detail that identifies you. After checking the request, we can update the record or explain why a record must remain unchanged.

We keep data while it supports account security, payment reconciliation or a legal need. When those purposes end, we delete or anonymise the relevant records where local law permits.

Yes. Access and eligibility depends on local law. If you are unsure about your position in Indonesia, contact us through the account help route before sharing additional personal details.