Reference

satset 138 Privacy Policy for Your Account

Our Privacy Policy explains what satset 138 collects when you open an account, verify your phone, browse on mobile, or use DANA and QRIS.

Clear data purposesPhone verification recordsWallet status detailsCookie choices
satset 138 satset 138 Privacy Policy for Your Account
CONTACT PATHS

Account Help Beside Privacy Requests

A clear contact path matters when your Privacy Policy question is tied to a real account event.

Account access If phone verification blocks your account, contact account help through the path shown after login. We use the request to check identity and explain which recorded detail needs attention.
Wallet status For a DANA, OVO, GoPay or QRIS question, include the payment reference and approximate time. We check the receipt and status record without asking you to reveal a wallet password.
Data change request To correct or remove eligible account data, send the request through support with your registered phone detail. We may ask for an account step before making a privacy change.
HANDLING DETAILS

Phone Verification, Cookies and Account Security

We handle privacy as an operating process rather than a short notice hidden behind the account screen.

Data we collect

We collect account details, phone verification results, login events, device signals, cookie preferences and payment references. A Baccarat or Aviator selection may appear as activity context, not as a reason to collect unrelated personal details.

Why we use it

Account and device data help us provide access, protect sign-in, resolve wallet status questions and answer Privacy Policy requests. We use payment references to trace a transaction, not to request your wallet credentials.

Cookies on mobile

Our mobile browser path may use cookies for session continuity, security checks and saved preferences. If you clear them, you may need to verify your phone again before returning to account pages.

Account security

Phone verification is an account step before access, and login records help us investigate an unfamiliar session. Never send a wallet PIN or password when asking us to check account privacy.

Retention approach

We keep account, security and payment-status records while they serve access, dispute handling, security or legal needs. When a record is no longer required, we remove it or reduce its link to your account.

Your request route

You can ask what data we hold, request a correction, ask about deletion or raise a cookie concern through account support. We may verify the registered phone detail before changing or releasing records.

Privacy Policy Questions for Your Account

These Privacy Policy answers cover the account steps Indonesian customers ask about most often, including phone checks, cookies, payment references and data requests. We keep each answer tied to the way information is handled on satset 138, so you know what to prepare before contacting support or opening an account where local law permits.

It covers account details, phone verification, device and login records, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us connect an access or data request to the correct account. It also supports account security when a login, correction request or wallet-status enquiry needs identity checking.

Yes. We may retain a payment reference, status and related account details so we can match DANA or QRIS activity, investigate a missing receipt and answer your privacy request.

Cookies can keep a mobile browser session active, remember selected preferences and support security checks. Clearing them can remove those settings and require another phone verification step on account pages.

Yes. Contact account support with your registered phone detail and describe the copy or correction needed. We verify the request before sharing records or changing information linked to your account.

We assess account, security and payment-status records when they no longer serve access, dispute handling, security or legal needs. Eligible records are then removed or separated from direct account identification.

Yes. Access and eligibility depend on local law. We apply this policy to Indonesian account activity where local law permits, and support can explain the route available for your request.