Reference

master38 Privacy Policy For Your Account

master38 Privacy Policy explains how we collect, use and protect the account details connected with your lobby access and wallet activity.

Clear data purposesWallet record contextPhone verificationPolicy request path

Browse Our Lobby Read FAQ

How We Use Account And Wallet Data

master38 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy starts with a simple rule: we use personal data for account access, payment checks, security, support and required record keeping, not for unrelated activity. When you open an account, we may receive your name, contact details, device signals and phone verification result. A

1
DANA, OVO, GoPay or QRIS reference helps us match a wallet event to your account, while bank transfer and virtual account records help resolve payment status. We limit access to staff who need it for these tasks and retain records only as long as the purpose
2
or a legal requirement calls for. Where local law permits, you can request access, correction or deletion through our support path.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Privacy Policy Help Through Your Account

A privacy question should not leave you searching through the lobby. We connect policy requests with the same account route used for login and wallet status checks, so our team can confirm which record you mean before making a change. Contact us through the support channel shown in your account, include your registered phone number and describe the request. We respond during the support hours displayed on the site, with access subject to local law.

Team online

Account request

Use the support route inside your account when you want a copy of the personal data linked with your master38 access. We may ask for phone verification before releasing details, so a private request is not sent to the wrong person.

Wallet record

If a DANA, OVO, GoPay or QRIS entry appears unfamiliar, send the date, amount reference and wallet name through support. We use those details to trace the relevant account record without asking you to share a wallet password.

Correction route

Tell us which account field needs correction, such as a contact number or profile detail. Our team checks the request against your verified account and explains any reason a record must remain unchanged under an applicable legal requirement.

DATA PRACTICES

Cookies, Devices And Account Protection

Privacy Policy choices also apply to the way the lobby works on your device. We use necessary cookies and similar signals to keep sessions active, remember security settings and detect unusual account…

Session cookies

Necessary cookies help keep your signed-in session connected as you move from the account page to policy details. Clearing them can sign you out and may require another phone verification before your account opens again.

Device signals

We may record browser, device and connection signals to spot repeated access attempts or unusual changes. These signals support account protection; they do not give us permission to collect unrelated content from your phone or computer.

Account security

Keep your phone number and account access details private. If a login concern reaches support, we compare the request with account records and can ask for phone verification before discussing personal or wallet-linked data.

Payment records

A payment reference is used to reconcile activity, investigate a stalled status and answer your request. We do not need your DANA, OVO, GoPay or QRIS password to check the record attached to your account.

Retention period

We keep personal data while your account relationship, an open support matter or a legal record requirement makes it necessary. When the relevant purpose ends, records are removed, anonymised or restricted according to our retention process.

Request changes

For access, correction, deletion or a question about cookies, contact support from the account path shown on the site. Include the subject of your request, and we will explain the next verification step and any local-law limitation.

Privacy Policy Questions About master38

These Privacy Policy answers address the account questions we expect before you open access. They cover the data connected with your phone, device and wallet records, plus the practical route for requesting a copy or correction. If your situation is specific, contact support from the account area so we can review the relevant record under the law that applies to you.

The master38 Privacy Policy covers account details, phone verification, device signals, cookies, payment references, support messages and retention. It explains why we use each category, who may handle it for account operations and how you can request access or correction where local law permits.

Phone verification helps us connect an account request to the person who controls the registered contact number. We may request it before opening account details, changing sensitive fields or discussing DANA, OVO, GoPay, QRIS, bank transfer or virtual account records.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS. We use them to match a transaction to your account and investigate a delayed status. We do not ask for your wallet password through support.

Send an account-data request through the support path shown after login. State that you are asking under the Privacy Policy and include your registered phone number. We may verify your identity first, then explain which records can be supplied and the expected handling steps.

You can ask support to correct an inaccurate contact or profile detail. Describe the field and the correct value, then complete any requested phone verification. We will update eligible records or explain why a record must stay unchanged because of an applicable legal duty.

We retain data while it supports your account, an unresolved payment or support matter, or a record requirement under applicable law. Once the relevant purpose ends, we remove, anonymise or restrict the data through our retention process rather than keeping it without a reason.

Use the support route in your account and ask specifically about cookies or device signals. Necessary cookies help maintain your session, while available controls address optional functions. We can explain the effect of clearing cookies, including why you may need to verify your phone again.

master38 Privacy Policy For Your Account

Privacy Policy Help Through Your Account

Account request

Wallet record

Correction route

Cookies, Devices And Account Protection

Session cookies

Device signals

Account security

Payment records

Retention period

Request changes

Privacy Policy Questions About master38

01 What does the master38 Privacy Policy cover?

02 Why does master38 ask for phone verification?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How can I request my master38 account data?

05 Can I correct personal details on my account?

06 How long does master38 keep personal data?

07 Where can I ask about cookies in the Privacy Policy?

Related Pages