Reference

sandibet login Privacy Policy Explained

sandibet login Privacy Policy sets out what we collect when you open an account, verify your phone and move between the lobby and wallet area.

Clear collection detailsWallet record contextPhone verification stepsMobile cookie choices
sandibet login sandibet login Privacy Policy Explained
CONTACT ROUTES

Get Privacy Help Near Account Access

A clear contact path helps when a privacy question concerns a login, wallet status or receipt.

Account privacy request Ask us to access, correct or explain personal data connected with your account. Include your account identifier and the phone verification step involved, but leave out wallet passwords and full payment credentials.
Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the payment reference and status shown in your account. We use those details to locate the relevant transaction trail.
Device and cookie help If the Privacy Policy behaves differently on a mobile browser or desktop, tell us your device path and browser setting. We can explain cookie choices and the account effect without requesting unnecessary personal data.
DATA PRACTICES

How We Handle Your Policy Requests

We keep the Privacy Policy practical by linking each request to a real account event, such as phone verification, a QRIS receipt or a browser session.

Account data

We may use your account details, phone verification result and access history to provide the requested account service, investigate a privacy question and connect a support response to the right record.

Cookie choices

Cookies can remember a browser session and help us understand whether a login step returned correctly. On mobile or desktop, you can adjust browser cookie settings, although some account paths may then need repeating.

Security checks

Before discussing account data, we may ask for a matching account detail or phone verification context. We do not ask for your wallet password, full card credentials or a secret code in an open message.

Retention timing

We retain records only for the period needed for account operation, transaction matching, security checks or a legal request. A QRIS receipt and its status may therefore remain after a session ends.

Change requests

You can ask us to correct inaccurate account details or clarify how a record was used. We may verify the request first, then explain any restriction that depends on local law.

Policy contact

For a Privacy Policy question, describe the data category, account step and preferred response route. Mentioning a device path such as mobile browser or desktop helps us investigate without broad data collection.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the searches we hear around account access, Indonesian wallets, cookies and personal data. If your question concerns a specific record, include its category and account step so our support route can respond with the right context.

It covers account details, phone verification, browser and cookie signals, wallet references, support requests, security checks and retention. It also explains how to request access or correction where local law permits.

Yes. We may keep DANA and QRIS transaction references, receipt details and status results to match a wallet request with your account. We do not need your wallet password for that matching process.

Phone verification helps connect an account request to the correct account before access. It can also support a privacy identity check, while we avoid asking for secret wallet credentials through an open message.

Use the privacy contact route and state the account detail you want corrected, the related account step and your identifier. We may verify ownership before making a change or explaining a legal restriction.

Cookies may keep a mobile browser session active and show whether a login step returned correctly. You can adjust browser settings, but disabling cookies may require you to repeat some account steps.

Retention depends on why the record is needed, including transaction matching, account security, support handling or a legal request. A DANA, QRIS or bank reference may remain after the browser session ends.

Yes. Name the data category, such as phone verification, cookie activity or GoPay status, and identify the account step involved. We will explain the relevant handling route where local law permits.