Reference

Open your account with clear privacy terms

pekanslot keeps your account data, DANA, OVO, GoPay and QRIS records, device checks, and lobby activity tied to this Privacy Policy so you know what we collect before…

DANA data useOVO receipt recordsGoPay wallet checksQRIS payment logsAccount privacy requests
pekanslot Open your account with clear privacy terms
CONTACT PATHS

Check privacy help before you join

Privacy questions should reach a person who can read your account record, not a script. Our support desk handles data access, correction, deletion, cookie, and payment-record questions through live chat, email, and…

Live chat Use live chat from the account screen for urgent privacy questions. We answer daily from 10:00 to 02:00 WIB and may ask for your username, registered phone, and recent DANA or QRIS reference.
Email desk Send longer privacy requests by email when you need a written reply. Put your account name, contact number, and the exact change you want, such as correcting an OVO receipt or updating email access.
Account message The message box inside your account is useful when you are already logged in. We can link the request to your session, device signal, and wallet history without asking you to repeat every detail.
DATA HANDLING

Browse how we handle your data

Your account record is used to run the service you asked for, not to bury you in vague privacy wording.

Account setup

During account creation we ask for details needed to identify you, contact you, and secure access. If a field is not needed for that step, we aim not to collect it.

Payment records

DANA, OVO, GoPay, and QRIS entries are stored with reference numbers and timestamps so deposits and withdrawals can be matched. We use those records for wallet checks and dispute handling.

Device checks

When you sign in from mobile browser, tablet, or computer, we read basic device and session signals. That helps us flag unusual access and protect your balance from account takeover attempts.

Cookie control

Cookies keep your session active, remember display choices, and help us see if pages load correctly. You can clear them through your browser settings, then sign in again when needed.

Retention checks

We keep account and wallet records only as long as needed for service, dispute, security, and legal reasons. When retention is no longer required, we remove or separate data from active tools.

Request handling

Ask us to access, correct, or delete eligible data through chat, email, or the account message box. We verify control of the account before changing privacy-related records.

Start with common privacy questions

Your privacy questions usually come up at account creation, wallet checks, login changes, and support chats. These answers explain how we handle the data tied to your account, payment references, device sessions, and cookie choices. If your case involves a specific DANA, OVO, GoPay, or QRIS record, contact us with the reference number so we can find it faster.

We collect the details needed to create and secure your account, such as username, contact number, email if provided, login records, device signals, and payment references linked to DANA, OVO, GoPay, or QRIS.

Payment references help us match wallet activity to the correct account. If a DANA transfer or QRIS scan needs checking, the timestamp, amount record, and reference let support trace the entry.

Yes. Contact live chat, email, or the account message box and tell us what needs changing. We verify account control first, then update eligible details such as phone number or email access.

Cookies keep your login session active, remember display settings, and help pages load as expected. You can clear cookies in your mobile browser settings, then sign in again with your account details.

Only the team members needed to answer your request can view the related account record. For example, a wallet case may involve payment support, while a login case may involve account security.

We keep data while it is needed for account service, wallet checks, dispute handling, security review, and legal duties. When those reasons end, we remove data or separate it from active systems.

No. Access and eligibility depend on local law and are available only where local law permits. If a privacy request relates to access status, we still handle the request through our normal contact paths.