Reference

Privacy Policy for Your Account

tiger189slot keeps your account, wallet, device, and cookie data inside one clear Privacy Policy, so you know what we collect before you open the lobby.

Account data scopeDANA and QRIS contextCookie choicesWIB support hours
tiger189slot Privacy Policy for Your Account
PRIVACY HELP

Contact Paths for Privacy Requests

A privacy request should reach the team that can act on it, not sit in a general inbox.

Live chat Open live chat from the lobby footer between 10:00 and 02:00 WIB. Tell us you have a Privacy Policy question, then confirm your registered email before we discuss account or wallet data.
WhatsApp support Message our WhatsApp channel from your account help panel when you need to show a device or payment screenshot. Blur any balance figure not linked to the privacy request before sending it.
Email privacy desk Send written requests to [email protected] with your username, registered phone, and the data you want checked. We answer privacy emails in queue order during WIB service hours.
DATA HANDLING

How We Handle Account Privacy

Account privacy is handled through repeatable steps, not guesswork. Our team checks who is asking, what account record is involved, and whether a payment, cookie, login, or support record is needed to…

Account data

We collect details you submit during account setup, such as username, phone, email, and verification status. These fields help us confirm ownership before changing private records or answering account-specific privacy questions.

Wallet references

DANA, OVO, GoPay, and QRIS records are stored as transaction references, not as open wallet access. We use them to match deposit and withdrawal checks with the account that requested them.

Device signals

We may log browser type, IP range, device model, and login time. These signals help us flag unusual access, such as a new handset signing in after your usual Android session.

Cookie settings

Cookies keep your session active, remember language choices, and help us see if pages load correctly. You can clear them from your browser settings, though you may need to sign in again.

Retention checks

We keep records only for account operation, security checks, payment matching, support history, and legal duties that apply. When a record is no longer needed, we remove it or separate it from your profile.

Change requests

To update or correct data, open Account > Profile or contact privacy support. For safety, we may ask for email confirmation before changing phone, wallet name, or other sensitive account fields.

Privacy Policy Questions You May Ask

This FAQ focuses only on privacy: what we collect, why we use it, how long we keep it, and how you can ask us to correct or remove account data. If your question involves a wallet check, include the payment rail name and request date so we can find the right record faster.

We collect the details you enter, such as username, phone, email, password status, and account verification progress. We also record login signals and support history when needed to protect your account.

No. We store payment references linked to account activity, not direct access to your wallet. Those references help us match deposits, withdrawals, and privacy requests with the correct account record.

Start with Account > Profile for basic details, then contact privacy support if a locked field needs correction. We may ask you to confirm your registered email before changing sensitive data.

Device and login data helps us detect unusual access, protect sessions, and answer account-security questions. For example, Login History can show whether a new phone accessed your account recently.

We keep records for as long as they are needed for account operation, wallet matching, support history, security checks, and legal duties. When the purpose ends, we remove or separate the data.

Yes, you can send a deletion request to [email protected]. Some records may need to stay for payment matching, dispute handling, security checks, or legal duties where service is permitted.

Only staff handling account, privacy, wallet, or security tasks can access support messages when needed. We use those messages to answer your request, verify context, and keep a record of the response.