Reference

Privacy Policy for Your solana4d Account

solana4d’s Privacy Policy explains what we collect when you create an account, verify your phone, browse Dragon Tiger or use DANA and QRIS.

Account dataWallet activityCookie choicesAccess requests
solana4d Privacy Policy for Your solana4d Account
PRIVACY CONTACTS

Get Privacy Help Through Your Account

A clear contact route makes a Privacy Policy request easier to resolve. Sign in first where possible, then use our support path and include the phone number linked to your account, the relevant wallet rail and the date of the event. We use those details to locate the right record without asking for your full payment credentials. If you are in Denpasar or elsewhere in Indonesia, the same account route applies where local law permits.

Team online

Account access

Use the account support path for questions about phone verification, sign-in records or a request to correct the personal data attached to your solana4d account.

Wallet records

For DANA, OVO, GoPay or QRIS concerns, share the payment rail and receipt reference only. We can check the stored status without requesting your wallet PIN.

Privacy requests

Ask us to explain a data use, amend an inaccurate detail or discuss removal of eligible records through the same support contact route.

DATA CARE DETAILS

What We Protect Across Your Account

We keep this policy practical by tying each data point to an account task. Phone verification supports account access, device records help us spot unusual sessions and payment references let us trace…

Account records

We use your phone number, verification result and account identifiers to connect you with the correct sign-in record and to handle access requests without mixing accounts.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match status and receipts. We do not need your wallet PIN for that check.

Device signals

Browser type, device details and session timing can help us identify unusual access. On mobile, these signals relate to the browser path from login to the lobby.

Cookie choices

Cookies can keep a session open or remember selected settings. You can adjust cookie controls in your browser, though disabling some may affect account access.

Retention periods

We retain records for the period needed to provide support, investigate a payment status or meet legal duties. Ask through support for the reason a record remains.

Your requests

You may ask for access, correction or removal of eligible data. We may verify your account first so a request cannot be made against another person’s records.

Privacy Policy Answers Before Account Access

These Privacy Policy answers cover the account and wallet questions we expect before you open access. If your case involves a particular receipt, device session or phone verification step, send those details through our support route so we can respond to the record involved.

It covers account creation, phone verification, device activity, cookies, wallet references and support records connected with your access to casino, sports and payment pages.

When you use DANA, OVO, GoPay or QRIS, we need a route and receipt reference to match payment status. We do not require your wallet PIN for that check.

We may collect your phone number, verification result, account identifier, device details and session records. These help us confirm access, detect unusual sign-ins and answer support requests.

Yes. Use the account support path, identify the phone number linked to your account and state whether you want access, correction or removal of eligible records.

Cookies may keep your session active or remember settings in your browser. You can change browser controls, but disabling some cookies may interrupt the login path.

We keep records for support, security and legal duties for as long as needed for those purposes. You can ask support why a particular record is still retained.

Yes. Sign in where possible and use the account support route with the relevant wallet rail, receipt reference or device detail. Access depends on local law and account verification.