Reference

7777w Privacy Policy for Your Account Data

7777w Privacy Policy sets out how we handle your account details, phone verification, wallet records and mobile-browser activity.

Account data clarityWallet record scopeAccess depends on local lawCookie choices
7777w 7777w Privacy Policy for Your Account Data
REQUEST ROUTE

Contact Us About Policy Requests

A policy question should not get lost beside a wallet issue, so we keep account support close to the access path.

Data access request Ask us which account details, phone-verification records, device events or DANA, OVO, GoPay and QRIS references are linked to your profile through the account support route.
Correction request If your phone number, identity detail or payment reference is inaccurate, send the affected field and account reference; we may ask for an ownership check before changing it.
Account privacy help When login or wallet status stalls, contact the same support path and describe the screen, mobile browser and account step involved so we can separate access trouble from a data request.
SECURITY PRACTICE

Protect Your Account Data on Mobile

Our handling process follows the account journey rather than collecting every detail by default. We use data to provide access, check payment status, protect the account and respond to your policy requests.

Purpose-based handling

We use contact details for account access and support, phone verification for ownership checks, and wallet references for payment matching. We do not treat casino or sports browsing as permission to collect unrelated data.

Cookie controls

Cookies and similar browser records can keep a session available, remember selected settings and help identify suspicious login patterns. You can clear browser cookies, though doing so may require another account verification step.

Account security

We may compare login timing, device signals and phone-verification status when access looks unusual. Never send your password, wallet PIN or one-time security code through a support request.

Retention periods

We retain account, payment and support records only for the period needed for account operation, security checks, dispute handling or a legal requirement that applies where local law permits.

Requesting changes

You can ask us to correct inaccurate profile data, explain a processing purpose or provide available account records. Include your account reference, the requested change and a safe way to receive our reply.

Third-party processing

Wallet and bank rails may process transaction details to complete DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. Their own privacy terms may apply to records they handle directly.

Browse Privacy Policy Answers for Account Holders

These Privacy Policy answers cover the questions we expect before account access: payment records, cookies, phone verification, correction requests and account closure. If your situation is different, use the privacy support route attached to your signed-in account or the access path shown when login is unavailable.

It covers account details, phone verification, login and device events, cookies, support requests, casino or sports browsing records, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use your phone number to create and protect the account, complete phone verification before access, respond to account requests and help identify the correct profile when payment status needs checking.

Yes. The Privacy Policy explains how we handle QRIS, DANA, OVO and GoPay references, including transaction status, receipt details and account matching. Wallet providers may separately control records held in their systems.

Use the privacy request route shown after sign-in and provide your account reference. We may verify ownership through the registered phone details before releasing available records or explaining why a record is retained.

Yes. Send the incorrect field, the replacement detail and your account reference through support. For safety, we may request phone verification or another ownership check before applying a correction.

Cookies can preserve your session, remember settings and help detect unusual sign-in behaviour. Clearing them may sign you out and trigger phone verification when you return through the mobile browser.

Yes. Access, deletion, correction and other requests depend on local law. We assess each request against applicable requirements and explain any limits through the privacy support route.