Reference

api gacor 88 Privacy Policy for Your Account

api gacor 88 Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and contact our support path.

Clear data categoriesWallet record detailsCookie choices
api gacor 88 api gacor 88 Privacy Policy for Your Account
REQUEST HELP

Get Privacy Help Near Account Support

A clear request path matters when a phone check, wallet reference or account detail needs attention. We ask you to contact our account support route with the email or phone detail linked to your account, the subject of your request and any receipt reference that helps us locate the record. Do not send a password or full payment credential. Where local law permits, we may ask for an account step that confirms you are requesting access to your own data.

Team online

Account data request

Ask us to identify the account details connected with your login, phone verification and device access. Include your linked contact detail so we can separate your request from another account without asking for a password.

Wallet record check

For DANA, OVO, GoPay or QRIS records, send the payment reference and date shown in your receipt. We use that narrow detail to locate a status entry without requesting your wallet PIN or complete banking credentials.

Cookie and access query

Tell us if a mobile browser keeps an old session, rejects a policy choice or shows the wrong account state. We can explain the relevant cookie setting and the account step needed for a safe correction.

DATA HANDLING

How We Keep Privacy Choices Practical

Privacy controls should make sense during an actual account visit, not only in legal wording.

Account details

We may use your contact detail, phone verification result and account activity to identify your account, keep sign-in working and investigate an access issue. We do not need your password in a support message, so leave it out of every request.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a transaction status to your account. We use the reference for that check and do not ask you to disclose a wallet PIN.

Cookies

Cookies can keep a session, remember a policy choice and help us understand whether a mobile browser returned to the same account path. You can adjust browser cookie settings, although refusing them may require another login step.

Device security

When you sign in from a new phone or browser, security signals may help us spot an unusual session. Keep your phone verification detail private, sign out on shared devices and contact account support if the displayed access does not match you.

Retention period

We keep each data category only as long as needed for the stated account, security, payment or legal purpose, subject to local requirements. A retention request can name the category, such as a login record or QRIS receipt reference.

Changing your data

To request correction, access or deletion where local law permits, contact us through account support with your linked phone or email and a precise description. We may verify account control before changing a record or disclosing stored details.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the questions that arise when you open an account, use an Indonesian wallet or return to the lobby on another device. We keep the wording tied to actual account steps, payment references and request handling. If your situation is not covered, use the account support route and describe the exact record or privacy choice you want us to check.

The Privacy Policy covers account and contact details, phone verification, sign-in and device activity, cookies, wallet references, support messages and retention. It explains why we use each category, how we protect account access and how you can request access, correction or deletion where local law permits.

Phone verification helps connect an account request with the person controlling the linked contact detail and helps us detect an unusual sign-in. It is also part of an account recovery check. We will not ask you to place a password or wallet PIN in a support message.

Yes. The policy covers references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. Send only the receipt reference and date when asking for a check; do not share a wallet PIN or complete banking credential.

Contact account support using the phone or email linked to your account and state that you want a data access request under the Privacy Policy. Name the category you need, such as login activity or a QRIS reference. We may verify account control before responding.

You can request a correction by describing the inaccurate account detail and providing the linked phone or email. We may ask for an account verification step before changing it. Requests and available remedies depend on local law, particularly where retention is required.

Cookies can keep your session, remember a policy choice and help the mobile browser return to the correct account path. You can change cookie settings in your browser. If cookies are refused or cleared, you may need to sign in and verify again.

Retention depends on the category and purpose: account security, payment matching, support handling and legal requirements can each require a different period. The Privacy Policy does not promise one fixed timeframe. Ask us to identify the period for a named record or data category.