Reference

seru88 Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open a seru88 account, sign in from a phone or desktop, and use wallet options such as DANA, OVO…

Account detailsWallet recordsDevice sessionsCookie choices
seru88 seru88 Privacy Policy for Your Account
CONTACT DATA HELP

Reach Us About Your Privacy Policy

A clear contact path matters when a name, phone number or wallet reference needs attention.

Account help route From your signed-in account, open the help path and describe the Privacy Policy request. Include the affected field, such as phone verification or a DANA receipt, so we can locate the correct record.
Cashier status query For a wallet record connected to OVO, GoPay or QRIS, share the transaction reference and approximate date. We can compare the cashier status without asking you to disclose a wallet password.
Login access request If you cannot sign in, tell us the account phone number, device type and last successful access. Never send a one-time code; we use safer account checks before discussing personal data.
DATA HANDLING PRACTICE

Browse How seru88 Handles Your Data

We keep this Privacy Policy practical: the account step, device session and wallet reference each have a defined reason for being recorded.

Account data

We use your chosen account details and verified phone number to create a sign-in record, confirm that a request comes from you and connect account changes to the correct profile.

Device sessions

A browser or mobile session may generate device, browser and sign-in time records. These help us spot an unusual login and investigate why your account path stopped before the lobby.

Cookies

Cookies can remember a session choice, language setting or consent preference. You can manage cookies through your browser controls, although clearing them may require phone verification again.

Wallet records

For DANA, QRIS, bank transfer or virtual account activity, we retain the reference and status needed to reconcile your account. We do not ask for wallet passwords or one-time codes.

Retention periods

We keep each data category for the period needed for account security, payment reconciliation or a legal duty. When that purpose ends, the record is removed or separated from active account use.

Change requests

To request correction, access or deletion, contact us through the account help route with your verified phone number and the specific field. We may ask an account check before changing personal data.

Explore Common Privacy Policy Questions

These Privacy Policy answers address the account and wallet questions you may have before opening an account or returning from a mobile device. We keep the request path tied to your verified account, and access depends on local law.

It covers account creation, phone verification, sign-in sessions, cookies, device records, support messages and payment references connected with DANA, OVO, GoPay, QRIS or bank transfer.

We use your phone number for account identification and verification before account access. It also helps us match a privacy request to the right profile when you ask for a correction.

No. Our payment record uses a transaction reference and status for reconciliation. You should not send a DANA, OVO, GoPay or QRIS password, PIN or one-time code to us.

Use the signed-in account help route and state that you want an access request under the Privacy Policy. Add your verified phone number and the data category you want us to locate.

Yes, where local law permits. Contact us with the incorrect field, such as a phone detail or account name. We may complete an account check before applying the requested correction.

We retain payment references and status for the period needed to reconcile the account, protect access and meet applicable legal duties. The exact period can differ by record type and purpose.

Yes. It applies to both device paths, including browser cookies, sign-in times and session details. Clearing mobile cookies can remove saved preferences and may trigger phone verification on the next visit.