Reference

Privacy Policy For Your sgp138 Account

sgp138 Privacy Policy explains what we collect when you create an account, sign in, use the lobby or connect DANA, OVO, GoPay and QRIS.

Account clarityWallet data careDevice access recordsPolicy contact path
sgp138 Privacy Policy For Your sgp138 Account
CONTACT YOUR WAY

Three Routes For Privacy Questions

A clear contact route matters when a Privacy Policy question affects your account or wallet status. We ask you to use the signed-in support area whenever possible because it helps us confirm which account the request concerns. If you cannot sign in, use the account access contact route and include only the details needed to locate your record. We can then explain the next step without asking you to send payment credentials through an open message.

Team online

Account support

Open the support area after phone verification and choose the privacy question path. We can check the account record connected to your request before discussing sign-in activity, stored contact details or a requested correction.

Wallet status

For DANA, OVO, GoPay or QRIS data questions, include the payment reference shown in your account rather than a wallet password or PIN. We use that reference to separate a status query from unrelated account activity.

Access help

If your account page will not open, contact us through the available access route and mention your device type and sign-in time. This gives our team enough context to investigate without requesting unnecessary personal details.

SIX DATA CONTROLS

What This Privacy Policy Covers

We apply this Privacy Policy across the account journey, from the first phone verification to wallet status checks and sign-out.

Account details

We use the contact details and phone verification information you provide to create, identify and protect your account.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create references used for reconciliation.

Device signals

Your browser, device type and sign-in timing may be recorded to identify unusual access or repeated failed attempts.

Cookies

Cookies can keep a sign-in session working, remember essential choices and help us understand whether a page request completed.

Retention

We retain account, payment and support records only for the period needed for service operation, account protection and legal duties.

Your requests

You can ask about the data connected with your account, request a correction or seek clarification about handling.

Privacy Policy Answers For sgp138

These Privacy Policy answers address the account, device and payment questions we hear most often from Indonesian customers. Each answer points you toward the practical step that helps us identify your record safely. If your question involves a specific wallet reference, keep that reference ready, but never send a wallet PIN, password or full payment credential through a general contact message.

It covers data connected with your account, phone verification, sign-in activity, device signals, cookies, support requests and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account use. It also explains contact routes, retention and requests for access or correction.

Phone verification helps us confirm that the person requesting account access is connected with the account record. It also helps reduce mistaken wallet matching when a payment status from DANA, OVO, GoPay or QRIS is being checked.

Yes. The Privacy Policy covers payment references and status details returned through QRIS, DANA, OVO, GoPay, bank transfer and virtual account processes. We use those details for reconciliation and support, not as a reason to request your wallet PIN.

Sign in, complete the available account check and send a correction request through the support area. Describe the field that needs attention and the correct value. We may ask for an ownership check before changing contact, verification or account records.

You can ask what account data is connected with your record through the signed-in support path. We may verify your phone or account ownership first. The response and available request rights depend on local law and the type of record involved.

Retention varies by record type. Payment references may support reconciliation, account records may support access protection, and device signals may help investigate unusual sign-ins. We keep each category for operational or legal needs, so ask support about a particular record.

Try opening the page from the account menu on your phone or computer, then use the access support route if the page still fails. Tell us the device type and approximate sign-in time, without sending a password or wallet credential.