Reference

Open the sorbet Privacy Policy Clearly

Your account details, wallet references and mobile access deserve a clear explanation, so this Privacy Policy sets out how sorbet collects, uses, stores and protects them.

Account dataWallet recordsCookie choicesPolicy requests
sorbet Open the sorbet Privacy Policy Clearly
REQUEST HELP

Check Policy Support Through Your Account

A clear contact path matters when you want to ask about personal data rather than a game or wallet result.

Account data request Ask us to explain the account details connected with your sorbet access, including the…
Wallet record query If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account records…
Cookie and device help Tell us whether you opened sorbet on a mobile browser or desktop and describe…
HANDLING DETAILS

Explore How We Handle Your Privacy

Our Privacy Policy is useful only when it matches the account steps you can see.

Account creation

When you open an account, we collect the details needed to establish access and send you through clear phone verification.

Payment records

A DANA, OVO, GoPay or QRIS action can create a reference, method label, status and time record.

Cookies and sessions

Cookies and similar session tools can remember sign-in state, protect the account path and help us see why a mobile…

Device protection

We may use device, browser and connection signals to detect unusual access and investigate a stalled login.

Retention decisions

We keep records only as long as needed for the purpose described in this Privacy Policy, account security, payment reconciliation…

Change requests

To request access, correction or deletion, contact support from the account route and identify the record involved.

Browse Privacy Policy Answers for sorbet

These Privacy Policy answers address the searches we expect before account creation: what data is collected, why payment references appear, how cookies work and how you can ask for a change. We keep the examples close to the account path you use in Indonesia, including mobile access, phone verification and local wallet records. If your situation is not covered, contact support with the smallest useful account detail.

It covers data connected with your account, phone verification, mobile or desktop session, cookies, support requests and payment references. It also explains how we use those records for access, security, reconciliation and legal needs, with eligibility and access handled where local law permits.

Phone verification helps us confirm that the person opening or accessing the account controls the stated contact route. It supports account security and policy requests, especially when you ask to change login details or discuss a wallet record linked to DANA, OVO, GoPay or QRIS.

Yes. The Privacy Policy covers payment references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We may retain the selected method, reference, status, amount and time so a receipt or stalled cashier status can be checked.

Cookies can preserve a session, support account security and help us diagnose repeated login prompts on your mobile browser. You can change cookie settings in the browser, but restricting them may sign you out or require phone verification again before account access.

You can request correction through the account support route. State which record is wrong and provide the account identifier needed to locate it. We may verify ownership before changing phone, login or payment-related data, so an unauthorised person cannot alter your record.

Retention depends on the purpose of the record, account security, payment reconciliation, support history and applicable legal requirements. We do not promise one fixed period for every record. You can ask support what category applies to your data and whether deletion is available.

Use the account support path and describe whether you want access, correction, deletion, cookie help or an explanation of payment data. Include only the account detail needed for verification, never a wallet password, and mention whether the issue appeared on mobile or desktop.