Reference

simbolslot Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open a simbolslot account, why we use it and how you can ask about your records.

Account dataWallet recordsCookie choicesSecurity requests
simbolslot simbolslot Privacy Policy For Your Account
CONTACT YOUR WAY

Get Help With A Privacy Request

A clear request path helps us respond to questions about your personal records. Tell us which account step or wallet reference you mean, and avoid sending a full password or one-time security code. We can use the account context to separate a cookie question from a request about DANA, QRIS or a login event.

Team online

Account request

Use the account support path to ask what personal details are linked to your profile. Include your registered contact detail and the specific Privacy Policy question so we can locate the right record.

Wallet record

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, state the payment rail and reference shown in your account. Never include your password, PIN or one-time code.

Security concern

If a login or device event looks unfamiliar, contact us through the account help route and describe the device path, such as phone login or desktop access, without sharing secret credentials.

YOUR DATA CONTROL

What We Keep And How We Protect It

We keep this policy practical by connecting each data use to an account action you can recognise.

Collected details

We may handle contact details, account credentials in protected form, device signals, login activity and payment references. The exact data depends on the form you complete and the account action you request.

Cookie controls

Cookies can help remember a session and support account navigation between login and the lobby. Your browser settings let you inspect or clear cookies, although some account steps may then need to be repeated.

Account security

We use account checks around login and important profile changes. Before discussing sensitive records, we may ask for account details that match your profile, never your password or one-time security code.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us connect a wallet request with the correct account record. Bank transfer and virtual account references serve the same checking purpose.

Retention period

We retain records only for the period needed for account operation, security checks, support handling and applicable legal duties. The period can differ by record type and local requirements.

Changes and access

You can ask us to explain, correct or update personal details through the account support path. Where local law permits, we will assess requests against identity, security and record-keeping needs.

Answers About Privacy Policy

These direct answers cover the Privacy Policy questions most relevant when you open an account from Indonesia. If your request concerns a particular login, device or wallet reference, include that detail through the account support path.

It covers account details, login and device signals, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

We use your details to create and protect the account, confirm important changes, connect a wallet reference with the right profile and respond to a specific Privacy Policy request.

Yes. It explains cookies used around sessions and account navigation. You can manage them in your phone or desktop browser, though clearing them may require you to repeat a login step.

Send a request through the account support path with your registered contact detail and the record you mean. We may confirm ownership before discussing or changing personal data.

Yes. The Privacy Policy covers payment references used to match DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests with your account activity.

Retention depends on the record, account security needs, support handling and applicable legal duties. We keep data for the period needed for those purposes and assess removal requests under local rules.

Use the account support route promptly and describe the device path, such as phone or desktop access. Do not send your password, PIN or one-time security code in the request.