Reference

Privacy Policy for Your Account

We use this page to explain how your account data is handled from the first login onward.

DANAOVOGoPayQRIS
pentaslot Privacy Policy for Your Account
CONTACT ROUTES

Where to Reach Us About Privacy

If you need a privacy change, reach us through chat, email, or the request form from the account area.

Live chat Use live chat from the account page or lobby footer. Send your request with the email or phone number on the account, and we will reply during the published support window.
Email Write to our support email for requests about access, correction, or removal. Include DANA, OVO, GoPay, or QRIS references and the date if your question involves a transaction record.
Request form Use the form if you cannot access chat. We may ask for a short verification step before changing stored details, especially when a request touches account safety or a device change.
ACCOUNT SAFETY

Data, Cookies, and Account Safety

We keep privacy controls close to the account, not buried in a separate flow. Cookies remember your login state, the language you picked, and whether you opened the lobby on mobile or…

Data minimization

We collect the email or phone you use, device markers, and the transaction reference only when needed to match a DANA, OVO, GoPay, or QRIS request. Extra fields stay out of the flow unless we need them to finish the task.

Session cookies

Cookies help us keep you signed in, remember your language choice, and route the lobby correctly on mobile or desktop. They do not store your payment details, and you can clear them in your browser at any time.

Device checks

A new phone, a browser reset, or a SIM change can trigger a confirmation step. We use that step to protect the account before we restore access or update contact details.

Retention rules

We keep records only as long as needed for support, audit work, or any legal duty that applies in your region. After that, we archive or remove them according to our retention schedule.

Change requests

Send corrections, access requests, or deletion requests from the account email or phone number, then tell us exactly what should change. We may verify ownership before we act.

Payment trace

If your request involves DANA, OVO, GoPay, or QRIS, add the reference number, date, or amount so we can find the right record faster and respond in the same thread.

Privacy Questions and Clear Answers

Use these answers when you want to know what we keep, how long we keep it, and how to ask for a change. If your question touches DANA, OVO, GoPay, QRIS, or a new-device login, support may ask for a short verification step before moving ahead. That keeps the account tied to the right person and helps us respond in the same channel you used to contact us.

We collect the account details you enter, device and browser signals, login history, and payment references only when needed to match a DANA, OVO, GoPay, or QRIS request. We do not ask for more than the task needs.

We keep records only for support, security checks, and any legal duty that applies in your region. When a record is no longer needed, we archive or remove it according to our retention rules.

Yes. Send the request from the account email or phone number, and tell us exactly what should change. If the request touches a payment record, add the DANA, OVO, GoPay, or QRIS reference so we can match it.

No. Cookies help us keep you signed in, remember the language you picked, and route the lobby correctly on mobile or desktop. Payment details stay in the payment record, not in the cookie itself.

A new phone can trigger a security check, especially if the device, browser, or SIM changes at the same time. We may ask you to confirm the account email or phone before restoring access.

Use live chat, email, or the request form from your account area. Include the account email, the date of the request, and any payment reference if the question is tied to DANA, OVO, GoPay, or QRIS.

No. Access depends on local law and is available only where local law permits. If a region is not eligible, we may block sign-in or keep some data handling steps disabled there.