Reference

Open master38 Privacy Policy Clearly

master38 Privacy Policy explains how we collect, use and protect the details connected with your account, including phone verification, wallet records and device access.

Account recordsWallet dataCookie choicesAccess requests
master38 Open master38 Privacy Policy Clearly
CONTACT PATHS

Ask About Privacy Through Support

A direct support path helps you resolve a Privacy Policy question without guessing where to send it. Include the account phone number or registered account detail that lets us locate your request, but do not send a password or wallet PIN. We can help distinguish a login record from a payment reference, explain a cookie choice and route a correction or deletion request for assessment. If you are in Jakarta or elsewhere in Indonesia, use the account help route shown beside the cashier area and keep your receipt reference ready.

Team online

Account privacy request

Ask through the account help route when you want to know which personal details are linked to your master38 account. We may ask you to confirm the registered phone number before discussing account-specific records, so a different person cannot obtain private account details.

Wallet record question

For a DANA, OVO, GoPay or QRIS record, include the date, reference and displayed status rather than a wallet password. We use those details to locate the relevant transaction entry and explain whether the record is pending, completed or requires another account check.

Correction or deletion

If your name, phone detail or account preference is inaccurate, tell us the field that needs attention and the reason for the request. We assess correction and deletion requests against account security, legal duties and any record needed to resolve an open payment question.

DATA CONTROL

Switch Through Our Privacy Safeguards

Privacy controls work best when they match the way you actually access an account. We separate login credentials from payment references, limit account discussions until the phone verification step is satisfied and…

What we collect

We may receive your account contact details, verification status, sign-in time, device signals, selected settings and records you create while using account services. A QRIS or bank transfer entry can include a reference and status. We collect only the details needed for the stated account, security or payment purpose.

How we use records

We use account data to provide access, confirm requested actions, show the correct wallet status and investigate login or payment discrepancies. We may use device signals to identify unusual access patterns. We do not treat a stored payment reference as permission to access your DANA, OVO or GoPay wallet.

Cookies and sessions

Cookies and similar session tools help keep your account path connected as you move from login to the lobby on a phone or desktop. You can adjust available browser settings, although blocking required cookies may interrupt sign-in or make a selected preference unavailable during the current session.

Account security

Phone verification before account access helps us connect a request with the correct account. Keep your password, verification code and wallet PIN private, and contact support if a sign-in appears unfamiliar. We may ask for a limited account check before changing contact details or discussing stored records.

Retention approach

We retain account, security and payment records for as long as needed for the purpose explained in this policy, account administration, dispute handling or a legal requirement. When a retention reason ends, records are deleted, anonymised or placed beyond ordinary account access according to our handling process.

Your privacy contact

You can ask for access to personal records, a correction, a deletion assessment or an explanation of processing through the account support route. State your request clearly and include the registered account detail. Where access or eligibility is discussed, it depends on local law and identity checks may apply.

Check Privacy Policy Answers Before Access

These Privacy Policy answers focus on the account questions you are most likely to have before connecting a wallet or signing in from a new device. We explain the practical route for data access, corrections, cookies, payment references and account security. If your situation is not covered, send the question through support with the smallest amount of account detail needed to locate the matter.

The master38 Privacy Policy covers account contact details, phone verification, device and session records, cookie choices, wallet references and support requests. It explains why we use those details, how we protect account access, how long records may remain available and how you can ask about a stored record.

The policy can apply to references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We may need the displayed reference, amount and status to resolve an account question. We do not ask for your wallet PIN or treat a reference as wallet access.

Use the account support route and ask for access to your personal records. Include the registered phone detail or another account identifier, but never include your password or verification code. We may confirm your identity before sharing account-specific data, and the response depends on local law.

Yes, you can ask us to correct an inaccurate contact detail, verification record or account preference through support. Name the field and explain the change you need. We may request a phone verification check before editing it, because an unconfirmed change could affect future account access.

When you sign in from a mobile phone, we may process session and device signals needed to keep the account path connected and examine unusual access. Browser cookie settings can change how the session behaves. We do not need an installed application for you to make a privacy request.

You can submit a deletion request through the account support route. We assess which records can be removed and which must remain for account security, payment reconciliation, dispute handling or a legal requirement. A deletion request may also affect access to the account or unresolved wallet records.

Send the question through the account help route shown near the cashier path and describe the exact record or process you are asking about. A payment receipt reference can help with DANA, OVO, GoPay or QRIS matters. Do not send passwords, wallet PINs or verification codes.