Reference

Privacy Policy For Your Account

wasiatlogin Privacy Policy explains what we collect when you create an account, verify your phone, enter the lobby, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesPhone verification
wasiatlogin Privacy Policy For Your Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact route matters when you want to know why a record exists or how long it remains stored.

Support Chat Center Open Support Chat Center from the account help path and ask about collection, access, correction or removal. We use your account identifier to locate the right record without requesting your password or wallet PIN.
Receipt and status For DANA, OVO, GoPay, QRIS or bank transfer questions, share the transaction reference and date shown in your account. We use those details to check a status without asking for your complete wallet or bank credentials.
Account access If phone verification or a device sign-in blocks your privacy request, tell us which step stopped and the device path you used. We may ask for account confirmation before discussing personal records.
HANDLING PRACTICES

How We Handle Account Data

We keep this Privacy Policy practical by linking each data category to an account task you can recognise.

Data collected

We may collect your account name, phone number, verification result, sign-in time, device details and transaction references. These fields support account access, payment matching, security checks and replies to your Privacy Policy requests.

Cookie choices

Cookies can remember a session, language setting and consent choice on your browser. You can clear or block them through browser controls, although removing session cookies may require phone verification at the next account access.

Account security

We review sign-in patterns, device changes and phone verification before discussing account data. If a request comes from an unfamiliar device, we may ask for an account step that confirms it is your record.

Wallet references

We retain references for DANA, OVO, GoPay, QRIS, virtual account and bank transfer activity rather than collecting your wallet PIN. The reference, amount status and timestamp help us trace a cashier question.

Retention period

We keep records for as long as needed for the account purpose, security checks, dispute handling or a legal duty. When a record is no longer needed, we remove it or separate it from direct account identifiers.

Change requests

You can ask us to correct inaccurate account details, explain a collection purpose or request deletion where applicable. Contact Support Chat Center with your linked phone number and the exact change you want considered.

Privacy Policy Questions Answered

These Privacy Policy answers cover the account steps you are most likely to check before opening access or contacting us. They explain phone verification, device records, cookies, wallet references and requests for changes in terms connected to wasiatlogin. If your question concerns a specific receipt or sign-in event, Support Chat Center can use the account reference to narrow the response.

It covers account registration, phone verification, sign-in and device records, cookies, lobby activity used for security, payment references, retention and requests to access, correct or remove personal data where applicable.

We use your phone number to create and confirm the account path, complete phone verification and help identify your record when you contact Support Chat Center. We do not need your wallet PIN for this process.

Yes. The Privacy Policy includes references linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use a reference, status and timestamp to reconcile an account transaction without storing wallet credentials.

Yes. Send a correction request through Support Chat Center with the phone number linked to your account, the field that is inaccurate and the replacement detail. We may confirm ownership before changing personal records.

We retain data for the account purpose, security checks, transaction questions, dispute handling or a legal duty. Once those needs end, we remove the record or separate it from direct account identifiers.

You can block or clear cookies through your browser settings and adjust available consent choices. Session cookies support account access, so refusing them may require phone verification again or prevent a session from staying open.

Yes. The way we handle access, correction or deletion requests depends on local law. Where local law permits, contact Support Chat Center with your account reference and we will explain the available next step.