Reference

Privacy Policy for Your Account

coblos 77 slot Privacy Policy explains how we collect, use and protect details connected with your account, including phone verification and wallet status for DANA, OVO, GoPay and…

Clear data purposesWallet detail controlsAccount access rightsCookie choices
coblos 77 slot Privacy Policy for Your Account
CONTACT ROUTES

Privacy Help Beside Account Support

A privacy question should not require a long search, so we keep a clear contact route beside account support.

Account message Use the signed-in account support path for a Privacy Policy request. Tell us whether you want access, correction, deletion or an explanation of a data use. We may ask for a phone verification step before revealing account-linked details.
Wallet status query If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the transaction reference through account support. We use that reference to locate the relevant record without asking for your wallet password or complete payment credential.
Login assistance When you cannot reach the account help path, tell us the device type and the last successful sign-in. We use those details to route the request, then confirm identity through the registered phone before discussing personal data.
DATA PRACTICES

What We Keep And Why

Our privacy work follows the real steps you take: opening an account, confirming a phone, signing in from a device and checking a wallet status.

Account creation

When you open an account, we record the details needed to create your profile and send access messages. Phone verification confirms control of the registered number before account details are shown, helping us distinguish your request from an unauthorised attempt.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may produce a reference, amount and status record. We use those fields to reconcile an account action; we do not ask for a wallet password through our support route.

Device signals

We may record browser, operating system, session time and basic device signals when you sign in. On a mobile browser, these signals help identify an unusual session; they are reviewed with account details rather than treated as a complete identity by themselves.

Cookies

Session cookies keep your signed-in path available while you move between account pages and the lobby. Preference or measurement cookies may have separate settings where available. Clearing browser data can sign you out and may remove choices saved on that device.

Account security

We use phone verification, sign-in records and access controls to reduce unauthorised viewing of your account data. If a sign-in looks unusual, we may pause a data request until you confirm the registered phone or provide the requested account details.

Retention requests

We retain records only for operational, dispute, security or legal needs that apply to the account. You can ask which records remain, request a correction or ask about deletion through account support; some records may stay when a valid obligation applies.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the questions we expect before you open an account or connect a local wallet. We explain the account step, payment references, cookies, device signals and contact process in plain English for Indonesia. If your situation is not covered, send the question through the signed-in support path and we will identify the relevant record before responding.

It covers account details, phone verification, sign-in records, device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains purposes, retention, security controls and ways to request access or correction.

We use your phone number to create the account path, send verification and confirm that a privacy request comes from the account holder. We do not treat phone verification as permission to collect unrelated contacts, messages or information from your device.

Yes. We may receive a transaction reference, status and related account record when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use those details to match an account action and do not request your wallet password.

Send an access request through the signed-in account support path and identify the phone number linked to your profile. We may complete a phone verification step before sharing account-linked details. Where local law permits, we will explain the records covered by your request.

Yes. Tell us which detail is incorrect and provide the corrected version through account support. For a phone number, identity or payment reference, we may ask for an additional verification step. We record the request and explain any reason a change cannot be made.

Session cookies help keep your mobile browser connected while you move between account pages. Clearing them can sign you out and remove saved preferences. Cookie settings may be available in the browser or on the relevant page, depending on your device.

Yes. Account availability and any related data handling depend on local law. We apply the Privacy Policy to information collected through the account path, but a request, retention period or access decision may differ where local law permits a different treatment.