Reference

pajak88 Privacy Policy: Your Data And Account Access

Our pajak88 Privacy Policy explains what we collect when you create an account, use DANA or QRIS, and open the lobby on mobile or desktop.

Account data explainedWallet activity clarifiedMobile privacy coveredAccess depends on local law

Explore Our Lobby Read FAQ

How Privacy Works Around Your Account

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

We collect account details such as your phone number, verification result, login records and support requests so we can identify your account and respond when access stalls. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account help us match a deposit or

1
withdrawal request without storing wallet credentials that we do not need. Device type, browser signals and security events help us detect unusual sign-ins. We use this data for account administration, payment reconciliation, fraud prevention, service messages and legal obligations. Retention depends on the purpose and applicable
2
rules; after that period, records are deleted or separated from direct account identifiers where practical. Access to pajak88 and any related processing depends on local law. You can ask about a record through the support route connected to your account.

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

HELP WITH PRIVACY

Get Clear Answers About Your Data

A clear account route helps you raise a privacy question without sending payment details through an unverified channel.

Account support route Use the support path inside your signed-in account for privacy questions. We may ask for a verification step before discussing phone, login, DANA, OVO, GoPay or QRIS records.

Payment reference check If a privacy request concerns a bank transfer or virtual account, share the transaction reference rather than a wallet password. This lets us locate the record while limiting sensitive exposure.

Device access concern Tell us when a mobile or desktop sign-in looks unfamiliar. We can review the account event, help secure access and explain which device signals were connected with that session.

DATA HANDLING

What We Do With Privacy Requests

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

Collected account fields

We may hold your phone number, verification status, login history and support messages. These fields connect an account request to the correct person and help us investigate access questions.

Wallet references

DANA, OVO, GoPay and QRIS references can appear in payment records, along with bank transfer or virtual account identifiers. We use them to reconcile activity, not to request your wallet password.

Cookies and sessions

Cookies and similar browser storage can remember a session, preserve basic preferences and support security checks. Clearing them may sign you out or require another account verification step.

Account protection

We examine sign-in time, browser or device signals and unusual account events to reduce unauthorised access. If a new device opens the account, an additional check may be requested.

Retention periods

We retain records only for the operational, security, dispute or legal purpose that requires them. When a period ends, we delete, aggregate or separate the record where practical.

Changes and requests

Ask for access, correction or deletion through the signed-in support route. Include the relevant account or payment reference, and we will assess the request under applicable rules.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers cover the account steps most relevant to an Indonesian customer, from phone verification to wallet references and mobile sessions. If your question concerns eligibility or access, the answer depends on local law and the details of your request.

It covers account details, phone verification, payment references, device signals, cookies, support messages, retention and your available requests. It also explains how we handle records linked with DANA, OVO, GoPay, QRIS and bank transfer.

Phone verification helps us connect an account request to the correct person and protect sign-in activity. It may be required before account access or before we discuss private records through the support route.

Yes. The Privacy Policy explains that DANA and QRIS references may be used to match payment status. We can also process OVO, GoPay, bank transfer and virtual account references for reconciliation.

We may record device type, browser details, session timing and security signals. On a mobile browser, these details help identify an unusual login; clearing cookies can end the session and trigger another check.

Sign in, open the account support route and describe the field that needs correction. Provide the relevant account reference, not a wallet password. We assess the request where local law permits.

Retention varies by the reason for collection, such as account administration, payment reconciliation, security, disputes or legal duties. When the relevant period ends, we delete or separate records where practical.

Yes. A request may concern service or device events created while opening Mobile Legends or another lobby area. Use the signed-in support route so we can verify the account before responding.

pajak88 Privacy Policy: Your Data And Account Access

Get Clear Answers About Your Data

What We Do With Privacy Requests

Collected account fields

Wallet references

Cookies and sessions

Account protection

Retention periods

Changes and requests

Privacy Policy Answers For Indonesian Accounts

01 What does the pajak88 Privacy Policy cover?

02 Why does pajak88 need phone verification?

03 Does the Privacy Policy include DANA and QRIS data?

04 What device data is collected when I sign in?

05 How can I request a correction to my data?

06 How long does pajak88 keep account records?

07 Can I ask about data linked to Mobile Legends?

Related Pages