Reference

Privacy Policy for your menarah4d account

Our menarah4d Privacy Policy shows how we handle the details linked to your account, phone verification and wallet activity before you open the lobby.

Clear data useWallet record detailsMobile access notesPolicy access anytime

Explore Our Lobby Read FAQ

See how wallet and account data moves

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

We use account details to create your profile, confirm your phone before account access, protect sign-in activity and match wallet records to the correct account. When you choose DANA, OVO, GoPay or QRIS, we retain the transaction reference and status needed to reconcile a deposit or

1
withdrawal request; the payment provider may handle additional data under its own terms. Cookies help us keep your session active on a mobile browser and remember selected settings, while security records help us investigate unusual access. We keep records only for the period needed for account
2
support, legal duties or dispute handling, then remove or anonymise them through our internal process. Where local law permits, you can ask what data we hold, request a correction or contact us about deletion. Access and eligibility depends on local law, so the policy should be
3
read before opening an account.

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

CONTACT THE POLICY TEAM

Get help with a privacy request

A clear support path helps when your account record or wallet reference needs attention.

Account data request Ask us to confirm the account details connected to your phone verification step. We may request account identifiers so we can separate your record from another profile safely.

Wallet record check For DANA, GoPay, OVO or QRIS questions, share the transaction reference and status shown in your account. Never send a wallet PIN, one-time code or full password.

Access correction If your name, phone number or contact detail is inaccurate, use the support path to request a change. We check the account step before applying any personal-data update.

DATA HANDLING DETAILS

Keep control of your account records

Our privacy process follows the practical steps you see during account access: phone verification, sign-in protection, wallet matching and policy requests.

Account security

We use phone verification before account access and keep sign-in events available for security checks. If activity looks unusual, we may ask you to confirm ownership through the account contact already on file.

Cookie choices

Cookies keep your session working, remember selected settings and help us understand technical errors. You can manage or clear them in your browser, although some account functions may need an active session.

Payment references

A DANA, OVO, GoPay or QRIS reference lets us match a wallet status to your account request. We do not need your wallet PIN to check whether that reference is pending or complete.

Mobile browsing

When you access the lobby from a mobile browser, we process session and device signals needed to keep the page connected. We do not require a separate app download for this access path.

Record retention

We retain account, support and transaction records for account operation, dispute handling or legal duties. When a record is no longer needed, our process removes it or changes it so it no longer identifies you.

Change requests

You can ask us to correct, access or delete eligible personal data through support. Include your account contact and a precise request; we may verify ownership before changing or releasing records.

Answers before you open an account

These Privacy Policy answers focus on the account steps and local wallet records you are most likely to ask about before joining. If your question concerns a particular transaction, use the reference shown beside the relevant DANA, OVO, GoPay or QRIS status and contact our account support route.

It covers account details, phone verification, cookies, device session data, support requests and payment references connected with your account. It also explains retention, security checks and how to request access or correction.

We use phone verification before account access to confirm that the contact belongs to you and to reduce mistaken or unauthorised entry. We do not ask you to send a password or wallet PIN.

Yes. The Privacy Policy explains how we use DANA and QRIS references to match a transaction status with your account. The relevant payment provider may handle additional details under its own privacy terms.

You can contact our account support route with the phone or email linked to your profile and ask which eligible records we hold. We may verify account ownership before providing the requested data.

Send a correction request through the support path and identify the inaccurate name, phone number or contact detail. Include enough account context for us to locate the record, but never include your password.

We keep account, support and transaction records while they are needed for account operation, security checks, legal duties or disputes. After that period, we remove or anonymise them through our internal process.

Yes. Account access and eligibility depends on local law, while certain data requests may also depend on applicable rules. Read the current Privacy Policy and contact us if you need a local clarification.

Privacy Policy for your menarah4d account

Get help with a privacy request

Keep control of your account records

Account security

Cookie choices

Payment references

Mobile browsing

Record retention

Change requests

Answers before you open an account

01 What does the menarah4d Privacy Policy cover?

02 Why does menarah4d need phone verification?

03 Does the Privacy Policy cover DANA and QRIS records?

04 Can I request a copy of my account data?

05 How do I ask menarah4d to correct my details?

06 How long does menarah4d keep personal data?

07 Does Privacy Policy access depend on local law?

Related Pages