Reference

Legal terms for your account

We set out the legal rules for account access, data use, and request handling before you move further.

Indonesia lawData useAccount accessRequest changes

Browse Lobby Read FAQ

Where local law sets the rules

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

We collect only the details needed to verify your account, handle access requests, and reconcile records tied to DANA, OVO, GoPay, or QRIS. Access to our services depends on local law and is available only where local law permits, so we may block or pause a

1
request if the region does not allow it. When you ask for a correction, export, or closure, we may ask for your registered email, a recent sign-in device, or a payment reference so we can protect the account from misuse. We keep request logs for a
2
limited period to resolve disputes, audit changes, and prevent duplicate submissions, then we remove or archive them according to the rule that applies to your case. If your local law gives you extra rights, send the request through the same channel and we will tell you
3
what we can do next.

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

CONTACT PATHS

Where to send requests

If you need a correction, access check, or account-data request, use the same contact thread from start to finish.

Live chat Send the registered email, your request type, and the last payment rail you used. We answer from one case thread every day 09:00-21:00 WIB, which helps us match the record and explain the next step without asking you to start again.

Email Use email when you need attachments, screenshots, or a written trail for a correction. We reply with a case reference and tell you whether we need a device match, payment trace, or another confirmation.

WhatsApp If mobile is easier, message us from your registered number and keep the request short. We use WhatsApp for status checks, identity confirmation, and final changes that need a quick back-and-forth.

DATA HANDLING

How we keep records safe

We handle this area with a narrow data set, one request trail, and account checks before any change is approved.

Data use

We only keep the details needed to verify your account, handle access requests, and reconcile records tied to DANA, OVO, GoPay, or QRIS when you contact us from the same account.

Cookies

Our cookies remember sign-in state, language choice, and the form you last opened. You can clear them in your browser, but you may need to sign in again and resend the request from the account page.

Account security

We ask for a matching email, a recent sign-in device, or a payment trace before we change account data. That extra check keeps someone else from editing your details without permission.

Retention

We keep support logs only as long as we need them for audit, dispute handling, and fraud checks. After that, we archive or remove the record according to the rule that applies to your case.

Change requests

If you want to correct, export, or close account data, send the request from your registered contact channel. We will tell you what we can process, what we must keep, and what proof we need.

Contact path

For privacy or access questions, use the same support thread until the case closes. That gives you one case reference, one reply trail, and a clear history of every change we made.

Common questions about legal access

These questions cover access, corrections, retention, cookies, and who can request changes. We keep the answers practical: use your registered email, include a device or payment trace when needed, and send the request through the contact path that matches your account. If local law gives you a specific right, we will tell you whether we can act on it and what happens after we verify the request.

Send the request from your registered email or WhatsApp number, and include the account name you use with us. We will confirm the record, tell you which parts we can share, and explain any legal hold.

Yes, if the change matches your account record and we can verify you own it. We may ask for a recent sign-in device, a payment trace, or another confirmation before we update the file.

Usually we ask for the registered email, a recent login device, or the reference tied to DANA, OVO, GoPay, or QRIS. That check helps us stop someone else from changing your data.

We keep support logs for a limited time so we can audit changes, answer disputes, and block duplicate requests. After that, we archive or remove them under the rule that applies to your case.

Cookies help remember your session and the form you last opened. They do not change your rights, but clearing them may sign you out and make you confirm the request again on the next visit.

Access depends on local law and is available only where local law permits. If your region does not allow it, we will say so plainly and stop the process before any account action is taken.

Use the same contact thread that matches your registered account, then keep the case reference in every reply. That makes it easier for us to trace the request and keep the history in one place.

Legal terms for your account

Where to send requests

How we keep records safe

Data use

Cookies

Account security

Retention

Change requests

Contact path

Common questions about legal access

01 How do I request my account data?

02 Can I correct my account details?

03 What proof do you ask for?

04 How long do you keep support records?

05 Do cookies affect access to my account?

06 Who can use the service where I live?

07 Which channel should I use for privacy requests?

Related Pages