Reference

Privacy Policy for Your samurai 69 Account

Our Privacy Policy explains what we collect when you open a samurai 69 account, use the mobile lobby, or check a DANA, OVO, GoPay or QRIS transaction.

Account dataWallet recordsCookie choicesPrivacy requests
samurai 69 Privacy Policy for Your samurai 69 Account
PRIVACY HELP

Where to Send a Privacy Request

A clear request helps us locate the right account record without exposing details to the wrong person.

Account help path Open account help while signed in and select the privacy subject. We use the account contact already attached to your profile to discuss a request, which reduces the chance that account data is sent to an unrelated address.
Receipt matching For a DANA, OVO, GoPay or QRIS question, provide the transaction reference and date shown in your wallet history. We use those details to find the relevant record without asking you to share a wallet password or private security code.
Access questions If you cannot reach the privacy page or account help from a phone, try the site footer after signing in on your mobile browser. Tell us your device path and the page step where access stopped; eligibility depends on local law.
DATA PRACTICES

What We Protect, Store and Change

Privacy Policy choices should be understandable at the moment you need them, so we separate account operation from optional cookie activity.

Account creation

We use the contact details and verification step you provide to create an account and confirm access. If a detail is wrong, ask us to correct it through account help rather than opening a second profile with different information.

Wallet matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are used to identify a payment status or receipt. We keep the reference needed for reconciliation, but we do not need your wallet password to answer a status question.

Device signals

We may record browser type, operating system, connection details and sign-in time when you use the mobile lobby or desktop site. These signals help us investigate unusual access and explain why a privacy request is linked to a particular account event.

Cookie choices

Cookies can remember a session and your selected site settings. You can adjust cookie controls in your browser, although removing required cookies may sign you out or prevent the Privacy Policy page from loading as expected.

Account protection

We use sign-in checks, verification records and activity review to protect account details. Keep your password private, sign out on shared devices and contact account help if a login event or contact change does not match your activity.

Retention requests

We keep information only for the period needed for account support, payment reconciliation, security checks and applicable legal duties. You may request access, correction or deletion of eligible data; some records may need to remain for a defined reason.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers cover the searches we hear most often from people considering an account or checking a wallet record. We keep each answer tied to the actual account step, device path or payment reference involved. If your situation is not listed, use account help and include enough detail for us to identify the request safely.

It covers account details, verification results, sign-in activity, device signals, cookies, wallet references and support messages. It also explains retention and your available requests. The policy applies to the data created when you use the site, subject to access rules that depend on local law.

No. We use a DANA or QRIS transaction reference, status and timing to match a payment question. We do not need your wallet password or private security code. Never include either item in account help, even when asking us to check a receipt.

Yes. Send a correction request through account help while signed in, using the contact detail attached to your account. Tell us which field is wrong and what it should say. We may use a verification step before changing contact or access data.

Use the privacy subject in account help and ask for an account data copy. Include your account email or phone number, but not your password. We may verify the request before responding, so the copy is provided to the person connected with the account.

Browser type, operating system, connection details and sign-in time help us investigate unusual access and support a mobile account path. A device signal is not used as a wallet password. If an event looks unfamiliar, contact account help and describe when it occurred.

We retain the payment reference and status for as long as needed to reconcile DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, support the account and meet applicable legal duties. You can ask why a particular record remains through the privacy contact path.

Start from the site footer or account help on your mobile browser or desktop device. State the page step that failed and the account contact linked to you. If eligibility or access is involved, it depends on local law, and we will explain the available path.