Reference

timsestoto Privacy Policy for Indonesian Account Data

Your account details, wallet records and device choices are covered in the timsestoto Privacy Policy, so you can understand what we collect before opening an account.

Account dataWallet recordsDevice choicesPrivacy requests
timsestoto timsestoto Privacy Policy for Indonesian Account Data
REQUEST HELP DIRECTLY

Privacy Support Beside Your Account Path

A clear support path matters when a Privacy Policy question concerns login, a wallet status or a receipt.

Policy questions Ask which account data we hold, why a field is needed, or how the…
Account access If phone verification or login blocks your request, use the account help path and…
Wallet status For a DANA, OVO, GoPay or QRIS record, provide the visible reference and status…
ACCOUNT DATA PRACTICE

Account Security Across Mobile and Desktop

We apply the Privacy Policy to the practical moments around your account: phone verification, device access, wallet matching and requests to change stored data.

Data collected

We may handle account identifiers, phone verification results, device signals, selected game activity and payment references. These records help connect your account step with the request you send.

Cookie choices

Cookies and similar device storage can remember session state and support page preferences. You can manage browser controls, although changing them may require another login or affect page continuity.

Account security

Phone verification helps us connect account access with the person completing the step. Never send your password, wallet PIN or full payment credentials through a support request.

Retention period

We keep records only as long as needed for the stated account, payment matching, security or legal purpose. Some transaction records may remain after a request is closed.

Correction request

If your account data is inaccurate, contact us through account help and identify the field to change. We may ask for a verification step before editing information tied to access.

Access request

You can ask what personal data is connected to your account and request an explanation of its use. Include the account path involved, such as mobile login or QRIS status.

Privacy Policy Answers for Your Account

These Privacy Policy answers focus on the questions you may have before creating an account or sending a data request. We keep the route practical: identify the account step, name the wallet or device involved, and contact support through the available account help area. If a question concerns access, the outcome depends on local law.

It covers account identifiers, phone verification, device signals, cookie use, selected activity, payment references and support requests. It also explains purposes, retention, security steps and how you can request access or correction.

We record the payment reference and status needed to match a DANA or QRIS event with your account. This helps us check a receipt or stalled wallet status without requesting your private wallet credentials.

Yes. Send an access request through account help, identify the relevant account path and complete any verification we require. We will handle the request according to the Privacy Policy and local law.

Contact support through the account help path and name the inaccurate field, such as a phone detail or account identifier. We may verify your identity before changing data connected to account access.

Yes. It explains how session records, device signals and cookies may support mobile login and continuity. The policy also applies when you move from a phone to desktop during an account request.

We retain payment references for the period needed to match transactions, handle account security, meet stated legal duties or resolve a request. A closed support case does not always remove its related record.

Use the support route in your account help area and describe whether the request concerns access, correction, deletion or a DANA, OVO, GoPay or QRIS reference. Do not include passwords or wallet PINs.