Reference

idebet Privacy Policy for Your Account Data

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

Clear data purposesCookie choicesPayment record controlsAccount access requests
idebet idebet Privacy Policy for Your Account Data
CONTACT PATHS

Get Privacy Help Through Your Account

A clear account route helps you ask about personal data without sending sensitive wallet credentials through an unfamiliar channel. Start from the account help path, describe the privacy request, and include the relevant payment reference when your question concerns DANA, OVO, GoPay or QRIS. We use the account record to locate the right case and may ask for a phone verification step before changing access details.

Team online

Account help

Use the account help path for a copy request, correction request or question about data linked to your login. We may confirm your phone number before discussing account-specific records.

Payment status

For DANA, OVO, GoPay or QRIS records, share the payment reference and status shown in your account. We use that reference to separate your transaction from another account.

Receipt checks

If a receipt appears different from the account record, ask us to check the payment trail through account help. Do not send a wallet PIN, password or full authentication code.

CONTROL DETAILS

Privacy Controls From Login to Retention

Our handling process follows the points where account data is actually created: phone verification, browser login, payment matching and support contact.

Data collection

We collect details you enter for an account, verification records, session activity and payment references. We do not ask for your DANA, OVO or GoPay wallet password to match a transaction.

Cookies

Cookies and similar browser storage help keep your login session, remember security settings and measure technical errors. You can manage browser permissions, though restricting them may interrupt account access.

Account security

Phone verification supports account access and sensitive changes. We check session details and unusual sign-in patterns, then may pause a request until the account holder completes the required verification.

Payment matching

For QRIS, bank transfer and virtual account payments, we use reference data and status results to match the transaction. Wallet credentials remain with the relevant payment service rather than our account record.

Retention checks

We keep account, support and payment records only while they support account operations, dispute handling, security checks or legal duties. When a purpose ends, records are deleted, anonymised or restricted.

Change requests

Ask through account help if your personal data needs correction, access, deletion or clarification. We confirm ownership first and explain any request we cannot complete because a legal duty still applies.

Privacy Policy Questions Indonesian Customers Ask

These Privacy Policy answers cover the practical account, device and payment questions we hear before access is completed. If your case involves a specific record, use account help and include only the reference needed to locate it.

The idebet Privacy Policy covers account details, phone verification, browser cookies, device and session data, payment references, support records, security checks, retention and requests to access or change your data.

We use your phone number to create the account path, complete verification and help protect access after unusual sign-in activity. We may confirm ownership before discussing account data or changing sensitive details.

Yes. The Privacy Policy explains how we use payment references, status results and account matches for DANA, OVO and GoPay. We do not require your wallet password or private wallet authentication code.

Our records may include browser type, device type, session identifiers, cookies and approximate connection details. These support login continuity, technical diagnosis and security checks on mobile and desktop sessions.

Use the account help path and ask for a data access request. We first confirm that you control the account, then locate the relevant records and explain any limits caused by security or legal duties.

You can request correction or removal through account help. We assess the request against active account, payment, dispute and legal needs, then remove, amend or restrict records where the applicable rules allow.

The policy is written for Indonesian account access where local law permits. Eligibility and access depends on local law, so your location and applicable requirements may affect which account steps we can provide.