Reference

soka4d Privacy Policy for Your Account

Your account details, wallet records and device choices stay at the centre of our Privacy Policy.

Account recordsWallet activityDevice choicesPolicy access

Privacy Policy for DANA and QRIS Records

soka4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect the details needed to create and protect your account, such as your contact details, verification responses, login events and wallet references. When you select DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we receive transaction status and reference data so we can

1
match an account action with its result; we do not need your wallet password. Browsing records may include the game page opened, such as Rocket Crash or Bingo, along with device type, browser data and approximate technical location. We use this material to provide account access,
2
check unusual activity, answer payment questions and meet applicable obligations. Access to our services depends on local law. You can read this Privacy Policy before opening an account and contact us if a local rule affects how your data is handled.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP CHANNELS

Where Privacy Policy Questions Go

A clear contact route helps you ask about personal data without searching through the lobby. From your account area, open the support path and describe the record, device event or wallet reference involved. Include the email or phone detail linked to your account so we can verify the request before discussing Privacy Policy matters.

Team online

Account contact

Use the support route inside your account for Privacy Policy questions, access requests or corrections. We may ask you to confirm the phone detail connected with your account before sharing personal records.

Wallet query

For DANA, OVO, GoPay or QRIS records, send the transaction reference and date through account support. We use those details to locate the relevant status without asking for your wallet password.

Device access

If a login from your phone or desktop looks unfamiliar, contact us through the same support path and mention the device. We can review account access details while keeping the request tied to your identity.

DATA PRACTICE

How We Protect Account Records

Our Privacy Policy is applied at the points where data enters, moves through and leaves your account.

Data collection

We collect account contact details, verification information, login events and payment references only when they support access, account protection, transaction matching or a stated policy purpose.

Cookie choices

Cookies and similar device storage can remember session choices and help us understand page access. You can manage browser storage, though changing it may require another login.

Account security

Before discussing personal records, we check the account detail used for access. Device and login signals can help us identify unusual entry attempts around your account.

Retention periods

We retain records only for the period needed for the purpose collected, account support, dispute handling or applicable legal duties. When no purpose remains, records are removed or separated.

Correction requests

If your name, contact detail or another account record is inaccurate, contact us through account support. Tell us what changed and we can assess the correction under this Privacy Policy.

Access requests

You can ask which personal data we hold and how it is used. We may request account verification, then respond through the contact route connected with your soka4d account.

Privacy Policy Questions About soka4d

These answers cover the searches we hear most often about account records, wallet references and device access. If your situation is different, use the account support route and include enough detail for us to locate the relevant Privacy Policy request.

It covers account details, verification data, login events, device information, cookies, game-page activity and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use the contact detail linked to your account for access checks, account messages and support verification. It helps us confirm that a Privacy Policy request comes from the right account holder.

No. We use transaction status and reference details to match an account action with DANA, OVO, GoPay or QRIS. Your wallet password remains with the relevant wallet service.

Open the support route inside your account and ask for a personal data access request. Include your linked contact detail; we may verify your identity before sending records covered by the Privacy Policy.

Yes, ask through account support and identify the detail that needs correction. We review the request against account verification records and update eligible information under the Privacy Policy.

Cookies may keep your session active and record basic page access. You can adjust browser storage settings, but removing cookies can sign you out or change how account access works.

Yes. Account access and data handling depend on local law. Where local law permits, we apply the stated requests and safeguards; a local rule may change the response or available access.

soka4d Privacy Policy for Your Account

Where Privacy Policy Questions Go

Account contact

Wallet query

Device access

How We Protect Account Records

Data collection

Cookie choices

Account security

Retention periods

Correction requests

Access requests

Privacy Policy Questions About soka4d

01 What does the soka4d Privacy Policy cover?

02 Why does soka4d need my phone or email?

03 Does the Privacy Policy store my DANA password?

04 How can I request a copy of my data?

05 Can I correct my soka4d account details?

06 How are cookies handled on my device?

07 Does local law affect this Privacy Policy?

Related Pages