Reference

tole jitu Privacy Policy Explained Clearly

The tole jitu Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesAccess requests
tole jitu tole jitu Privacy Policy Explained Clearly
HELP WITH RECORDS

Get Privacy Help Without Guesswork

A clear contact route helps you resolve a data question before it affects account access.

Account contact Open the support path beside your account details and state the Privacy Policy request in plain English. Include the phone number tied to your account so we can identify the correct record without asking you to send a password or wallet PIN.
Wallet receipt check If your request concerns DANA, OVO, GoPay, QRIS or a bank transfer receipt, add the transaction reference and date. We use that context to separate a payment record from unrelated account activity before replying through the available contact route.
Access question For a question about regional availability or account eligibility, tell us your location and the screen message you received. We will explain the applicable route where local law permits, without asking you to bypass a location or account control.
DATA HANDLING DETAILS

How We Handle Your Privacy Choices

Privacy controls work best when each part of the account journey has a clear purpose. We separate sign-in checks from wallet reconciliation, record cookie choices on the device where they are made…

Account collection

We collect the details needed to create and maintain your account, including contact data and phone verification status. If you browse the lobby before signing in, we may still receive basic device and browser signals needed to deliver the page and protect the session.

Device signals

A phone, tablet or desktop can provide browser type, operating details, session time and security signals. These records help us spot an unusual login and keep the account path consistent when you move from sign-in to a lobby page.

Cookies

Cookies and similar storage can remember a session, preserve a selected setting and help us understand whether a page loaded correctly. You can manage browser permissions on your device, although blocking necessary storage may interrupt sign-in or account navigation.

Account security

We use phone verification, sign-in records and session checks to help protect your account. Never share a password, one-time code or wallet PIN in a support message. If a login looks unfamiliar, contact us with the time and device used.

Retention approach

We retain account, support and wallet-related records for as long as needed for the stated service, security checks, dispute handling or legal duties. A deletion request may have limits where a record must remain for a defined legal or account matter.

Changing your data

Ask us to correct an inaccurate phone number, contact detail or account record through the support route. We may request enough account context to verify ownership, then explain which fields can be changed and when the updated record should appear.

Privacy Policy Answers For Your Account

These answers address the Privacy Policy searches we hear most often from Indonesian account holders. If your situation involves a wallet receipt, a device change or a regional access question, include those details when you contact us so we can point you to the relevant record and request path.

The tole jitu Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages and wallet references. It explains why we use those records, how retention works and how you can request access or correction through the account support route.

We use your phone number to create and identify the account and to complete the phone verification step before account access. It also helps us locate the correct record when you ask about a DANA, OVO, GoPay or QRIS receipt.

Yes. The Privacy Policy includes payment references and confirmation details connected with DANA, QRIS, OVO, GoPay, bank transfer or a virtual account. We use those details to match an account request or receipt, not to collect your wallet PIN.

Use the support path connected to your account and ask for a copy of the personal data we hold. Include your account phone number and request subject, but do not send a password, one-time code or wallet PIN. We may verify ownership before responding.

You can ask us to correct an inaccurate contact detail, phone number or account record through the support route. Tell us what is wrong and what should replace it. We may request account context before making the change, and some records may need to remain for legal duties.

Cookies may keep your session active, remember a setting or help us identify a page-loading problem. They can be managed through your browser or device settings. Blocking necessary cookies may stop sign-in, phone verification or account navigation from working correctly.

The policy applies to the account and records we handle, but account eligibility and regional access depends on local law. If a location message appears, contact us with that message rather than trying to bypass it; we will explain the available route where local law permits.