Reference

Privacy Policy For Your Account

The pasukan jitu Privacy Policy explains what we collect when you open an account, use the lobby, or check a wallet record, and why each detail is needed.

Account clarityWallet recordsCookie choicesRequest access
pasukan jitu Privacy Policy For Your Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact route matters when a name, phone detail, cookie setting, or wallet reference needs attention.

Account support path Use the account support path for a copy of personal details, a correction request, or a question about phone verification. Tell us which account field needs attention and we will connect the request with the relevant account record without asking you to post private details in a public message.
Cashier record check If your privacy question concerns DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, include the payment reference and approximate date. We use those details to locate the transaction record and explain what is stored for reconciliation or account assistance.
Device session help For an unfamiliar sign-in, cookie concern, or device session that remains active, contact us through the same account support route. Mention whether you used a mobile browser or desktop path, and we can focus the check on session activity rather than changing unrelated account details.
DATA PRACTICE

What We Do With Account Data

We handle personal data according to the purpose that brought it into the account flow. Phone verification supports account access checks; wallet and bank references help match cashier activity; device and cookie…

Account details

We use the details entered during account opening to create and maintain your account record. Phone verification can be used before account access, helping us distinguish an account request from an unverified attempt. If a name or contact detail is wrong, ask us to check the specific field.

Payment references

DANA, OVO, GoPay and QRIS references, along with bank transfer and virtual account details, are handled as transaction records. We use them to match cashier status and answer payment queries. The record may remain when needed for reconciliation, security checks, disputes, or legal duties.

Cookies and sessions

Cookies can keep your selected path connected and help us recognise a returning device session. They may relate to sign-in, preferences, or security checks. You can manage browser cookie settings, but switching them off may require you to repeat account steps or sign in again.

Security checks

We examine sign-in and device signals for activity that does not match the account pattern, such as an unfamiliar session or repeated access attempt. These checks are used to protect account records. If a security check interrupts you, use account support and describe the device path.

Storage periods

Retention depends on why a record exists. Account, phone verification, cashier, support, and security records may be kept for operational continuity, dispute handling, fraud prevention, or legal requirements. Ask us about a particular record type rather than assuming every field follows the same period.

Your requests

You can ask for access to your personal data, correction of an inaccurate field, clarification of its purpose, or a review of whether continued storage is needed. Send the request through account support with enough detail to locate it. We may verify ownership before responding.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and device questions you are most likely to have before opening an account. They cover the information we collect, payment references, cookies, security checks, retention, and the steps for requesting access or correction. If your situation is not listed, use the account support path and include the relevant account or cashier detail. Access depends on local law.

It covers personal details used for account opening, phone verification, sign-in, device sessions, cookies, support requests, and cashier records. It also explains why we handle DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references when they relate to account reconciliation or assistance.

Phone verification helps connect an account request with the person seeking access and supports checks when account details change. We use the verified contact detail for account-related handling, not as a reason to collect unrelated data. Ask through account support if your phone record needs correction.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity. We use those references to match cashier status and answer a specific account question. They may be retained when reconciliation, security, dispute, or legal needs apply.

Use the account support path and ask for access to your personal data. Include your account identifier and describe the records you want, such as phone verification, cookie-related details, or a cashier reference. We may verify account ownership before providing records or explaining the available response.

You can request a correction for an inaccurate account field, contact detail, or other personal record. Tell us exactly what appears wrong and what should replace it. We may ask for an account check before making a change, and the response depends on local law and the record type.

Cookies can support sign-in continuity, saved preferences, and device security checks. Browser settings let you restrict or remove them, although you may need to repeat account steps afterward. If a cookie or session behaves unexpectedly on mobile or desktop, contact account support with the device path.

There is no single period for every record. We consider the purpose of account, phone verification, cashier, support, and security data, then retain it for operational, dispute, security, or legal needs. Ask about a specific record through account support if you need a retention explanation.