Reference

niastoto Privacy Policy for Your Account

Live Baccarat, Great Rhino Megaways and League of Legends sit behind one clear Privacy Policy, so you can see how we handle account, device and wallet details before…

Account dataWallet recordsDevice choicesPolicy access
niastoto niastoto Privacy Policy for Your Account
CONTACT PATHS

Check Privacy Policy Questions Through Support

A direct support path helps you resolve privacy questions without sending sensitive details through random channels. From your signed-in account, open the support route near the cashier area and describe the record you want checked. If login access is unavailable, use the contact route shown on the niastoto site and include only the minimum account detail needed to locate your request.

Team online

Account privacy request

Ask us to find, correct or explain account records after phone verification. Keep your message focused on the specific detail, such as a login record or profile field.

Wallet record question

For DANA, OVO, GoPay or QRIS references, send the date and status shown in your account rather than a full wallet password or unrelated personal material.

Access issue

When a privacy request follows a stalled login, tell us the device path and account step that failed. We use that context to separate access help from data changes.

DATA PRACTICE

Explore How We Handle Your Policy Rights

Privacy choices work best when each account step has a clear reason. We limit collection to records needed for access, wallet reconciliation, security and support, while giving you a practical route to…

Account details

When you open an account, we use the details you submit to create your profile and connect phone verification with the right sign-in. We do not ask for unrelated information during that step.

Phone verification

A phone check helps us confirm account access and respond to requests about your records. We may keep a verification result and related event time without storing your private conversation content.

Device signals

Browser, device and login signals help identify repeated access or unusual sign-in patterns. On mobile, these signals relate to the path from login to the lobby, not to unrelated device activity.

Cookies and settings

Cookies can keep a session open, remember a selected setting and help us understand whether a page loads correctly. You can manage browser storage through your device settings, though some account steps may then need repeating.

Retention choices

We keep account, payment-reference and support records for as long as operational, security, dispute or legal needs require. After that period, we remove or anonymise them through our retention process.

Change request

To request a correction or ask what data is held, contact support from your account when possible. We may ask for phone verification before changing records so another person cannot alter your profile.

Browse Privacy Policy Answers Before Joining

These Privacy Policy answers address the searches we hear most often from people preparing an account in Indonesia. They cover collection, wallet references, cookies, access requests and the verification step used to protect account changes. If your situation is different, send a focused request through our support route.

It covers account creation, phone verification, login activity, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Device and browser signals help us recognise an unusual sign-in and keep the mobile path from login to the lobby working. They are used for account security and service operation, not unrelated device activity.

No. Our Privacy Policy concerns payment references and status details needed to reconcile an account action. You should never send a wallet password, security code or full private credential through support.

Contact support from your signed-in account, name the record that appears wrong and complete phone verification if requested. We then assess the request and update applicable account details through the account process.

We retain account, security, payment-reference and support records only while operational, dispute, security or legal needs require them. We then remove or anonymise them under our internal retention process.

Yes. Send a specific access request through the support route, preferably while signed in. Tell us which area you mean, such as login events, cookies, phone verification or wallet status.

Yes. Account access and any applicable privacy request depend on local law. We apply this policy where local law permits and explain the next step when a request needs additional verification.