Reference

Legal access for your account

This page explains how we handle access, data use, cookies, and account changes in the play88 notice before you move deeper into the account area.

Where local law permitsDANA, OVO, GoPay, QRISAndroid Chrome / iPhone SafariAccount email checks

Explore Lobby Read FAQ

What our legal notice covers

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

Our legal notice explains what we collect, why we keep it, and when access is limited by jurisdiction. If local law changes, we update the notice in plain English and keep the account steps readable so you can check them before you continue. We also show

1
the local rails we recognise - DANA, OVO, GoPay, and QRIS - because payment records can be part of an account check or a correction request. When you contact us, we verify the account email, the last payment reference, and the request itself before any change
2
is made. If access to a page or function depends on local law, we state that directly instead of hiding it in fine print.

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

CONTACT ROUTES

Where to reach us about records

Our chat desk is open every day from 09:00-23:00 WIB, and email stays available when you need a written trail.

Live chat Open chat from the help tab and send the account email plus the request type. We use it for access checks, stored-data copies, and correction requests when you need a fast answer.

Email trail Email gives you a written record for legal questions. Send the account email, the page or record you want changed, and the last payment rail used so we can verify the file first.

In-account form Use the form inside your account when you want the request tied to the same login. It helps us match the notice you saw on mobile, desktop, or both.

DATA HANDLING

How we handle your data

We treat this page as a live record, not a static footer. Cookies remember your session and the notice you last saw, while account security checks protect changes to your email, password…

Data handling

We store the account email, login timestamps, device type, and payment reference needed to answer legal requests. That lets us confirm who is asking before we change a record or share a copy.

Cookies

Cookies remember the legal notice you last accepted, the session on Android or iPhone, and your language setting. They also reduce repeat prompts when you return from the same browser.

Account security

We ask for the account email, a matching code if needed, and the last known payment rail before we change sensitive settings. That helps us block unauthorised edits to your file.

Retention

We keep request logs only for the period needed to handle support, resolve disputes, and meet legal duties. After that, records are trimmed or removed according to the rule that applies.

Change requests

Send changes through chat or email with the account email, the exact request, and any matching payment reference. We confirm the details first, then update the record and send a reply.

Local law access

If a page, function, or account step is restricted, access depends on local law. Where local law permits, we show the current notice and let you continue after the check.

Questions about access and records

These answers cover the legal questions that matter before you move ahead. We keep them short on purpose: what we collect, how long we keep it, where local law changes access, and which contact path fits a correction request. If you are checking from Android Chrome, iPhone Safari, or a desktop browser, the same wording applies so you do not have to guess which version to trust.

Yes. Access depends on local law, and where local law permits we show the account area and the current notice. If a region is restricted, we state it plainly before you continue.

We keep the account email, login logs, device type, and the payment reference tied to a request. That record helps us confirm identity before we change data or share a copy.

Send the request by chat or email with the account email, the exact change you want, and the last payment rail used. We verify the file first, then update it.

Cookies remember your session, the notice you last saw, and the browser you used. They also cut repeat prompts when you return from the same Android or iPhone device.

Yes. Ask through chat or email, and we will check the account details before sending any copy. If a record must stay for legal reasons, we explain the limit.

Live chat is the fastest path for simple checks, while email is better when you want a written trail. Both routes work for access, corrections, and record requests.

Legal access for your account

Where to reach us about records

How we handle your data

Data handling

Cookies

Account security

Retention

Change requests

Local law access

Questions about access and records

01 Does access depend on local law?

02 What account data do you keep?

03 How do I request a correction?

04 Why do you use cookies here?

05 Can I ask for a copy of my data?

06 Which contact path is fastest for legal questions?

Related Pages