Reference

Privacy Policy For Your sweetalert2 Account

Our Privacy Policy explains what we collect when you open a sweetalert2 account, use the mobile lobby, or check wallet status through DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
Explore Our Lobby Read FAQ
sweetalert2 Privacy Policy For Your sweetalert2 Account
PRIVACY HELP PATH

Get Policy Help Beside Account Support

A clear contact path matters when your account record or wallet status needs attention. We keep privacy questions separate from game requests so a correction, access request or cookie concern reaches the right handling queue. Include the phone number linked to your account and a short description of the issue, but do not send a password or full payment credential. When access is requested from Makassar or another Indonesian location, we may ask for account details needed to confirm that the request belongs to you.

Team online

Account data request

Ask us to confirm which account data we hold, why it is used and whether a particular record is still needed. We may verify the phone number connected to your account before discussing details, so another person cannot obtain your account history through a simple message.

Wallet record question

For a DANA, OVO, GoPay or QRIS receipt that appears under the wrong account, send the transaction reference and approximate date. We use that reference to locate the record without asking you to reveal a wallet PIN, password or complete bank credential.

Cookie assistance

Tell us if a cookie choice needs to be changed or if a device keeps showing an old preference. We can explain the relevant setting and the account effect, while browser controls remain available for cookies that are stored on your own phone or computer.

DATA HANDLING DETAILS

What Our Privacy Policy Covers

The practical parts of our Privacy Policy follow the account journey you take from phone verification to wallet status and mobile sign-in.

Account information

We may collect your name, phone number, account credentials, verification result and messages sent to support. We use these details to create the requested account, confirm account ownership, answer a privacy request and maintain a reliable record of changes made to your profile.

Device and sign-in data

When you sign in from a phone or desktop browser, we may record device type, browser signals, approximate location and login events. These details help us spot unusual access and protect your account; they are not a request for permission to read unrelated files on your device.

Payment matching

A wallet or bank record can include a payment reference, amount, channel and status. For DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI transfers, we use matching details to connect a receipt with the right account and investigate a status that has not updated.

Cookies and preferences

Cookies can keep a session active, remember a language or security preference and help us understand whether a page loads correctly. You can manage browser cookies on your device. Removing some cookies may require you to sign in again or repeat a preference choice.

Security and retention

We use access controls, verification steps and activity records to reduce unauthorised account access. Retention depends on the purpose of collection, account status, unresolved payment questions and legal requirements. When a record is no longer needed, we delete it or remove identifying details where appropriate.

Changes and contact

You can ask for a copy, correction or eligible deletion of your personal data through our privacy contact path. Include the account phone number and request type. We may request additional proof before acting, and we will explain any restriction that local law places on the requested change.

Privacy Policy Answers For sweetalert2

These Privacy Policy answers focus on the questions you may have before opening an account or using the Indonesia-facing lobby. We keep the wording practical: what data is collected, why a payment reference may be retained, how cookies affect a device, and what you need to include when asking us to access or change your records.

The sweetalert2 Privacy Policy covers account creation, phone verification, sign-in events, device signals, cookies, support messages and payment references. It explains the purposes for collection, security handling, retention and your available request path. Access or eligibility depends on local law and applies where local law permits.

We use your phone number to create the requested account, support phone verification and help confirm ownership when you ask about personal data. It can also help us match an account with a DANA, OVO, GoPay or QRIS status without exposing another person's account details.

Yes. The Privacy Policy includes transaction references, channel names, status and matching details for wallets, bank transfer and virtual account activity. Where relevant, records may mention DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI, but we do not need your wallet PIN.

Cookies can keep your session active, retain a selected preference and help us identify page-loading problems. Browser settings let you remove or restrict them. After removal, you may need to sign in again, repeat a preference choice or complete an account security step.

Our Privacy Policy ties retention to the reason data was collected, account status, unresolved payment questions and legal requirements. We remove or de-identify records when they are no longer needed for those purposes, subject to any period that local law requires us to keep.

Use the privacy contact path and state whether you want access, correction or eligible deletion. Include the phone number linked to your account and the record concerned. We may ask for additional proof before acting, then explain the result or any legal restriction on the request.

You can submit a deletion request through the privacy contact path. We first confirm account ownership and check whether a record must remain for an unresolved receipt, security matter or legal duty. Where local law permits, eligible data is deleted or de-identified after that check.

Related Pages

sweetalert2 Indonesia FAQ About Us Account information Live Roulette Elite