Reference

cerah88 Legal rules for your account

cerah88 Legal explains how we handle account access, wallet records and requests to change your personal details.

Account verificationWallet record clarityPolicy access
cerah88 cerah88 Legal rules for your account
CONTACT ROUTES

Where Legal questions reach our team

A clear contact path helps when a Legal question concerns your account, payment record or access status.

Account policy request Open the account support path after signing in and include your registered phone details.
Payment record check For DANA, OVO, GoPay or QRIS questions, keep the receipt reference and payment time…
Access eligibility If access is unclear, tell us your location and the account step you reached.
DATA PRACTICE

How Legal handling protects account records

Legal handling is tied to practical account controls rather than broad promises. We limit requests to the details needed for verification, payment matching and policy administration, while your account area remains the…

Data collection

We use phone details and account activity to confirm ownership, connect DANA or QRIS records, and assess a payment status. We do not ask for unrelated details through the policy request path.

Cookie controls

Cookies can help keep your account session and policy pages working across mobile and desktop. Your browser settings can restrict them, although some account functions may then need another check.

Account security

Phone verification comes before account access, and unusual sign-in or wallet activity can require an additional ownership check. Keep your sign-in details private and contact us through the signed-in route.

Record retention

We retain account, payment and policy records for the period needed to operate the account, resolve disputes and meet applicable legal duties. Retention can vary with the record type and local requirements.

Change requests

To request a correction, deletion or update, use the account support path and describe the exact field or record. We may ask for phone verification before changing information linked to ownership.

Policy contact

Questions about Legal wording, data use or account closure should include your account identifier and location. We use those details to send the request to the appropriate policy contact.

Legal answers for Indonesian account holders

These Legal questions cover the points you may check before opening an account or asking us to change account data. We address access, payment records, cookies, retention and contact steps directly, with eligibility always handled where local law permits.

cerah88 Legal covers account opening conditions, phone verification, payment records, data use, cookies, account security, retention, correction requests and closure. Access depends on local law and the location connected with your account.

Yes. Our Legal process requires clear phone verification before account access. This helps connect you with the correct account record and supports checks involving DANA, OVO, GoPay, QRIS or bank transfer activity.

We use DANA and QRIS receipt details to match payment status with the correct account. If a record needs checking, keep the reference and payment time available through the account support path.

Yes. Send a Legal data-change request through the signed-in account support path and identify the exact field. We may request phone verification before correcting information linked to account ownership.

We keep account, payment and policy records only for the period needed for account operation, dispute handling and applicable legal duties. The period can differ according to the record and local requirements.

Yes. Our Legal policy explains that cookies can maintain sessions and display account pages across devices. You can restrict cookies in your browser, but some access steps may require another verification check.

Eligibility depends on local law. Tell us your location through the account support route, and we will explain the applicable Legal position where local law permits, without bypassing a stated access requirement.