Reference

satria128 Privacy Policy for Your Account

The satria128 Privacy Policy explains what account, device and wallet details we use when you open an account, verify your phone and enter the lobby.

Account clarityWallet recordsPrivacy requestsIndonesia access
satria128 satria128 Privacy Policy for Your Account
PRIVACY HELP ROUTES

Get Privacy Help Beside Account Status

A clear contact path matters when you want to ask about personal data, a device record or a wallet receipt. We keep privacy support connected to the account and cashier areas, so you can give the relevant account step instead of explaining the entire issue. Before sending a request, keep your registered phone detail and payment reference ready; never send a password or wallet PIN.

Team online

Account privacy request

Use the support route inside your account to ask what personal details are linked to your phone verification. We can direct the request to the correct privacy handling path.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, contact support from the cashier path and include the receipt reference only. We will check the account-status connection.

Device access concern

When a mobile or desktop session shows an unexpected sign-in, tell us through account support. We can review the session detail and explain the next account-security step.

HOW WE HANDLE DETAILS

Protect Account Data From Login To Lobby

The Privacy Policy gives you a direct view of how we handle details from account creation through the lobby.

Account details

We use the contact details you provide to create your account, complete phone verification and respond to account requests. The Privacy Policy explains which details support access and which are optional.

Wallet matching

Payment references help us connect a DANA, OVO, GoPay, QRIS, bank transfer or virtual account action with the correct account. We describe this matching purpose without requesting your wallet PIN.

Cookie choices

Cookies can keep a selected language, sign-in state or page setting available during your visit. Our Privacy Policy explains their purpose and how a browser setting can affect your session.

Device signals

A mobile browser and a desktop browser can create different session details. We use limited device signals to help identify access problems and investigate unusual account activity.

Retention questions

Records are kept only as described for account operation, support, security checks or legal needs. You can ask which category applies when requesting clarification about a stored detail.

Change requests

To request correction or removal of eligible data, contact us through account support with the detail in question. We verify ownership before changing an account record.

Find Answers Before Opening Your Account

These Privacy Policy answers cover the account steps you are most likely to check before opening an account. We keep the wording tied to real actions: phone verification, mobile sign-in, payment references and requests sent through support. If your question concerns eligibility, access depends on local law and is available where local law permits.

It covers account details, phone verification, device signals, cookies, payment references, support records, retention and requests to correct or remove eligible personal data.

Phone verification helps connect account access to the contact detail you provide. The Privacy Policy explains how that result is used for account security and support handling.

Yes. It explains that DANA and QRIS references may be used to match a payment action with your account, while your wallet PIN and unrelated credentials are not requested.

OVO and GoPay transaction references can support wallet-status checks and receipt matching. The policy explains the purpose, account connection and request path for questions about those records.

You can send a correction request through account support. We first verify account ownership, identify the record involved and then explain whether the requested change is eligible.

Contact support from the affected account and mention the mobile sign-in or session detail. Do not send a password or wallet PIN; we will explain the relevant privacy path.

Open the privacy or support path connected to your account and submit your question with the registered contact detail. Availability depends on local law and applies where local law permits.