Reference

pejuang slot Privacy Policy For Your Account

Our Privacy Policy shows how we collect, use and protect the details connected with your pejuang slot account, including login records, device signals and wallet status.

Account dataCookie choicesWallet recordsAccess requests
Explore Our Lobby Read FAQ
pejuang slot pejuang slot Privacy Policy For Your Account
CONTACT THE TEAM

When Policy Questions Meet Login Help

A clear contact route helps when your account record, cookie choice or wallet receipt needs attention. We keep policy support separate from game activity so you can ask about personal data without describing a table or lobby session. Include the email or phone detail attached to your account, the device you used and the issue you want checked. That gives our team enough context to locate the relevant record without asking you to send a password or wallet PIN.

Team online

Account contact form

Use the account contact form for a copy of your stored details, a correction request or a question about how phone verification data is used. We match your request to the account identifier you provide and never ask for your password or wallet PIN.

Wallet status desk

If a DANA, OVO, GoPay or QRIS receipt appears incorrectly, send the transaction reference and approximate time through the wallet status path. We can check the payment record while keeping the request focused on data accuracy and account access.

Policy request path

Choose the policy request path when you want to ask about cookies, retention, deletion or a data copy. Tell us which account detail concerns you, and we will explain the next verification step before changing or releasing records.

DATA HANDLING

How We Protect Account Data

We handle Privacy Policy requests through the same account controls used to protect login access.

Purpose-based collection

We collect account details for defined tasks such as phone verification, session protection, payment matching and policy support. If a field is not needed for that task, we do not present it as a condition of ordinary account access.

Cookie controls

Cookies can remember a session choice and help us understand whether a login request comes from the same browser. You can ask which cookie category applies to your visit and request help when a saved preference does not appear correctly.

Device protection

Our access checks may use device type, browser details and session timing to identify unusual login behaviour. These signals support account protection; they are not a substitute for your password, phone verification or careful wallet handling.

Wallet references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account record can help us match a receipt to your account. We use the reference for status checks and do not request your wallet PIN as part of a policy enquiry.

Retention choices

We keep records only for as long as their purpose, account history or applicable requirements call for them. You may ask why a record remains, whether it can be removed and which verification details are needed before we process that request.

Change requests

To correct a name, phone detail or contact record, submit a policy request with the account identifier and the change you want. We verify ownership first, then explain the result and any record that must remain for account or payment checks.

Privacy Policy Questions For Your Account

These Privacy Policy answers focus on the questions you may ask before opening an account or when a record looks unfamiliar. We describe the practical steps for data access, corrections, cookies and payment references without shifting into general lobby advice. If your question is not covered, use the policy request path and include only the account context needed for us to locate the record.

The Privacy Policy covers account details, phone verification, login and device signals, cookie preferences, payment references and support requests. It explains why we use each category, how long records may remain and how you can ask for access, correction or removal where the request can be processed.

We may collect the account contact details you submit, phone verification results, login events, device and browser signals, cookie choices and payment references. For DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, we use transaction details needed to match status with your account.

Send a request through the account contact form and include your account identifier plus the email or phone detail attached to it. We verify ownership before releasing records, and we may ask you to confirm the request from the same contact route used on your account.

Yes. Tell us which account detail is inaccurate, what the corrected value should be and why the change is needed. We check ownership before editing the record, then confirm the outcome. A payment or verification record may need to stay unchanged when it supports an earlier account event.

Cookies can keep a login session available, remember a selected preference and help identify whether a browser behaves unusually. We can explain the cookie category connected with your visit and help with a preference request. Clearing cookies may require you to complete account access steps again.

The Privacy Policy treats wallet records as transaction references used for receipt matching, status checks and account support. DANA, OVO, GoPay and QRIS details may appear in that history, as can bank transfer or virtual account references. We do not ask for your wallet PIN.

Access to the service and the handling of some requests depends on local law. Where local law permits, you can ask about stored data, cookies, retention or corrections through our policy request path. We will explain any verification step and the reason a request cannot be completed.

Related Pages

pejuang slot Indonesia nusa366 celebsroulette About Us pejuang slot Casino