Reference

Open berkaslot Privacy Policy Details

We keep this policy plain so you can see what data we collect, why we use it, and when we share it for payment checks or support.

Account dataDevice logsCookie useLocal law
berkaslot Open berkaslot Privacy Policy Details
HELP CHANNELS

Browse privacy support channels

When you need a privacy change, we keep the path simple: start from live chat in the account area, send an email, or submit the contact form after login.

Live chat Open chat from your account page for access, correction, or removal requests. Our team answers every day, with faster replies during WIB working hours and clear next steps after the first check.
Email Send a written request when you want a copy of stored details or a question about retention. We reply in the order received and keep the thread with your account record.
Contact form Use the form if chat is unavailable. Add your registered name, phone number, and the last DANA, OVO, GoPay, or QRIS reference so we can match the right file.
CONTROL POINTS

Switch through our data handling

We treat privacy as account control, not fine print. That means we log only the data needed for login checks, payment matching, and support, then limit access to staff who need it.

Account data

We store your name, phone number, and wallet label so we can verify ownership and answer account requests. Those fields stay tied to your profile, not to public pages or other people.

Device logs

Device model, browser, IP address, and session time help us detect unusual access and keep your login stable when you move from mobile to desktop. We do not use those logs for extra profiling.

Cookies

Cookies remember login state, language choice, and basic safety checks. If you clear them in your browser, the next visit may ask you to log in again and confirm a fresh session.

Retention

Some records stay after closure for settlement, dispute handling, fraud checks, or legal duties under local law. Other routine data is removed sooner once it is no longer needed.

Your requests

You can ask to read, correct, or remove your data where local law permits. We verify the request against your account before acting, so changes reach the right file.

Security steps

We keep access to a small support group, use encrypted sessions on login pages, and ask for a fresh check when your phone number or wallet details change. This lowers the chance of account misuse.

Browse common privacy questions

These are the questions we hear most when you want to know how your data is handled. Each answer stays close to account use, payment matching, cookie control, and support requests, so you can decide what to do next without guessing.

We collect the name, phone number, device details, login logs, and the DANA, OVO, GoPay, or QRIS reference used to match your account. We use that data to run the account and answer requests under local law.

We use cookies to keep you signed in, remember language choice, and spot unusual session changes when you switch between phone and desktop. You can clear them in browser settings, but some parts may ask for a new login.

Yes. Send the request through live chat, email, or the form in your account area, and we will verify it against your record before changing anything. Extra checks may apply if the detail affects security or payment matching.

We keep some records only as long as needed for account handling and support, while logs tied to settlement, dispute handling, or legal duties can stay longer. When that period ends, we remove or anonymise what remains.

Only staff who need it for support, security, or account checks can access it, and payment partners may see limited details needed to confirm DANA, OVO, GoPay, or QRIS activity. We do not sell your data.

Contact us from the logged-in account, and we will confirm your identity before closing access and starting the retention process that applies to your record. Some logs may stay for legal duties after closure.