Reference

Open satset 138 Privacy Policy Before Access

satset 138 Privacy Policy shows what we collect when you open an account, connect DANA, OVO, GoPay or QRIS, and move between the lobby and your wallet.

Clear data purposesWallet activity contextDevice access controlsContact for changes
satset 138 Open satset 138 Privacy Policy Before Access
CONTACT ROUTES

Browse Privacy Help From Your Account

If a Privacy Policy question affects your login or wallet status, start from the support path attached to your account so we can match the request…

Account request Use the account support route when you want a copy of the personal details…
Wallet question For a DANA, OVO, GoPay or QRIS record, send the payment reference and approximate…
Access concern When a mobile browser blocks a policy page or your account session stalls, tell…
DATA CONTROL

Switch Through Your Privacy Choices

Privacy controls work best when each request names the account step or record involved.

Data handling

We use account details to create access, complete phone verification and respond to support requests.

Cookie choices

Cookies and similar browser storage can keep a session active, remember basic page settings and help us understand whether the…

Account security

A phone verification step helps us distinguish an account owner from an unrelated request.

Retention timing

We keep records only for the period needed for the stated account, payment, security or legal purpose, subject to local…

Correction request

If your phone detail, contact record or account attribute is wrong, contact us with the field that needs correction.

Privacy contact

For access, correction, deletion or cookie questions, use the support route inside your account and identify the request clearly.

Check Privacy Policy Answers Before Joining

These Privacy Policy answers address the searches we hear most often from people considering an account in Indonesia. Each answer stays focused on personal data, cookies, wallet references, account access and the request process, so you can understand the practical effect before you open an account where local law permits.

The satset 138 Privacy Policy covers account details, phone verification, wallet and bank references, device signals, cookies, support records and retention. It explains why we use each category, how we protect access, and how you can request access, correction or removal where local law permits.

Yes. Our Privacy Policy explains that DANA and QRIS activity can create a payment reference, amount, status and timing record for cashier reconciliation. We use those fields to locate a transaction, but you should not send a wallet PIN, password or one-time security code.

Open the account support route and ask for an access request under the Privacy Policy. Provide your registered phone number and a short description of the records you need. We may complete phone verification before discussing account-specific data or sending a response.

You can request a correction through account support and identify the exact field that is wrong. We may verify ownership before changing it. If the detail is tied to a pending wallet or bank transfer record, we will explain any limit on editing that record.

The Privacy Policy covers cookies and browser storage used for session continuity, basic settings and page operation checks. You can clear or restrict them in your browser. Doing so may sign you out and require another phone verification step when you return.

We retain payment references for the period needed for account support, reconciliation, security or applicable legal duties. The exact period can depend on the record and local requirements. You can ask support why a DANA, QRIS or bank reference remains stored.

Send a deletion request through the support route inside your account and state which data category you want removed. We will explain the next step and any record that must remain for a pending payment, security matter or legal requirement where local law permits.