Reference

Privacy Policy For Your Account

The ajaib 88 Privacy Policy explains how we collect, use and protect the account, device and wallet details connected with your access.

Account dataCookie choicesWallet recordsSecurity requests
ajaib 88 Privacy Policy For Your Account
REQUEST HELP

Get Policy Help Near Your Account

A clear contact route matters when you want to understand a Privacy Policy request, correct an account detail or ask why a wallet reference appears in a record.

Account requests Ask us to correct a phone number, sign-in detail or account identifier through the account support path. Include only the details needed to locate your record, and we may ask for a verification step before changing data connected with account access.
Wallet records For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, share the relevant receipt reference and approximate transaction date. We use those details to locate the record and avoid asking you to repeat wallet data that is not needed.
Access questions If you cannot reach a policy page or need help understanding a data request, contact us through the support route shown after sign-in. Tell us whether the issue concerns cookies, account access, retention or a correction request so we can route it clearly.
DATA PRACTICES

What You Can Control In Privacy Settings

We keep the Privacy Policy practical by linking each data practice to a visible account action. Your phone verification supports account security, cookie controls shape browser storage, and a payment reference helps…

Data we collect

We may collect your account contact details, phone verification result, sign-in events, device type, browser settings and support messages. When you use DANA, OVO, GoPay or QRIS, we may retain a payment reference and status rather than treating the wallet name as a complete account record.

Cookie controls

Cookies and similar browser storage can remember a sign-in state, preserve a selected setting or help us understand whether a policy page loads correctly. You can adjust browser controls, although removing required storage may interrupt sign-in or make a saved preference unavailable.

Account security

Phone verification, sign-in records and device signals help us identify unusual access before an account change is completed. Keep your sign-in details private, and contact support if a device path or account action does not match what you initiated.

Retention periods

We keep account, support and payment-reference data only for the period needed for account operation, security checks, dispute handling or a legal requirement. When a record is no longer needed, we delete it or remove identifying links where our process permits.

Access and changes

You can ask what account data we hold, request a correction or ask about deletion through the support contact route. We may verify the request against your account before acting, especially when it could change phone access or expose wallet-linked records.

Limited sharing

We share data only where needed to operate a requested account process, protect access, answer a payment-status question or meet a legal obligation. A DANA receipt reference, for example, is handled for the matching support task rather than reused for an unrelated purpose.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the questions we expect you to ask before opening an account or sending a support request. We explain the account step, the data connected with local wallets and the practical route for corrections. If a rule affects access in Indonesia, the result depends on local law, and our support team can clarify which request path applies to your record.

It covers account details, phone verification, sign-in events, device data, cookies, support messages and payment references connected with your use of the site. It also explains why we use those records, how long they may remain and how you can request access, correction or deletion.

Phone verification helps connect an account request to the person controlling the registered number and supports checks before an access change. We record the verification result and related security event, not a reason to use your phone data for an unrelated purpose.

Yes. The Privacy Policy covers the payment references and status details needed to match a DANA or QRIS receipt with the correct account process. The same approach applies to OVO, GoPay, bank transfer and virtual account requests, with only the needed record used.

Use the support contact route available from your account area and state whether you want access, correction or deletion. Add the registered phone number or relevant receipt reference, but do not send extra wallet credentials. We may verify ownership before completing the request.

Cookies can keep a sign-in state, remember a selected setting or help us identify a loading problem on your browser. You can manage them through your browser controls. Blocking required cookies may affect account access, while optional choices can be changed where the setting is available.

We retain records for the period needed to operate your account, investigate security events, resolve payment-status questions or meet a legal duty. After that need ends, we delete the record or reduce its connection to you where our process and local law permit.

Access and eligibility depend on local law. If access is available where local law permits, the account flow may ask for phone verification and a security check before showing account-linked areas. Contact support if you need the policy basis for a location or access request.