Reference

wawaslot Privacy Policy For Your Account

Your wawaslot Privacy Policy explains what we collect when you open an account, sign in from a phone, or check DANA and QRIS wallet status.

Account dataDevice controlsWallet recordsCookie choices

Explore Our Lobby Read FAQ

What This Privacy Policy Covers

wawaslot Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers the details you provide during account creation, including contact data used for phone verification before account access. It also covers sign-in records, device signals, cookie settings, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or a virtual

1
account. We use this material to confirm that the right account is being accessed, match a payment receipt to the correct record, investigate an unusual sign-in, and answer a request about your data. The same approach applies whether you browse from Makassar on a mobile browser
2
or use a desktop device elsewhere in Indonesia. We retain records only for operational, security, dispute, or legal needs, then remove or separate them when they are no longer needed. Access or eligibility depends on local law, and this policy does not change that requirement.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT YOUR WAY

Get Privacy Help Near Account Support

A clear contact path helps you ask about personal data without repeating your account story.

Account data request Use the signed-in support route to ask which account details we hold. We may request an account step or phone verification detail before discussing private records.

Wallet record question For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account query, include the receipt reference and date so we can trace the relevant payment record.

Access correction If a device or phone detail appears wrong, contact support from your account area and describe the change. We check ownership before altering a personal record.

DATA HANDLING PRACTICE

How We Work With Your Data

Privacy depends on practical handling, not broad promises. We separate account details from routine device signals where our operation allows, limit internal access to a need, and use account checks before discussing…

Account details

We receive details you enter during account creation and phone verification. Those fields help us identify your account and answer a data request without exposing another account’s records.

Device signals

A mobile browser or desktop session may send device and sign-in signals. We use them to spot unusual access and connect your current session with the correct account.

Cookies

Cookies can preserve a selected setting or support sign-in continuity. Your browser controls let you remove or restrict them, although some account steps may then need repeating.

Account security

Phone verification before account access helps us distinguish your sign-in from an unfamiliar attempt. We may ask for matching account details before changing private records.

Retention choices

We keep data for the operational, security, dispute, or legal reason that requires it. When that reason ends, we remove, anonymise, or separate the record where possible.

Change requests

Ask through the signed-in support route to access, correct, or request removal of your data. Include the affected account detail so we can assess the request accurately.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the practical searches you may make before opening an account or while checking a record. We explain the account step, device path, wallet reference, and contact route we use so your request can reach the right handling process.

It covers account and phone verification details, device and sign-in signals, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account.

We use phone verification before account access to connect you with the correct account and help identify unusual sign-ins. It also supports checks before we discuss or change private records.

Yes. A mobile browser can provide session and device signals used for account security and sign-in continuity. We do not treat those signals as a replacement for the account details you provide.

We use payment references, dates, and account links to match a DANA or QRIS record with the correct request. Include the receipt reference when asking support to locate or correct it.

You can ask through the signed-in support route for access or correction. We may confirm account ownership and ask which field or record you mean before preparing a response.

Retention depends on why the record exists, such as security, payment matching, support, dispute handling, or legal needs. We remove, anonymise, or separate it when that reason ends where possible.

Open the support route in your account area and state whether your request concerns access, correction, deletion, cookies, or a wallet record. Add relevant dates and references without sending unnecessary private details.

wawaslot Privacy Policy For Your Account

Get Privacy Help Near Account Support

How We Work With Your Data

Account details

Device signals

Cookies

Account security

Retention choices

Change requests

Privacy Policy Answers For Your Account

01 What does the wawaslot Privacy Policy cover?

02 Why does wawaslot need my phone verification detail?

03 Does the Privacy Policy cover mobile device data?

04 How are DANA and QRIS records handled under this policy?

05 Can I request a copy or correction of my data?

06 How long does wawaslot keep personal data?

07 How do I contact wawaslot about this Privacy Policy?

Related Pages