Reference

master toto Privacy Policy: Your Data Explained

The master toto Privacy Policy shows what we collect, why we use it and how you can ask us to change or remove eligible account data.

Account dataPayment recordsCookie choicesAccess requests
master toto master toto Privacy Policy: Your Data Explained
CONTACT YOUR WAY

Get Privacy Policy Help Through Support

A clear contact route matters when your account data or payment record needs attention.

Account data request Use the logged-in support path to ask about your stored account details.
Payment record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, share the receipt…
Cookie support If a cookie setting does not behave as expected on your mobile browser, tell…
HANDLING YOUR RECORDS

How We Apply Privacy Policy Controls

We keep the Privacy Policy practical by connecting each data use to an account action you recognise.

Account details

We use your submitted contact and verification details to create, maintain and protect the account.

Device signals

Login time, browser type and device signals can help us investigate an access issue or unusual sign-in.

Cookie choices

Our Privacy Policy explains cookies used around sign-in, preferences and page operation.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can connect a receipt to its status.

Retention period

We retain account, support and payment records for the period needed for their stated purpose or applicable legal duties.

Requesting changes

To request access, correction or deletion of eligible data, contact support from your account and describe the record.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or contacting us about stored data. We explain the account step, device path, cookie setting and payment references in plain terms. If your request concerns eligibility or access from Indonesia, that outcome depends on local law. Use the logged-in support route when a question needs a record check.

It covers account details, phone verification, login device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps confirm that you control the account before access or a data request is handled. It also lets support locate the correct account without relying only on a payment receipt.

No. We use a transaction reference and status details for payment support. You should not send a DANA, OVO, GoPay or QRIS password through support or any account message.

Sign in, open the support path shown in your account and ask for a data access request. Include your verified phone number and the record type, then complete any identity check we request.

Yes, you can ask us to correct eligible account details through logged-in support. State which field is wrong and provide the updated value; we may verify your phone before applying the change.

Cookies can retain sign-in and preference settings in your mobile browser. Changing or clearing them may remove those settings and require a fresh login, while available cookie choices remain explained in the Privacy Policy.

We keep payment references for the period needed to reconcile status, answer support questions and meet applicable legal duties. A deletion request can be assessed through support, subject to those duties.