Reference

Open cerutu4d Privacy Policy Before Access

Our cerutu4d Privacy Policy shows how we handle account details, phone verification, wallet records and device access before you enter the lobby.

Account dataWallet recordsCookie choicesRequest path
cerutu4d Open cerutu4d Privacy Policy Before Access
CONTACT ROUTE

Check Privacy Questions Through Account Help

A clear contact path helps when your account record or wallet status needs attention. Start from account help and include the phone number linked to your profile, the relevant date, and the payment reference if your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use those details to locate the right record without asking you to send a password.

Team online

Account access

Use the account help path when phone verification, a device change or a sign-in record looks unfamiliar. We may ask for identity details already linked to your account before discussing personal data.

Wallet records

For a DANA, OVO, GoPay or QRIS question, attach the payment reference and time shown in your receipt. We check the matching account record and avoid requesting your wallet password.

Policy requests

Ask us to access, correct or remove eligible personal data through account help. We confirm the request belongs to you, explain any retention requirement, and respond through the contact route on your profile.

DATA PRACTICE

Browse Device And Cookie Controls

Privacy choices work best when you know which account step creates each record. We separate sign-in checks, payment references, support messages and browsing signals so a request can be handled against the…

Account details

We collect details you provide when opening an account, including contact information needed for phone verification. We use them to maintain access, answer a data request and connect you with the correct profile.

Payment references

A DANA, OVO, GoPay or QRIS receipt can include a reference, amount and time. We use that record to match wallet status and resolve account questions, not to request your private wallet password.

Device signals

Browser type, device details and connection signals can help us identify an unusual sign-in. If you switch from mobile to desktop, another phone verification step may appear before account access.

Cookie settings

Cookies can keep your account path, security checks and selected page available during a session. You can clear or restrict them in your browser, although some account functions may then require another sign-in.

Record retention

We keep account, payment and support records only for the operational, security or legal period that applies. When a record is no longer needed, we remove it or separate it from direct account identifiers.

Policy changes

If this Privacy Policy changes, we place the updated version on the policy page and show the revised date. Your continued account access may require acknowledgement when the change affects your available choices.

Browse Answers About Your Privacy

These Privacy Policy answers focus on the account steps you are most likely to check before opening access. We keep the wording practical, from phone verification and mobile cookies to payment references and requests made through account help.

It covers account details, phone verification, device and browser signals, cookies, support messages, payment references and records linked to account activity. It applies to our website and account paths where local law permits.

Phone verification helps us connect an account request to the right person and reduce unusual access. It may be requested again after clearing browser data, changing devices or asking for personal-data changes.

Yes. We may store the payment reference, time and account match for DANA, QRIS, OVO, GoPay, bank transfer or virtual account activity so support can check a wallet status.

You can send an access request through account help. We verify your identity first, then provide eligible account data or explain why a specific record must remain under an applicable retention rule.

Contact us through the account help path with the field you believe is incorrect and the reason for the change. We may request phone verification before updating the profile or payment record.

Cookies can retain a session and security state in your mobile browser. Restricting or clearing them may sign you out, remove saved page settings and trigger phone verification when you return.

Use account help and identify your request as a Privacy Policy question. Include the account contact detail and relevant payment reference when applicable, but never send a password or wallet security code.