Reference

Open alat99 Privacy Policy Before Account Access

Our alat99 Privacy Policy explains what we collect when you open an account, sign in on mobile, browse from Bandung, or use wallet options such as DANA and…

Account data explainedWallet records coveredCookie choices availableRequest path included
alat99 Open alat99 Privacy Policy Before Account Access
PRIVACY HELP

Contact alat99 About Your Privacy Choices

A clear contact route matters when a data request overlaps with a login or wallet issue. Start from the support link connected to your account and tell us whether you need a copy, correction, deletion request, or explanation of a record. We may ask for account details so we do not disclose private data to the wrong person.

Team online

Data request

Use the privacy contact path to ask what account details we hold, why they are used, and which records relate to your DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

Account match

When a request concerns your login, phone verification, or a device used to open the lobby, we compare the request with account details before discussing private records or making a change.

Wallet query

For a receipt or wallet-status question, include the relevant payment rail and transaction reference through the support path. We use that context to locate the record without asking you to resend unrelated personal details.

HANDLING DETAILS

Explore How We Handle Your Account Data

Our Privacy Policy is applied through ordinary account operations rather than a separate process you must learn.

Data collection

We may collect your account name, phone verification details, sign-in events, device signals, support messages, and payment references. The purpose is to create access, investigate account activity, match wallet status, and respond to your request.

Cookies

Cookies and similar browser storage can keep a session active, remember selected settings, and help us identify technical errors. You can manage browser permissions, although changing them may require another sign-in or affect parts of the account page.

Account security

Phone verification and sign-in records help us identify unusual account activity. If you move from a mobile browser to desktop, a fresh sign-in may be requested before private account or wallet details are shown.

Payment records

DANA, OVO, GoPay and QRIS references are used to match payment status with your account. Bank transfer and virtual account details may be retained for reconciliation, receipt checks, dispute handling, and required recordkeeping.

Record retention

We keep account, support, security, and payment records only for the period needed for the stated purpose, account administration, dispute handling, or legal requirements. When a record is no longer needed, our handling follows the applicable retention process.

Changes and requests

If this Privacy Policy changes, we will place the updated wording on this page and identify the effective date. You can contact us to request access, correction, deletion, or clarification, subject to identity checks and local legal requirements.

Check Privacy Policy Answers Before Joining

These Privacy Policy answers focus on the questions we expect before an account is opened or a wallet is connected. If your situation is not covered, use the privacy contact path with the smallest useful amount of detail, and we will assess the request against your account record and applicable local law.

The alat99 Privacy Policy covers account details, phone verification, sign-in events, device and browser signals, cookies, support messages, payment references, and retention. It explains why we use each category, how we protect access, and how you can request clarification or a change.

Phone verification helps us connect the right person to the right account and reduce mistaken disclosure during support. It may also be used when a new device signs in or when you ask about private records linked to DANA, OVO, GoPay, or QRIS.

Yes. The Privacy Policy covers payment references and status information connected with DANA and QRIS, as well as OVO, GoPay, bank transfer, and virtual account activity. We use these details for account matching, reconciliation, receipt checks, and support responses.

You can contact us through the privacy support path and request a correction. Include the account detail that appears wrong and the replacement wording. We may verify your identity first, then assess the request against account records, operational needs, and local legal requirements.

Cookies can keep your session active, remember browser preferences, and help us trace a technical fault. You can change cookie settings in your browser. If you clear or block them, you may need to sign in again or see reduced account-page functionality.

Retention depends on the record and its purpose. Account, security, support, and payment references may be kept for account administration, reconciliation, dispute handling, or legal requirements. When the stated need ends, the record follows our applicable deletion or retention process.

You may ask for removal of eligible personal data through the privacy contact route. We first match the request to your account and then check whether a record must remain for security, payment reconciliation, dispute handling, or legal duties. Processing depends on local law.