Reference

ajo98 Privacy Policy In Plain English

The ajo98 Privacy Policy explains what we collect, why we use it and how you can ask us to change or remove personal data.

Account clarityWallet contextDevice controlsContact route
ajo98 ajo98 Privacy Policy In Plain English
PRIVACY CONTACT

Three Ways To Ask About Your Data

A clear contact path helps you act on this Privacy Policy without searching through the lobby. Send a privacy request through the support route connected to your ajo98 account, include the email or phone detail used for access, and describe the change you need. We may ask for an account step or identity check before discussing personal data. That protects your records when a login or wallet status needs attention.

Team online

Access request

Ask us for the personal data linked to your ajo98 account. Include your registered phone detail so we can locate the correct record before sharing account, device or payment-context data.

Change request

Tell us which account detail is inaccurate, such as a phone number or contact address. We will check the request against your account path before changing the stored record.

Wallet concern

For a DANA, OVO, GoPay, QRIS or bank-reference question, attach the relevant receipt or status detail without sending a password. We use it to trace the payment context.

DATA HANDLING

How ajo98 Applies This Privacy Policy

Privacy controls work best when they follow the real account journey. We limit internal access to data needed for account operations, security checks, support replies and payment matching.

Account records

We store the details you provide during account opening and phone verification so we can identify your account and respond to a Privacy Policy request. We do not need unrelated profile details.

Device signals

Browser, device and login timestamps can help us detect unusual access. These signals support account security when you move from the mobile login screen to the lobby or return on desktop.

Cookie choices

Cookies may remember a session setting or help us understand whether a page request is functioning. You can ask support how cookie-related records are handled for your account.

Payment matching

A DANA, OVO, GoPay or QRIS reference can be checked against your account when a payment status needs clarification. We use the reference for matching and support, not unrelated profiling.

Retention period

We keep personal data only while it supports account security, a support request, payment reconciliation or a legal duty. When the purpose ends, records are removed or handled under applicable retention rules.

Policy changes

When this Privacy Policy changes, we update the page so you can see the current handling rules. Contact us through your account path if you need the change explained or want to request an update.

Privacy Policy Questions For ajo98

These Privacy Policy answers address the account, device and payment questions we expect before registration. They also explain how to reach us when you need a correction or want to understand a record connected with your Indonesia access path. Eligibility depends on local law, and requests are handled only after we can identify the relevant account.

It covers account details, phone verification, login and device signals, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, virtual account or bank transfer steps. It explains why we use each category and how you can request access or correction.

Use the support route connected to your ajo98 account and state that you are making a Privacy Policy data request. Include your registered phone or contact detail. We verify the account before sharing records so another person cannot obtain your account or wallet context.

We may store a payment reference, status and related account context when you use DANA or QRIS. The same principle applies to OVO, GoPay, virtual account and bank transfer steps. We use those details to match a transaction or answer a support question.

Device details and login timestamps help us recognise the account access pattern and investigate unusual sign-ins. They can also support a request involving a mobile login or desktop session. We use these signals for security and service operation under this Privacy Policy.

Yes, you can ask us to correct an inaccurate phone number, contact detail or account record through the account support path. Describe the exact field that needs changing. We may request phone verification or another account check before applying the amendment.

We keep records while they are needed for account access, security review, support handling, payment matching or a legal requirement. After that purpose ends, we remove or restrict the record under applicable retention rules. The period can depend on local law.

You may submit a deletion request through the support route linked to your account. We will confirm your identity and assess whether any record must remain for security, payment reconciliation or a legal duty. Where local law permits, data no longer needed will be removed.