Reference

namislot Privacy Policy for Indonesia

namislot Privacy Policy explains what we collect, why we use it and how you can request changes to your account records.

Account dataWallet recordsCookie choicesContact route
namislot namislot Privacy Policy for Indonesia
CONTACT OPTIONS

Privacy Questions Meet Account Support

A clear contact path matters when your Privacy Policy question concerns a phone check, wallet reference or stored account record.

Account access If a phone verification step blocks your account, contact support through the account route and describe the screen shown. We use the linked profile details to check the request.
Wallet records For a DANA, OVO, GoPay or QRIS reference, send the receipt number and account identifier only. We can check the stored payment reference without requesting your wallet password.
Data requests Ask us to correct, explain or remove eligible personal data through support. State the requested action clearly, and we may verify account ownership before changing any record.
DATA HANDLING

What We Do With Your Records

We keep the Privacy Policy practical by connecting each data use to an account task you can recognise.

Account details

We use your phone number and verification result to create and protect your account. Check that these details are current so an ownership request can be matched to the correct profile.

Device sessions

When you sign in on mobile or desktop, we record session and security signals to identify unusual access. Signing out of shared devices helps reduce exposure from an open account session.

Cookies

Cookies can retain session preferences and help pages load with the right account state. You can manage cookie settings in your browser, although some account steps may then need to be repeated.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we keep references needed to match a receipt or status check. We do not need your wallet password for that task.

Retention choices

We retain personal records while they serve account, security or legal needs. When a record no longer has that purpose, our process removes it or changes it so it no longer identifies you.

Change requests

You can ask us to correct eligible account data or explain a specific use. Include your linked account contact and requested change; we may confirm ownership before acting.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account, device and wallet questions we expect you to ask before opening an account. If your situation is not covered, use the support route with only the details needed to identify your profile.

It covers account details, phone verification, device sessions, cookies, payment references and requests concerning your personal data. It also explains retention and the support path for privacy questions.

Phone verification helps connect an account request to the person attempting access and helps us investigate unusual sign-in activity. We use the result for account security and ownership checks.

Yes. The Privacy Policy covers references linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when those references help match a receipt or check account status.

Cookies may retain session preferences and account-state settings so a page can recognise your current visit. Browser controls let you manage them, though some account steps may repeat.

You can contact support with your linked account contact and explain whether you want an eligible record corrected or a data use clarified. We may verify ownership before responding.

We keep records while they support account operation, security or legal needs. After that purpose ends, our retention process removes or anonymises the record where applicable.

The page is provided so you can understand our data practices, while account access and eligibility depends on local law. Where local law permits, use the stated support route for a local request.