Reference

sat set 138 Privacy Policy

sat set 138 explains how we collect, use, store and protect details connected with your account, wallet activity and lobby access.

Clear data purposesCookie choicesAccount access pathLocal wallet context
sat set 138 sat set 138 Privacy Policy
CONTACT ROUTES

Ask About Privacy Near Account Help

A privacy question should not require you to search through the whole site. We place account help near the cashier path so you can raise a data request while checking a receipt, wallet status or sign-in issue. Include the phone number linked to your account and a short description of the request. We may ask for an account step to confirm that the request comes from you.

Team online

Account privacy request

Use the account help route to ask what personal details are connected with your sat set 138 profile. We can explain the purpose of a phone verification record, the status of a request and the next account step needed to confirm your identity.

Wallet record question

If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, refer to the payment receipt and its date when contacting us. We use those details to locate the matching account record without asking you to send a wallet password or secret code.

Cookie and device help

When a mobile browser keeps an old session or cookie, tell us the device path you used, such as Android browser or desktop browser. We can explain the relevant cookie choice and account access step without requesting the contents of your private device.

DATA PRACTICE

Explore How We Handle Your Privacy

Privacy work is tied to practical account events, not a vague promise. We separate sign-in details, verification records, wallet references and device signals by their operational purpose.

Account details

We collect the details needed to create and maintain your account, such as a phone number and verification result. The account path uses these records to connect your sign-in with the correct profile, while unrelated details are not needed for this step.

Wallet references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be stored with transaction status. We use that connection to match a receipt, investigate a duplicate entry and separate your payment record from another account.

Device signals

Your browser and device can provide technical signals such as session data, language settings and security events. These signals help us recognise an interrupted login on mobile or desktop without reading private files stored on your device.

Cookie choices

Cookies can keep an active session, remember selected settings and help us understand whether a page loads correctly. You can adjust cookie controls in your browser; changing them may require another login before the lobby or account page opens.

Security checks

Before changing phone details, correcting wallet status or releasing account records, we may compare your request with the account step already on file. This reduces the chance that another person changes your profile using only a copied receipt.

Retention requests

To ask for access, correction or removal, contact us through the account help route and describe the record involved. We assess the request against the purpose, account status and applicable requirements, then explain any part that must remain stored.

Browse Privacy Policy Answers

These answers focus on the questions we expect you to ask before opening an account with sat set 138. They cover account records, Indonesian wallet references, cookies, device access and requests to see or change stored details. If your situation is different, use the privacy route beside account help and include enough detail for us to locate the correct record.

It covers personal details supplied during account creation, phone verification records, wallet and transaction references, device signals, cookies, support requests and retention. It also explains how we use those records for account access, security, payment matching and handling requests connected with your profile.

We use your phone number to create the correct account profile, support sign-in and complete a clear verification step before account access. If you ask to change that number, we may request an account check so the change is not made from an unauthorised request.

Yes. The policy covers references linked to DANA, OVO, GoPay and QRIS, including payment status, receipt details and the account connection used for matching. It does not ask you to share a wallet password or secret code when you request help.

Contact us through the account help route beside the cashier path and state that you want access to your stored account records. Include your account phone number and the type of record requested. We may verify your identity before preparing the response.

You can request a correction to an account detail, phone record or payment reference through account help. Tell us what appears wrong and provide the matching receipt or account step where relevant. We check the request before changing the stored record.

Cookies can keep your session and remember selected settings on a mobile or desktop browser. If you clear or block them, you may need to sign in again and some account pages may not retain your choices. Browser controls let you adjust cookie handling.

The policy is written for Indonesian account access and local wallet references, but eligibility and access depend on local law. Where local law permits, you can use the stated account and privacy routes. Contact us if a location-specific rule affects your request or access.