Reference

samson88 Privacy Policy for Indonesia

The samson88 Privacy Policy explains how we use the details connected with your account, device and wallet activity.

Account clarityWallet recordsCookie choicesRequest access
samson88 samson88 Privacy Policy for Indonesia
HELP WITH PRIVACY

Where to Ask About Your Privacy Policy

A clear contact route helps when you want to understand a record or change an account detail. Use the support route connected to your samson88 account and describe the Privacy Policy request in plain English, such as access, correction, deletion or cookie questions. Include the account identifier and the relevant wallet or device detail only when needed; do not send a password or full payment credentials. We may ask for an account step or phone check before discussing private records, so a request reaches the correct account.

Team online

Account request

For a copy of account data or a correction, contact us through the account support path after signing in. We use the account step and phone verification record to distinguish your request from an attempt to access another person’s profile.

Wallet question

If a DANA, OVO, GoPay or QRIS receipt appears incorrectly, send the transaction reference through support rather than sharing a wallet password. We compare the reference with the stored payment status and explain which record can be corrected.

Access concern

When a Privacy Policy request follows an unusual login or device change, we may pause disclosure until account security checks finish. This protects your record while we confirm the request through the account path and phone detail already held.

DATA HANDLING

What We Keep, Protect and Change

Privacy Policy choices are easier to use when each data purpose is visible. We separate account, payment, device and cookie records so our teams can answer a focused request instead of treating…

Account data

Your account record can include the details needed to open access, confirm your phone and maintain the profile you use for the casino lobby and sports pages. We use those details for account administration, not as a reason to request unrelated personal data.

Payment references

We keep transaction references and status results for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These references help match a receipt to your account without requiring us to store your wallet password or banking login.

Device signals

The mobile path may create technical signals such as browser type, device settings and login time. We use them to maintain sessions, detect unusual access and help explain why a phone verification step appeared before entry.

Cookies

Cookies can remember a session, preserve a selected setting and help us understand whether a page opens correctly. You can manage cookie controls in your browser, although disabling some cookies may interrupt account access or return you to the login step.

Retention

Retention depends on the purpose of a record. Account and payment entries may remain while needed for account service, receipt checks, disputes or legal duties. When the reason ends, we delete, aggregate or de-identify the record under our retention process.

Your requests

You can ask for access, correction, deletion or an explanation of processing where local law permits. Send the request through account support, identify the relevant profile and avoid passwords; we may verify your phone before releasing or changing private data.

Privacy Policy Questions About samson88

These Privacy Policy answers focus on the account records and access questions you are most likely to raise before opening or using a samson88 profile. They explain how payment references, cookies, device details and phone verification fit together. If your situation is different, use the account support route and include the smallest amount of detail needed to locate the record.

It covers account details, phone verification, device and browser signals, cookie activity, support requests and payment references. The policy explains why we use each category, how it supports account access or receipt checks, how retention works and how you can request access or correction where local law permits.

Yes. We may retain a wallet or QRIS transaction reference, amount status and related account match so we can check whether a receipt was processed. We do not need your wallet password or banking login for that check, and you should not send either through support.

Phone verification helps us connect an access request with the correct account and reduce the chance of another person entering your profile. It can also support a Privacy Policy request when you ask to see, correct or remove personal data associated with that account.

Where local law permits, you can request access to the personal data we hold about your account. Use the account support path, identify your profile and describe the request. We may verify your phone or ask for another account step before sending records to the approved contact route.

Send the affected DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference through account support. Tell us what appears wrong and avoid sharing passwords. We compare the reference with the stored status, correct an inaccurate record where appropriate and explain the result.

We keep each category only while it supports its stated purpose, such as account service, security checks, receipt matching, dispute handling or a legal duty. Device signals and payment references can therefore have different periods. You may ask support what applies to a particular record.

You can manage cookies through your browser controls. Session cookies may be needed to keep you signed in or move from phone verification to the lobby, while other cookies support page settings or technical checks. Turning them off can return you to login or limit some account functions.