Reference

tasiktoto Privacy Policy For Your Account

Our Privacy Policy explains how tasiktoto handles the details you provide when opening an account, signing in, checking wallet status or entering the lobby from Indonesia.

Account clarityWallet referencesCookie choicesContact steps
tasiktoto tasiktoto Privacy Policy For Your Account
CONTACT DATA HELP

Get Privacy Help Beside Account Support

A clear contact path helps when you want to ask what we hold, correct an account detail or question a wallet record. Start from the support route shown after login and include your registered contact detail, device path and any DANA, OVO, GoPay or QRIS reference involved. We use those points to locate the right record without asking you to send a password or wallet PIN.

Team online

Account support route

Use the signed-in support path for a Privacy Policy question, especially when your request concerns login records, phone verification or a device that no longer belongs to you.

Wallet status check

Send the payment reference shown for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity so we can separate a status question from unrelated account data.

Correction request

Tell us which account detail needs changing and why. We may ask for an account step that confirms you control the profile before making a record correction.

DATA HANDLING DETAILS

What We Keep And How You Ask Changes

We keep this Privacy Policy connected to the account path so you can read it before using the lobby, including from a mobile browser in Yogyakarta or elsewhere in Indonesia.

Account security

Phone verification is part of account access. We use sign-in and verification signals to identify unusual sessions, while your password and wallet PIN should remain private and must not be sent to support.

Cookie controls

Cookies and similar device signals can remember session choices and help us identify repeated access. Your browser settings provide a way to clear or restrict them, though some account steps may then need repeating.

Wallet records

DANA, OVO, GoPay and QRIS activity can create a payment reference or status entry. We use that record to reconcile your account path, not to collect your wallet password or banking PIN.

Retention approach

We keep account, support and transaction references for the period needed to provide the requested service, resolve a dispute, protect access or meet a legal duty where local law permits.

Requesting access

Ask what personal details are linked to your account through the support route. Include your registered contact detail so we can confirm the correct profile before sharing account-specific records.

Requesting changes

For a correction or deletion request, identify the exact record and explain the requested action. We may retain limited entries when needed for account protection, dispute handling or legal duties.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the account steps you are most likely to search before opening access from Indonesia. We cover payment references, cookies, phone verification, data requests and the local-law wording that applies to account eligibility. If your question concerns a specific record, use the support path with your registered contact detail rather than sending sensitive credentials in a message.

It covers account details, phone verification, device and cookie signals, payment references, support records, retention and requests to access or correct data. Access depends on local law.

No. We may receive a DANA or QRIS payment reference and status needed for account reconciliation, but you should never send a wallet PIN, banking PIN or password to us.

Phone verification helps connect the correct person with an account and can flag unusual sign-in activity. It also supports account recovery and privacy requests involving profile-specific records.

Use the signed-in support route and provide your registered contact detail. We may confirm account control before discussing profile records, device signals or payment references linked to you.

Yes, you can identify an incorrect account or support record and explain the correction needed. We may keep a limited audit entry when protection, dispute handling or legal duties require it.

Cookies can retain session choices and help connect your mobile browser with an active login. Clearing them may sign you out or require phone verification again during the next account step.

You can send a deletion request through the account support route. We assess the request against account protection, unresolved disputes, transaction records and legal retention duties before responding.