Reference

sga168 Privacy Policy for Your Account

Your sga168 Privacy Policy explains how we handle account details, phone verification, device access and wallet records linked to DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesSecurity requests

Explore Our Lobby Read FAQ

Check Privacy Before DANA Wallet Access

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

We use the details you provide during account creation to set up access, confirm your phone number and protect the account from unauthorised entry. When you use DANA, OVO, GoPay or QRIS, we may retain transaction references, status updates and the account identifier needed to match

1
a wallet action with your request. Bank transfer and virtual account records can include the selected rail, amount reference and reconciliation status; we do not need your wallet password for this process. Device type, browser details, login time and security events help us identify unusual access.
2
Cookies support login continuity, page settings and security controls, and you can manage browser cookie settings. We may share limited details with payment or technical service providers only when needed for these tasks. Access and processing depend on local law, and this policy applies where local
3
law permits. If you disagree with a change, contact us before continuing to use the account.

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

SUPPORT ROUTES

Ask About Account Data Through Support

A clear support path helps when you need to ask what we hold, correct an account detail or check a wallet record.

Account privacy request Use the logged-in support link to ask for a copy, correction or explanation of account data. We may ask you to complete phone verification before discussing private account details.

Wallet record check For DANA, OVO, GoPay or QRIS questions, open the cashier help path and include the transaction reference. We use that reference to locate status details without requesting your wallet password.

Login access concern If a device or browser no longer opens your account, use the login support link. We may compare recent device events and phone verification before changing access or disclosing account data.

SECURITY PRACTICE

See How sga168 Handles Your Data

Our privacy process follows the account actions you can check yourself: create an account, complete phone verification, use a device, and request help.

Account security

Phone verification is used before sensitive account access changes. We also review device and login signals when a sign-in appears unusual, helping us avoid sending private details to the wrong person.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity is handled through references and status records. We do not need your wallet password to match a payment request.

Cookie control

Cookies can keep a session active, remember selected settings and support security checks. You can change cookie permissions in your browser, although some account steps may then need to be repeated.

Retention timing

We retain account, security and transaction records only for the period needed for account operation, dispute handling, security checks or legal duties that apply where local law permits.

Requesting changes

You can ask us to correct inaccurate details, explain a record or consider deletion where applicable. Send the request through account support and provide enough detail to locate your account.

Policy changes

When this Privacy Policy changes, we update the page and identify the revised subject. Check the policy before using the account again, especially after a change to cookie or wallet handling.

Browse Your Privacy Policy Questions

These Privacy Policy answers address the account questions you are most likely to ask before opening access. They explain phone verification, wallet references, cookies, device checks and requests in direct terms. If your situation is not covered, use the support path while signed in and include only the account details needed to identify the issue.

The sga168 Privacy Policy covers account details, phone verification, device and login events, cookies, wallet references, support requests, retention and changes to your personal data where local law permits.

We use phone verification to confirm account access and protect sensitive changes. It can be required before we discuss private details, restore access or update information linked to your account.

Yes. The Privacy Policy covers DANA, OVO, GoPay and QRIS references, including status and reconciliation details. These records help us match a wallet action without requesting your wallet password.

We may retain browser type, device signals, login time and security events connected with account access. These details help identify unusual sign-ins and support an access request after verification.

Open the support link after login and describe the correction clearly. Include your account identifier and the affected detail, but do not send a password or complete wallet security code.

You can adjust cookie permissions through your browser settings. Cookies support session continuity, selected settings and security checks, so limiting them may require you to repeat some account steps.

We keep account, security and transaction records for the period needed for operation, dispute handling, security checks or legal duties. The applicable period depends on local law and the record type.

sga168 Privacy Policy for Your Account

Ask About Account Data Through Support

See How sga168 Handles Your Data

Account security

Payment references

Cookie control

Retention timing

Requesting changes

Policy changes

Browse Your Privacy Policy Questions

01 What does the sga168 Privacy Policy cover?

02 Why does sga168 ask for phone verification?

03 Does the Privacy Policy cover DANA and QRIS records?

04 What device details does sga168 retain?

05 How can I request a correction to my account data?

06 Can I control cookies used by sga168?

07 How long are Privacy Policy records kept?

Related Pages