Reference

Privacy Policy For Your tarbol Account

Our Privacy Policy explains what we collect when you open a tarbol account, use the mobile lobby, or check a DANA, OVO, GoPay or QRIS transaction.

Clear data categoriesWallet record contextDirect request pathDevice session controls
tarbol Privacy Policy For Your tarbol Account
CONTACT ROUTES

Get Privacy Policy Help Near Wallet Support

A clear contact route matters when a Privacy Policy question is connected to a wallet record or account login.

Account access When phone verification blocks your account, contact support from the account path and state that your request concerns the Privacy Policy. We can explain which identity detail is needed for access handling and help separate a device-session issue from a request to inspect stored account data.
Wallet records For DANA, OVO, GoPay or QRIS records, include the relevant reference and approximate date rather than sending a full wallet screenshot. This lets us locate the account-linked payment context while limiting extra personal data in your message and keeping the Privacy Policy request focused.
Policy requests Ask directly for access, correction, retention details or cookie handling through the support contact path. Tell us which account detail you mean and how we should reply. Where local law permits, we will explain the available action, any identity check and the next step.
DATA PRACTICE

How We Apply This Privacy Policy

The policy is applied through ordinary account controls you can recognise: phone verification before access, session checks on a changed device and records tied to the payment reference you submit.

Account data

We may handle the details you provide to open and maintain an account, including contact information and phone verification data. The Privacy Policy connects each category to an operational purpose, such as confirming access or responding to a request, instead of treating every detail as open-ended platform data.

Device sessions

A mobile browser session can create device and security signals that help identify unusual account access. When you move from a phone to desktop, a verification prompt may appear. These signals support account protection and are handled under the retention and access rules described in the Privacy Policy.

Cookies

Cookies can remember a session choice and support the page functions you request. Our Privacy Policy explains the purpose of these files and how your browser settings affect them. Clearing cookies may sign you out or remove a saved preference, but it does not erase account records by itself.

Payment matching

When you submit a DANA, GoPay or bank transfer reference, we use the payment context needed to match status with your account. QRIS and virtual account records follow the same purpose-based approach. We do not need unrelated wallet content to answer a Privacy Policy request.

Retention period

We keep account, security and transaction-linked records for the period stated by the applicable purpose or required rule. A request to remove data may have limits where a record must remain available. We will explain the relevant retention reason rather than treating deletion as automatic.

Changes and contact

If your name, phone detail or contact route needs correction, use the support path and identify the affected account field. We may ask for a reasonable identity check before changing it. The Privacy Policy also explains how to ask about a policy change or a data-handling decision.

Privacy Policy Questions Before Account Access

These Privacy Policy answers address the searches we hear before an Indonesian account is opened or checked on a new device. They explain the practical difference between account data, payment references, cookies and a formal access request. When a question depends on eligibility or a local restriction, the answer uses the applicable wording: access depends on local law or is available where local law permits. You can use the support route for a specific account request without sending your password or unnecessary wallet details.

The tarbol Privacy Policy covers account details, phone verification, device-session signals, cookies, payment references and support messages created through your account. It explains why each category is used, how retention works and how to ask for access or correction where local law permits.

Yes. The Privacy Policy covers the payment context needed to match DANA, OVO, GoPay, QRIS, bank transfer and virtual account status with your account. It does not require unrelated wallet content. Send only the reference needed for a support request and remove extra personal details.

Use the account support path and ask for a Privacy Policy data-access request. State the account email or phone detail and the categories you want, such as phone verification or payment references. We may confirm your identity before releasing data, where local law permits.

You can contact us through the policy support route to request a correction. Name the exact field, such as a phone number or contact detail, and explain the change. We may ask for an identity check, then explain the action available under the Privacy Policy.

On a mobile browser, cookies can retain a session choice and support requested page functions. Clearing them may sign you out or remove a preference. The Privacy Policy explains their purposes; your browser controls can restrict cookies, but that does not remove account records.

Phone verification may appear when a new device or session does not match earlier account security signals. It helps us confirm that the person requesting access controls the account contact detail. The Privacy Policy explains how this security data is used and retained.

You may ask through support whether deletion is available for a particular category. The result depends on local law and whether a record must remain for a stated security, payment or legal purpose. We will identify the relevant category, retention reason and available next step.