Reference

cerutu555 Privacy Policy for Your Account

cerutu555 Privacy Policy explains how we handle your account details, phone verification, wallet references and device activity when you use our site.

Phone verificationWallet referencesMobile privacy accessIndonesia data context
cerutu555 cerutu555 Privacy Policy for Your Account
REQUEST ROUTES

Reach Support About Privacy Requests

A clear support path helps you ask what we hold, why we use it or how to correct an account detail.

Account privacy request Use the support route beside your account area when you want a copy of the personal data connected with your cerutu555 profile. Include your registered phone detail so we can locate the correct record before replying.
Wallet record question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the payment date, reference and account identifier through support. We use those details to check our records without asking for your wallet PIN or password.
Correction request Tell us which account detail needs changing and why it is inaccurate. We may confirm your phone verification first, then update the relevant record or explain why a legal retention duty means it must remain stored.
HANDLING DETAILS

Secure Your Account Data on Mobile

Privacy depends on practical account habits as well as written rules. We separate account access details from wallet credentials, use session controls in the browser and check identity signals when a request…

Account details

We use the phone number and account details you provide to create access, complete phone verification and connect support requests to your profile. We do not need your DANA, OVO, GoPay or QRIS wallet password to check a payment reference.

Browser cookies

Session cookies help keep your signed-in path working between the account page, privacy page and lobby on your browser. You can manage browser cookie controls on your device, although blocking necessary cookies may interrupt account access or sign-in continuity.

Security checks

We may compare phone verification, sign-in records, device signals and payment references when protecting an account. These checks help us respond to unusual access or a wallet-status question without treating a new device as automatic proof of account ownership.

Retention periods

We keep account, support and transaction records only for the operational or legal period that applies to them. A request to remove data may not erase records needed for fraud checks, dispute handling, account security or a legal duty.

Requesting changes

Where local law permits, you can ask us to correct, access or clarify personal data through support. Give the account identifier, the requested action and a safe contact route; we may verify ownership before sharing or changing anything.

Policy access

Open the Privacy Policy from the site footer or account area on a phone, tablet or desktop browser. If you use an Indonesian connection and access is discussed, availability depends on local law and the rules that apply to your location.

Browse Answers About Privacy Policy

These questions cover the points you are most likely to check before opening an account: what we collect, how payment references are used, how browser access works and where to send a request. Our Privacy Policy remains the controlling page, while support can help connect your question with the correct account record.

The cerutu555 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It also explains why we use those records, how long we retain them and how you can request access or correction where local law permits.

No. We use transaction references and status details for DANA, OVO, GoPay, QRIS, bank transfer or virtual account checks. Your external wallet password and PIN should not be sent to support, and our Privacy Policy does not treat a reference as permission to access your wallet.

We receive the phone detail and account fields you submit, along with records showing that verification was completed. Device and browser signals may also be recorded for account security. We use these details to provide access, investigate unusual sign-ins and connect a privacy request to you.

Use the support route connected to your account and ask for a personal data access request. Include your registered phone detail or account identifier, describe the records you want, and complete any ownership check we request before private account data is shared.

Yes, you can send a correction request through support and explain which detail is inaccurate. We may confirm your phone verification before changing it. If a record must remain for security, dispute handling or legal reasons, we will explain that restriction.

Our Privacy Policy explains that session cookies help maintain your signed-in path between account pages and the lobby. You can adjust cookie settings in your mobile browser, but blocking necessary cookies may interrupt sign-in, policy access or movement through the account area.

Retention depends on the record and the operational or legal reason for keeping it. Account, support and payment references may remain available for security, dispute checks or legal duties. You can ask support which retention rule applies to a specific record.