Reference

satset138 login Privacy Policy Explained

satset138 login Privacy Policy shows what we collect, why we use it, and how you can ask us to correct or remove eligible account data.

Clear collection rulesWallet data contextAccount contact pathIndonesia access wording
satset138 login satset138 login Privacy Policy Explained
CONTACT THE TEAM

Privacy Help Beside Account Support

A privacy question should not require you to search through unrelated account screens.

Account privacy request Use the support contact shown after account access and state that your request concerns…
Wallet record question For DANA, OVO, GoPay or QRIS records, share the transaction reference and approximate date…
Access or correction If a phone, email or device detail is inaccurate, tell us which field needs…
DATA HANDLING DETAIL

What We Do With Your Privacy Choices

Privacy work is tied to practical account events, not broad statements. We separate details needed for access from records used to trace a wallet status or answer a…

Account data

We handle your account name, contact detail and phone-verification result to create and protect your profile.

Payment references

A DANA, OVO, GoPay or QRIS reference can be connected to your account when you ask about a receipt or…

Cookies and sessions

Cookies or similar browser storage may keep a login session, language setting or security signal on your device.

Device security

We may record device and connection signals around sign-in to spot unusual access, including a sudden change from a phone…

Retention periods

We retain account, support and payment-reference records for as long as needed for the stated purpose, security checks or a…

Changes and contact

You can ask about the data linked to your account, request a correction, or ask whether deletion is available where…

Privacy Policy Questions For Your Account

These answers cover the privacy searches we hear most often before account access. We keep the examples practical, including phone verification, device sessions and local wallet references, so you can decide what to share when contacting us. If your situation is different, use the account support route and mention the exact part of the Privacy Policy you want us to clarify.

It covers account details, phone verification, device and connection signals, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains your choices when access is available where local law permits.

Phone verification helps us confirm that the person requesting account access or a data change is connected to the registered account. We use the result for access protection and support matching, not as a reason to request your wallet PIN or password.

Yes. A DANA or QRIS reference may be linked to your account when you ask us to trace a receipt or status. Send the reference and date when needed, but do not send a PIN, full authentication code or unrelated wallet details.

You can contact support through the account path and ask what account data is held about you. We may request a sign-in confirmation before responding. Access, correction or deletion depends on local law and on records needed for security or legal duties.

Cookies or browser storage can remember a session setting and support security checks on your phone or computer. If you clear them, you may be signed out and asked to complete phone verification again. The Privacy Policy explains why those signals are used.

We keep each category only as long as needed for the stated account, security, support or legal purpose. A payment reference may remain while a status matter is being handled. When retention is no longer needed, we remove or separate the record.

Contact support after identifying the account field that is wrong, such as a phone or email detail. We may confirm your active session before making a change. This step protects your account from an unauthorised request and follows local privacy requirements.