Reference

Privacy Policy for Your matka Account

Your matka Privacy Policy sets out what account, device and wallet details we handle when you open the lobby from Indonesia.

Clear data purposesWallet record contextAccount request path
matka Privacy Policy for Your matka Account
HELP WITH DATA

Get Help With Privacy Requests

A clear contact route helps you act on the Privacy Policy rather than search through account screens. Start with the support contact displayed in your matka account when you need to ask about personal data, phone verification or a wallet reference. Include the account detail and request type you can safely share; we may ask for a further account step before discussing private records. When access is unavailable, use the contact route printed on this policy page and mention whether the issue concerns login, DANA, OVO, GoPay or QRIS.

Team online

Account privacy path

Use the privacy contact shown beside your account support area to ask what personal details we hold, why they are used, or which correction step applies to your matka record.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, share the transaction date and account identifier through the displayed support route so we can check the record without exposing private wallet details.

Access request route

For a copy, correction or removal request, follow the contact instructions on this Privacy Policy page. We confirm the account step first, then explain what can be changed and what must be retained.

DATA PRACTICES

How matka Handles Account Records

Our Privacy Policy connects each data practice to a practical account event: opening an account, confirming a phone number, signing in on mobile, or checking a wallet status.

Account data

We may handle your account identifier, contact details, phone verification result and sign-in events so the requested account path can function. These records also help us match a privacy request to the correct account.

Wallet references

DANA, OVO, GoPay and QRIS references help us connect a payment status with the right account without treating a wallet reference as your full account history. We use the reference for the stated transaction purpose.

Cookies and devices

Cookies and device signals can keep your session active, remember access choices and identify unusual sign-in behaviour. On a mobile browser, these controls may appear when you move from login to the lobby.

Account security

Phone verification and sign-in checks protect private account details from an unapproved request. Never send a password or one-time code through support; use the account step requested by the Privacy Policy contact route.

Retention choices

We keep a record only for as long as its stated purpose, account need or applicable requirement calls for. When you ask about removal, we explain which records can be cleared and which transaction references remain necessary.

Changes and contact

You can ask about your data, request a correction or seek a copy through the contact path displayed with this policy. Include enough account context for verification, and we will explain the next available step.

Privacy Policy Answers For DANA Users

These Privacy Policy answers focus on the questions you may have before opening a matka account from Indonesia. They cover wallet references, cookies, phone checks, account requests and local access wording without turning the policy into a general lobby description. If your situation is not listed, use the contact path shown on this page.

The matka Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies and payment references. It explains why we use each category, how long records may be kept, and how you can ask for access, correction or removal.

A DANA or QRIS reference helps us connect a payment status with your account and respond to a receipt or status question. We use it for the stated transaction purpose, not as a substitute for your complete wallet history.

Yes. Use the contact route shown with this Privacy Policy and identify the account safely enough for verification. We explain which records can be copied, what account step is required, and whether a lawful retention reason affects the response.

Send a correction request through the displayed privacy contact path and state which account detail is inaccurate. We may confirm your phone or another account step before changing the record, so private information is not altered by an unapproved request.

Cookies and device signals may support your mobile session, remember access choices and help identify unusual sign-in behaviour. If you clear them, you may need to sign in again before moving from the account screen to the lobby.

Retention depends on the purpose of the record, your account status and applicable requirements. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may remain when needed to check a transaction or answer a later request.

Yes. Where account access or eligibility is discussed, it depends on local law. The Privacy Policy describes our handling for the available service path, while your location may affect whether you can open or use an account.