Reference

pamanslot Privacy Policy For Your Account

pamanslot Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and move through the Live Casino lobby.

Account dataWallet recordsCookie choicesPrivacy requests
pamanslot pamanslot Privacy Policy For Your Account
PRIVACY HELP DESK

Where To Send A Privacy Request

A clear contact route helps you handle a data question without repeating your account story.

Account contact Use the support contact inside your account and identify the exact Privacy Policy request. We match your phone or email record first, so another person cannot receive details about your account.
Payment query For DANA, OVO, GoPay or QRIS records, include the transaction reference and date rather than sending a wallet password. We use that narrow detail to locate the relevant payment entry.
Access problem If sign-in blocks your privacy request, explain the device path and account step that stopped you. We can route the matter for account checking without asking you to post personal data publicly.
DATA CONTROL POINTS

What Our Privacy Process Covers

Privacy is handled through practical account controls rather than broad promises. We limit each request to the record you identify, check the account before making changes, and explain when a legal or…

Collection

We collect details you provide during account creation, including contact data and phone verification status. We also receive payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Cookies

Cookies keep your sign-in session and selected settings available as you move between account pages and Live Casino. You can manage browser cookie controls, though turning them off may interrupt account access.

Device signals

Browser and device signals help us identify unusual sign-in patterns and protect account records. We use these signals for access checks, not to infer unrelated personal details from your use of Fishing God.

Account security

Before we reveal or change personal records, we may compare your request with the phone or email attached to your account. Never send a password or wallet PIN through a support message.

Retention

We keep account, payment and support records only as long as needed for the stated service, dispute handling, security checks or legal duties. When retention ends, records are removed or separated from direct account use.

Change requests

You can ask us to correct inaccurate details, provide eligible account data or remove data that no longer needs to remain. We confirm your identity and explain any record that cannot be changed.

Privacy Policy Answers For pamanslot

These Privacy Policy answers focus on the account, payment and device questions you may search before opening access. If your situation is not listed, send a request through the account contact route and include only the details needed to identify your record.

It covers account details, phone verification, payment references, cookies, device signals, security checks, retention and requests to access, correct or remove eligible personal data.

Phone verification connects the account to the contact detail you supplied and helps us check identity before account access or a privacy change. Access depends on local law.

Yes. We may retain the payment rail, reference, date and status needed to reconcile DANA or QRIS activity. We do not need your wallet PIN for a privacy request.

You can request eligible account data through the support contact in your account area. We verify the linked phone or email first, then explain the records we can provide.

Send a correction request through the account support path, name the inaccurate field and provide the updated detail. We may ask for an account check before applying the change.

We retain payment and account records for the period needed for security, dispute handling, service administration or legal duties. After that need ends, we remove or separate them.

Yes. Your browser or Mobile App device controls may allow cookie changes. Some session functions can stop working when cookies are disabled, so review the setting before requesting account access.