Reference

Open tmokwin Privacy Policy Before Account Access

tmokwin Privacy Policy explains what we collect when you create an account, sign in from a mobile device, or connect DANA, OVO, GoPay and QRIS.

Clear data purposesWallet details explainedAccount request path
tmokwin Open tmokwin Privacy Policy Before Account Access
CONTACT ROUTES

Ask About Privacy Through Account Support

A direct support request gives you a practical route when a privacy question affects account access or a wallet record. Tell us which account step concerns you, avoid sending a full password, and include only the receipt or device detail needed to locate the issue. We can explain the applicable Privacy Policy section and confirm the next step.

Team online

Account access

If phone verification is not completing, contact account support with your registered number and device path. We use those details to locate the access record without asking you to disclose your password.

Wallet records

For a DANA, OVO, GoPay or QRIS privacy question, share the transaction reference and account identifier. We can explain which payment record is held and why it appears in your account history.

Policy requests

When you request a copy, correction or clarification, identify the relevant account step and contact route. We may ask for account verification before discussing personal data tied to your profile.

DATA PRACTICES

Understand How We Handle Your Privacy

Privacy choices should be clear before you open an account, especially when a mobile device and local wallet are involved.

Account data

We may handle your phone number, verification result and account activity to support sign-in and account checks. We use the details for the stated account purpose rather than requesting unrelated profile data.

Payment references

A DANA, OVO, GoPay or QRIS transaction may create a reference, status and receipt trail. These records help us match a wallet event to your account when a payment question is raised.

Cookies

Cookies and similar device signals can keep your session connected while you move from login to the lobby. Your browser settings provide a way to restrict them, although some account steps may then behave differently.

Account security

Phone verification and sign-in checks help us distinguish an account holder from an unknown device. Never send your password in a support message, and contact us if an unfamiliar access record appears.

Retention

We retain account, verification and payment references for the period needed for the stated service, security and record duties. The Privacy Policy explains the reasons for keeping each category and when removal can be requested.

Change requests

You can ask us to correct account details or clarify how a record is used. Send the request through account support, name the relevant field, and complete verification before we discuss personal data.

Find Answers About tmokwin Privacy Policy

These Privacy Policy questions cover the account actions you are most likely to take from Indonesia, including phone verification, wallet linking and a mobile sign-in. Each answer points back to a practical support step, so you know what to prepare before contacting us.

It covers account details, phone verification, device signals, cookies, payment references and support requests. It also explains retention, security handling and how to ask for correction or clarification.

We use your phone number for account creation and verification before access. It helps connect the sign-in record to your account, while any use or retention is described in the Privacy Policy.

Yes. The policy covers references connected with DANA, OVO, GoPay and QRIS, including payment status and receipt details needed to match a wallet event with the correct account.

Contact account support, identify the field that needs correction and provide the registered account detail requested for verification. We will explain the applicable Privacy Policy process before making a change.

You can request clarification about account, device or payment records connected with your profile. Include the relevant account step, and complete verification so we can protect the data from an unrelated request.

Cookies and device signals can keep a mobile session connected between sign-in and the lobby. You can adjust browser settings, but restricting cookies may affect verification or account navigation.

Access depends on local law and is available where local law permits. The Privacy Policy explains data handling for an eligible account, while support can clarify the account route for your circumstances.