Reference

limit138 slot Privacy Policy Explained

Our Privacy Policy shows what limit138 slot collects, why we use it and how you can ask for changes before opening or using an account.

Clear data purposesWallet status contextPhone verificationRequest path
limit138 slot limit138 slot Privacy Policy Explained
PRIVACY HELP PATH

Three Ways To Ask About Your Data

A clear contact route matters when your account or wallet record needs attention. Our support area separates login help, payment-status questions and privacy requests so you can describe the right issue once.

Account access If phone verification or a sign-in record looks wrong, use the account help path and give us the affected phone number. We check the account record without asking you to share your password or a complete wallet credential.
Wallet record For a DANA, OVO, GoPay or QRIS status question, provide the payment reference and date shown in your account. This lets us compare the wallet event with the related account record before explaining the next step.
Privacy request To ask for a copy, correction or removal of eligible personal data, select the privacy request route in support. We may ask account details to confirm that the request comes from the account holder.
DATA CONTROL DETAILS

Six Practical Privacy Commitments

We keep this policy practical by linking each data use to an account action you can recognise.

Account details

We use the contact and verification details you submit to create, identify and protect your account. Phone verification can be checked when access is requested, while your password remains yours and should not be sent to support.

Device signals

A mobile browser or desktop session can provide device and session signals such as browser type, access time and security events. We use these details to recognise unusual sign-in behaviour and investigate an account access concern.

Cookie choices

Cookies and similar session tools can keep your sign-in flow and page preferences working between visits. They may also help us understand which policy page or account step was opened, and you can manage browser cookie settings.

Wallet matching

When you check DANA, OVO, GoPay or QRIS activity, we may retain a reference, amount status and timestamp connected to your account. Bank transfer and virtual account records are used to trace the relevant account step.

Retention period

We keep personal data for as long as it supports an active account, a requested service or a necessary account record. When it is no longer needed for those purposes, we assess it for deletion or restricted storage.

Change requests

You can ask us to correct eligible details, explain a data use or remove information that no longer needs to remain. We confirm your account connection first, then assess the request under the rules that apply to your location.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you are most likely to have before opening an account or checking a wallet record. We keep the examples close to the actual account flow: phone verification, mobile access, payment references and requests for changes. If an answer depends on your location, eligibility depends on local law and the policy applies where local law permits. Use the privacy request route when your question involves a specific personal record.

It covers account details, phone verification, sign-in and device signals, cookies, lobby activity and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account steps. It also explains retention, account security and how to request access or corrections.

Phone verification helps us connect an access request with the correct account and investigate sign-in problems. We use the verification record for account security and support checks, not as permission to request your password or complete wallet credentials.

Yes. When you open the lobby from a mobile browser, we may receive browser, device and session signals linked to that visit. These records help us identify unusual access and keep the account path working across login, policy pages and wallet status checks.

We may retain a payment reference, status and timestamp so a DANA or QRIS account step can be matched with the right account. We do not need your wallet password. For a status question, send the reference and date through the wallet support route.

Yes. Use the privacy request route and identify the account details you believe are inaccurate. We may confirm your phone number or another account detail before changing a record. Requests are assessed under the rules that apply where local law permits.

We retain data while it supports an active account, a support request or an account and payment record that still needs handling. We then assess whether it can be deleted or placed in restricted storage, subject to applicable local requirements.

Start with the privacy request route in our support area and include the account phone number, request type and relevant date. Keep passwords and full banking credentials out of the message. We use the supplied details to confirm the request and locate the record.