Reference

Open ceri188 Privacy Policy with clarity

Our ceri188 Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesSecurity steps
ceri188 Open ceri188 Privacy Policy with clarity
CONTACT ROUTES

Check the support path for privacy questions

A clear contact route matters when you want to ask what a record means or request a change. Use the support link connected to your ceri188 account and include the phone number or account reference that can help us locate the correct record. For a wallet question, mention DANA, OVO, GoPay, QRIS, bank transfer or virtual account status without sending a password. We may ask for account verification before discussing personal data, and access remains where local law permits.

Team online

Account privacy request

Use the account support link to ask for a copy, correction or explanation of personal data. Include your account reference, but never place your password or one-time verification code in the message.

Wallet record question

When a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the date, rail name and visible status through support. We can check the matching account record after confirming that you control the account.

Security concern

If your phone, login or account details may have been exposed, contact us through the account support route before sharing further data. We use verification steps to separate a genuine request from an unauthorised one.

CONTROL DETAILS

Explore the controls behind your privacy

Privacy is handled through practical account controls rather than vague promises. We separate login verification from wallet references, use device and session signals to help identify unusual access…

Data we collect

We may handle account registration details, phone verification results, login events, device signals and payment references.

Cookie settings

Cookies can help keep a session connected and remember practical page choices.

Account security

Before we discuss private account records, we may check your phone verification or another account detail.

Retention timing

We retain records only for the period needed for the purpose described in the Privacy Policy, account administration, dispute handling…

Who receives data

Access is limited to parties involved in the stated account, payment, security or legal task.

Requesting changes

You can ask us to access, correct or delete eligible personal data through the support route linked to your account.

Browse Privacy Policy answers before opening

These questions focus on the parts of our Privacy Policy that matter before you create or use an account. We address wallet records, mobile access, cookies, account requests and the checks needed to protect your data. If your question is not listed, use the ceri188 support route and describe the record or account step involved.

It covers account registration, phone verification, login and device signals, cookies, payment references and requests connected with account activity. It also explains retention, lawful disclosures and your routes to ask for access, correction or deletion where local law permits.

We may store a transaction reference, status, amount and account match for a DANA or QRIS action. The reference helps us answer a payment-status question, but you should not send wallet passwords, personal access codes or one-time codes through support.

Phone verification helps connect an account request to the person who controls the account. It can also help us avoid disclosing private records to someone else. We may ask for a matching account detail before handling a data request.

Use the support link associated with your account and ask for an access request. Add your account reference and describe the data range you need. We verify ownership first, then respond according to the Privacy Policy and applicable local law.

Yes, you can submit a correction or deletion request through the account support route. Some records may need to remain for account administration, dispute handling or a lawful requirement. We explain the result after verifying your request where local law permits.

Mobile access may create login, session and device signals that help keep the account connected and identify unusual activity. The same Privacy Policy applies when you move from phone login to a lobby title such as Aviator Mobile Play.

Contact us through the support link in your account and name the rail, date and visible status. Mention whether it concerns OVO, GoPay, DANA, QRIS, bank transfer or virtual account activity, but leave out passwords and verification codes.