Reference

Privacy Policy for Your Account Data

For members in Semarang and across Indonesia, we keep the same rules whether you open Book of Dead, Speed Blackjack, or a QRIS payment screen: we only collect…

DANAOVOGoPayQRIS

Explore Lobby Read FAQ

How We Handle Data in Indonesia

sembahslot Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This policy covers the data we collect when you open an account, sign in on Chrome for Android or Safari on iPhone, send a DANA, OVO, GoPay, or QRIS payment reference, or contact us about a record change. We use that data only to run your

1
session, confirm your identity, answer support questions, and meet the record-keeping duties that apply in the place where you access us. Any sharing stays limited to the services that help us run the account or reply to your request. If a local rule conflicts with how
2
we normally store or share data, the local rule controls and we follow it only where local law permits. We may update this page when our tools, our process, or the law changes. The version on this path is the one that applies right now, and
3
we keep earlier copies only when a legal or security reason remains.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Where to Reach Our Privacy Team

If you want to ask for access, correction, or deletion, send the request from your registered email and include your username, the device you used, and the exact record you want changed.

WhatsApp Message the number shown in your account area and send your registered email, username, and request type. We use this channel for quick checks on access, correction, and deletion requests.

Email Send formal requests to our support inbox when you want a written trail. Attach the exact change you want, and we will confirm any identity step before we act.

Live Chat Open chat from desktop, Android Chrome, or iPhone Safari if you want a same-session answer. We keep the transcript with your case so the follow-up stays tied to one request.

ACCOUNT CARE

How We Protect Your Account Data

We handle privacy in small steps so you can see what happens to your data. Account fields, cookies, support logs, and payment references are separated by purpose, and only staff who need…

Data Use

We collect only the details needed to open your account, confirm DANA, OVO, GoPay, or QRIS records, and answer support questions. If a field is not needed for those tasks, we do not ask for it.

Cookies

Cookies remember your login state, language choice, and the last page you opened. That keeps you from repeating the same step on every visit, and you can clear them in your browser settings at any time.

Security Checks

When a device looks unfamiliar, we may ask for the registered email, a one-time code, or a support confirmation before we show private account data. That extra step helps stop someone else from entering your file.

Retention

We keep support and account records only as long as needed for account history, dispute handling, fraud checks, and local law. When that period ends, we remove or mask the parts that are no longer required.

Change Requests

If you need a correction, send the request from your registered email and name the exact record you want changed. We check the request against the account file before we make any update.

Access Control

Only staff who need the data for support, payments, or security can open private records. Role-based access keeps a billing check from exposing the whole file, and every request stays tied to a ticket.

Privacy Questions We Answer Often

These are the privacy questions we answer when you open an account, send a QRIS payment, or ask for a correction. If your request touches a login device or a payment record, we may ask for the registered email and one more identity check before we reply. That keeps the process tied to your account and to local law.

We collect the details needed to open and secure your account, such as your registered email, username, device data, support messages, and payment references. We do not ask for extra fields unless the request you make needs them.

Yes, we keep payment references only for account history, support checks, and local record-keeping duties. The record is used for that purpose only and is not reused for unrelated contact.

Yes. Send the request from your registered email, name the exact field, and tell us what should be corrected. We will verify the request before we update anything, so the change stays linked to your account.

We keep each record only as long as needed for your account, support handling, security checks, dispute work, and the law that applies where you access us. When the reason ends, we remove or mask it.

Only staff with a role that needs the data for support, security, or payment checks can open it. Access is limited by task, so one team cannot see more than the case requires.

Use WhatsApp, email, or live chat from the contact paths on this page. Send your registered email, username, and the request you want handled, and we will reply in the support window shown here.

Yes. If local law limits a request or requires us to keep a record longer, we follow that rule and explain the reason in our reply. Requests are available only where local law permits.

Privacy Policy for Your Account Data

Where to Reach Our Privacy Team

How We Protect Your Account Data

Data Use

Cookies

Security Checks

Retention

Change Requests

Access Control

Privacy Questions We Answer Often

01 What data do you collect from my account?

02 Do you keep DANA, OVO, GoPay, and QRIS records?

03 Can I ask you to change my personal data?

04 How long do you keep my data?

05 Who can see my private records?

06 How do I contact you about privacy?

07 Does local law affect access or deletion?

Related Pages