Reference

Your privacy rules in plain English

We spell out what we collect, why we use it, and how you can ask for changes before you open an account.

Account dataCookie controlData requestsLocal law
suka288login Your privacy rules in plain English
REQUEST ROUTES

Where to send privacy requests

When you need a correction, a copy of your records, or a question about cookie use, send one message and we start with account verification. Our team handles privacy requests daily from 09:00 to 21:00 WIB through WhatsApp, email, and the signed-in form. If you write from a new phone or browser, we may ask for one matching detail before we change anything, so the record stays tied to you.

Team online

WhatsApp

Use WhatsApp for quick privacy requests. Send your account name, phone number, and the change you want, and we reply during 09:00-21:00 WIB after a short verification step.

Email

Email suits longer requests such as data access, correction, or a copy of stored records. We keep the thread in order so you can track what changed and when.

Signed-in form

Open the signed-in form if you want us to match the request to your current device, login history, and wallet reference before we update the profile.

DATA CARE

How we store and protect data

We keep privacy handling narrow: only the account fields, device markers, and cookie records needed for sign-in, support, and legal duty.

Collected data

We record only what your account needs: name, phone number, device type, login time, and the transaction reference tied to DANA, OVO, GoPay, or QRIS when you use one of those rails.

Cookie use

Cookies remember your session, language choice, and login status, and they help us spot repeated sign-in attempts. You can clear them in your browser, but the page may ask you to log in again.

Account security

If your phone, browser, or SIM changes, we may ask for a fresh sign-in or a code sent to your contact path before we update sensitive details.

Retention

We keep records only as long as we need them for support, dispute handling, security checks, or a legal duty. After that, we remove or mask data that is no longer needed.

Request changes

You can ask us to correct a name, phone number, or linked wallet reference. We compare your request with stored records, make the change where allowed, and confirm by the same channel.

Contact path

Send privacy requests through WhatsApp, email, or the signed-in form. Our team works daily from 09:00 to 21:00 WIB and may ask for one verification step before acting.

Privacy questions people ask most

These answers cover the questions we hear most about privacy: what we keep, why we keep it, how cookies work, and how you can reach us for changes. The same policy applies on mobile and desktop, and access or eligibility depends on local law. If you are already signed in, use the account form; if not, WhatsApp or email both work.

We collect the account name, phone number, login time, device type, and any change you make in the profile. If you use DANA, OVO, GoPay, or QRIS, we also keep the transaction reference needed for support.

Cookies keep your session live, remember language choice, and help us spot repeated sign-in attempts. They also reduce the number of times you need to confirm the same device when you return.

Yes. Send the corrected detail through WhatsApp, email, or the signed-in form, and we compare it with the records we hold before updating anything that law and account checks allow.

We only keep the references needed to match a transaction to your account and support case. We do not keep more payment history than we need for security, dispute handling, or legal duty.

We keep data for the time needed to run the account, answer requests, and meet legal duties. When those reasons end, we remove, mask, or archive records that are no longer needed.

Yes. Ask through the signed-in form or by WhatsApp/email, and we will verify the account first. After that, we send the eligible record set and explain any item we cannot share.

Yes. When access or processing is limited by local law, we follow that rule and make the service available only where local law permits. The same policy still explains how we handle data and requests.