Reference

Privacy Policy for sarang slot Accounts

sarang slot Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and access the lobby from a mobile device.

Account dataWallet recordsDevice cookiesAccess requests
sarang slot Privacy Policy for sarang slot Accounts
CONTACT OPTIONS

Three Ways to Ask About Privacy

A clear contact route matters when your account record or wallet reference looks wrong. We use the Support Chat Center for privacy questions linked to sign-in, phone verification or a payment receipt, and we ask you to contact us from the same account whenever possible. If access is unavailable, include the registered phone number and a short description without sending a password or full payment credential.

Team online

Support Chat Center

Use the Support Chat Center to ask why a phone verification record, DANA receipt or QRIS reference appears in your account history. We may request account identifiers to locate the right record, but we do not ask you to disclose your password in chat.

Account access request

If you cannot sign in, tell us the registered phone number, device type and last successful access step. We use those details to locate your account safely before discussing stored information or making a correction.

Wallet record question

For an OVO, GoPay, bank transfer or virtual account reference, send the transaction date and visible reference code. Please hide unrelated balances and credentials; our support route needs enough detail to match the record, not your private wallet access.

DATA PRACTICES

Six Privacy Controls Behind Your Account

We handle this policy area through ordinary account controls rather than vague promises. The sign-in flow uses phone verification before account access, while session and device signals help us detect an unfamiliar…

Collection

We collect account details you provide, verification results, support messages and technical session data. When you use DANA, OVO, GoPay or QRIS, we record the reference needed to connect the transaction with your account, not your private wallet password or PIN.

Cookies

Cookies can keep a sign-in session connected to the correct account and remember basic device preferences. You can manage cookies through your browser settings, though turning them off may require you to verify your phone again when opening the mobile lobby.

Account security

Phone verification is part of the account access path. We may compare device and session signals when a login looks unfamiliar, then ask for an additional account step before discussing private records through Support Chat Center.

Retention

We keep account, support and transaction references for as long as needed for the purpose stated in this policy, account security and applicable legal duties. When a record is no longer needed, our handling follows deletion or restriction requirements where local law permits.

Your requests

You can ask us to access, correct, restrict or delete personal details where local law permits. Send the request through Support Chat Center from your account, and include the specific field or record so we can respond without changing unrelated account data.

Policy contact

For a Privacy Policy question, identify your account phone number and the subject of your request. We may need to confirm ownership before sharing details, especially when the request concerns a QRIS receipt, device history or another person’s account.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet is connected. We explain the account step, the device path and the contact method in plain English for Indonesian customers. If a local rule changes what we can provide, access to a record or request outcome depends on local law.

It covers account details, phone verification, support messages, device and cookie signals, plus transaction references for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains retention, security steps and how you can request access or correction where local law permits.

We use your phone number to create and identify your account and to complete the phone verification step before account access. It helps us distinguish your account from another record when you contact Support Chat Center about a login or wallet reference.

No. The Privacy Policy describes transaction references and status details needed to match DANA or QRIS activity with your account. We do not ask you to send a wallet PIN or password in chat, and you should hide those credentials from any support message.

Open Support Chat Center from your signed-in account and ask for an access request. Include the registered phone number and the categories you need, such as device records or wallet references. We may verify account ownership before sharing information where local law permits.

Yes, where local law permits. Contact us through Support Chat Center and name the exact field that is incorrect, such as a phone detail or account setting. We may request an ownership check, then explain the next step for correcting the record.

We retain account, support and transaction references only for the period needed for the stated purpose, account security and applicable legal duties. The exact period can differ by record type and local requirement. We remove or restrict records when retention is no longer needed.

Yes. You can open the account support area from a mobile browser, check cookie settings in your browser, and submit a Privacy Policy request through Support Chat Center. If cookies are disabled, the mobile path may ask for phone verification again before showing account details.