Reference

Privacy Policy for sar288 and Your Account

At sar288, our Privacy Policy explains how we handle the account details behind DANA, OVO, GoPay and QRIS access, from phone verification to wallet status checks.

Clear data purposesPhone verification explainedIndonesia access wordingWallet details covered
sar288 Privacy Policy for sar288 and Your Account
CONTACT ROUTES

Where To Ask About Your Privacy Policy

A clear account path helps you raise a Privacy Policy question without sending payment details through an unrelated route.

Account support path Open the support area after signing in, choose the Privacy Policy subject and identify the account record or phone verification step you want us to check.
Wallet reference check For DANA, OVO, GoPay or QRIS questions, include the transaction reference and date only. We use those details to locate the record without asking for your wallet password.
Change request Ask us to correct an account detail, explain a retained record or clarify a device event through the same support path. We may verify ownership before making changes.
DATA PRACTICE

How sar288 Handles Account Data

Our handling process is designed around identifiable account actions rather than broad collection.

Account details

We use the details attached to your account to identify your access, connect support requests and maintain the correct wallet status. We do not need your personal wallet password.

Device signals

A mobile browser may provide session and device signals that help us recognise repeated sign-in activity. These details support account protection when you move between the login page and lobby.

Cookies

Cookies can keep a session active, remember selected settings and help us understand whether a page opened correctly. You can manage browser cookie controls, though some account steps may then need repeating.

Game records

A record connected with Live Baccarat, Gates of Olympus or another selected title may show the account, session and transaction context needed for support. It does not reveal unrelated device content.

Retention

We keep account, security and transaction references only for the period needed for support, dispute checks and legal duties. When a record is no longer needed, our handling follows the applicable retention process.

Your request

You can ask what account data we hold, request a correction or seek clarification about its use through account support. We may confirm ownership before disclosing or changing personal details.

Privacy Policy Questions Before Opening An Account

These Privacy Policy answers focus on the account steps Indonesian customers ask about most, including phone checks, wallet references, cookies and access from a mobile device. If your question concerns a particular record, use the account support path with its date or reference.

The sar288 Privacy Policy covers account details, phone verification, device sessions, cookies, support records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect access to the correct account and identify unusual sign-in activity. We use the verification result for account protection and support, rather than requesting access to unrelated phone content.

Yes. The Privacy Policy covers transaction references and status details related to DANA and QRIS, along with OVO, GoPay, bank transfer and virtual account records needed to check an account request.

You can request a correction through the signed-in account support area. Tell us which detail is inaccurate and provide the relevant account context; we may verify ownership before changing the record.

Cookies can preserve a session, remember settings and show whether a mobile page loaded correctly. Browser controls can restrict them, although you may need to repeat login or phone verification steps.

We retain account, security and transaction references for the period needed for support, dispute checks and legal duties. The exact period can vary by record type and applicable local requirements.

Yes. Account access and eligibility depends on local law, and our Privacy Policy applies where local law permits. You can still use the account support path to ask how a local rule affects your request.