Reference

sgp slot Privacy Policy For Indonesia

sgp slot Privacy Policy explains how we collect, use and protect the details connected with your account, wallet status and device access.

Clear data purposesWallet details explainedAccount access controlsPolicy contact path
sgp slot sgp slot Privacy Policy For Indonesia
CONTACT YOUR WAY

Choose A Privacy Policy Contact Route

Questions about this Privacy Policy should reach the team through a path that matches the issue. Use live chat when you need help understanding a data request while signed in, or send an account ticket when your question includes a payment receipt or phone verification detail. If you are in Makassar or elsewhere in Indonesia, include your account identifier and the device path you used so we can locate the relevant record without asking you to repeat the whole issue.

Team online

Live chat

Ask about Privacy Policy wording, data use or cookie choices through live chat after signing in. We can explain which account step relates to your question without asking you to post wallet credentials in the conversation.

Account ticket

Send a ticket when your request concerns phone verification, a DANA receipt, QRIS status or another account record. Add the relevant date and reference so we can check the correct entry while limiting unnecessary personal details.

Payment support

For a privacy question connected with OVO, GoPay, bank transfer or virtual account activity, contact support from the account area. We use the payment reference you provide to separate a status question from a request to change personal data.

DATA HANDLING

Browse How We Handle Your Account Data

The Privacy Policy is designed around the records we actually need to operate account access: identity and contact details supplied during account creation, payment references, support messages and technical sign-in information.

Account records

When you create an account, we receive the details you submit and the phone verification result connected with that step. We use those records to identify your account, respond to requests and reduce confusion when the same account reaches support.

Payment references

DANA, OVO, GoPay and QRIS may provide a transaction reference or status linked to your account activity. We use that reference to reconcile a receipt or investigate a stalled wallet status, rather than requesting your wallet password.

Device signals

A mobile browser or desktop sign-in can send technical signals such as device type, browser version and access time. These details help us investigate unusual login behaviour and diagnose why a policy request or account page did not load correctly.

Cookies

Cookies and similar storage can keep an account session working and remember selected settings on your device. You can adjust browser controls, although blocking some storage may require you to repeat sign-in or phone verification before reaching account records.

Retention requests

We retain account, payment and support records only for the period needed for the stated purpose or an applicable legal requirement. Ask support about a category and its retention basis; we may keep limited records when deletion conflicts with that requirement.

Change or access

To request a copy, correction or change, contact us through live chat or an account ticket from your signed-in path. Include the account email or phone reference, and we may confirm ownership before changing any Privacy Policy record.

Find Privacy Policy Answers For sgp slot

These Privacy Policy questions cover the account and payment situations you are most likely to encounter before opening an account. We keep the answers practical: what data is collected, why a device may be recognised, how to request a change and which contact path to use. If your situation is not listed, send support a clear question from your account area.

The sgp slot Privacy Policy covers details used for account creation, phone verification, sign-in, payment references, support messages, cookies and device signals. It also explains why we use those details, how requests are checked and how you can ask about access, correction or retention.

These payment names appear because a receipt or wallet status can be connected with your account record. We may use a transaction reference to reconcile activity or investigate a stalled status, but you should never send a wallet password or secret code through support.

We may retain the phone number and verification result needed to identify your account and protect account access. The Privacy Policy explains the purpose of that record. If you believe the details are incorrect, contact us from the signed-in account path and request a correction.

Yes, you can ask what account, payment-reference, support or device records relate to you. Send the request through live chat or an account ticket, include your account email or phone reference, and complete an ownership check before we disclose or change personal details.

Use the account ticket route for a correction request and identify the field you believe is wrong. We may ask for phone verification or another account check before editing it. Payment references should remain accurate, so include the relevant DANA, QRIS or bank transfer date.

Retention depends on the purpose of the record and any applicable legal requirement. We aim to remove or limit data when it is no longer needed, but payment, account or support records may remain where keeping them is required. Ask support about a specific category.

Yes. The Privacy Policy explains that cookies or similar storage can maintain a session and remember settings on your mobile browser. You can change browser controls, but blocking storage may sign you out or require phone verification again before account access continues.