Reference

modal50 Privacy Policy And Account Choices

Our Privacy Policy explains what we collect when you open a modal50 account, use DANA or QRIS, and move between the lobby and your account area.

Account dataWallet recordsCookie choicesSecurity controls
modal50 modal50 Privacy Policy And Account Choices
PRIVACY HELP DESK

Get Help With A Privacy Request

A clear contact path matters when a record looks incorrect or you want to understand a Privacy Policy choice. Start from the account support route and describe the issue in plain English, including the email or phone detail connected with your account. We may ask for an account step, such as phone verification, before discussing personal data. Never send a wallet password or full payment credential in a message. We can explain a data request, cookie question or correction request and direct account access issues to the relevant support queue.

Team online

Account contact

Use the support path connected with your modal50 account for a Privacy Policy request. Include your account contact detail and the specific record or cookie choice you want us to check, so we can locate the correct account without asking for a wallet password.

Wallet records

If a DANA, OVO, GoPay or QRIS reference appears wrong, tell us the date, amount reference and wallet name shown in your account area. We use that detail to trace the record while keeping your private wallet credentials outside the support conversation.

Access concern

For an unfamiliar sign-in or a stalled phone verification step, contact us through the account support route before sharing more details. We may confirm account ownership first, then explain which security record or access event relates to your Privacy Policy request.

DATA CONTROL POINTS

What We Handle And Why

The practical side of our Privacy Policy is visible in ordinary account steps. We separate identity details from wallet references where the process allows, limit account access through…

Account details

We may hold the contact details and phone verification result you submit when opening an account.

Payment references

A DANA, OVO, GoPay or QRIS transaction reference can connect a wallet action with the correct account status.

Cookie settings

Cookies can preserve a sign-in session, remember a page setting or help us understand which account step failed.

Account security

Phone verification and device signals help us assess whether an access attempt matches your account pattern.

Retention timing

We keep different records for different periods rather than treating every account detail alike.

Your request

You can ask what personal data we hold, request a correction and ask about deletion where the law allows.

Privacy Policy Answers For modal50

These Privacy Policy answers address the account and payment questions we expect from Indonesian customers before they open an account. They cover the data created by phone verification, wallet references, cookies, device access and support requests. If your situation is not covered, use the account contact route with a specific question. Access and eligibility always depends on local law, and we will explain the relevant request path where local law permits.

The modal50 Privacy Policy covers account details, phone verification, device and browser signals, cookies, payment references, support messages and security events. It explains why we use each category, how retention works and how you can ask about access, correction or deletion where local law permits.

Yes. Our Privacy Policy includes references created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account routes. These references help match a payment status with your account. They do not require you to send a wallet password to support.

Phone verification helps connect an account request to the contact detail you supplied and can reduce mistaken or unfamiliar access. The Privacy Policy describes this account step and related security records. We may ask for ownership confirmation before discussing personal data or changing account details.

You can send a data access request through the account support route and specify the categories you want checked, such as profile details, payment references or support messages. We may verify ownership first. Our response and any available limits follow the Privacy Policy and local law.

Tell us which account detail appears inaccurate and provide the contact detail linked to your account. We may confirm ownership before making a correction. For a DANA, OVO, GoPay or QRIS reference, include the date and displayed reference so we can check the right record.

Cookies may keep your session active, remember a setting or show where an account step stopped working. The Privacy Policy describes those uses and your choices. If you remove cookies, you may need to complete phone verification or sign in again on your device.

Retention varies by record type and purpose. Account details, payment references, security events and support messages may follow different periods. The Privacy Policy explains the applicable approach, and you can ask support about a category. Any deletion request remains subject to local law and required records.