Reference

98toto Privacy Policy for DANA Accounts

Our Privacy Policy explains how we use the details connected with your 98toto account, including phone verification and DANA, OVO, GoPay or QRIS payment records.

Clear data purposesWallet record controlsAccount access rightsCookie choices
98toto 98toto Privacy Policy for DANA Accounts
PRIVACY SUPPORT

Privacy Help Along The Cashier Path

A clear contact route matters when an account detail or wallet reference looks unfamiliar. Start from the account support path and include the phone number on your profile, the relevant date and the payment reference; we use those details to locate the correct record without asking for your wallet password. If you are in Denpasar, the same request path applies where local law permits.

Team online

Account data request

Ask us to identify the personal details connected with your account, explain their purpose or correct a phone number after completing the account verification step.

Wallet record question

For DANA, OVO, GoPay or QRIS questions, send the receipt reference through account support. We can check the matching record without requesting your wallet PIN.

Access concern

If a mobile browser session or login check blocks your request, mention the device path and time. We use that context to separate access security from policy handling.

DATA CONTROL

Speed Blackjack Data And Device Security

Privacy is handled through practical account controls rather than broad promises. We separate identity details from payment references where the process allows, limit staff access to the task being handled and record…

Account details

We use your phone number and verification result to connect you with the correct account. Keeping that information accurate helps us protect your login and answer a data request.

Payment references

DANA, OVO, GoPay and QRIS references identify a transaction record, not your wallet password. Bank transfer and virtual account details are handled for matching and account checks.

Cookies

Cookies and similar browser storage can remember a session setting or help us understand a security event. You can manage browser permissions, though some account steps may then need repeating.

Device signals

We may record device type, browser details and login timing to detect unusual access. These signals help us protect your account without treating them as a replacement for phone verification.

Retention period

We retain account, security and transaction records only as long as needed for the stated purpose, account administration or a lawful request. Ask support which category applies to your record.

Change request

To request correction, access or deletion where available, use account support and describe the record clearly. We may need to verify ownership before changing personal details.

Privacy Policy Questions For Your Account

These answers cover the searches we hear most often before an account is opened or a wallet record is checked. Our Privacy Policy applies to the details you submit, the security events created by your account path and the payment references needed to match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. Access depends on local law.

It covers account details, phone verification, device and login signals, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us confirm account ownership and distinguish your request from an unauthorised attempt. We may use the result when handling access, correction or data-change requests.

We do not ask for your wallet password or PIN to match a payment reference. DANA and OVO records are used as transaction context for account and receipt checks.

Use the account support path and state that you want a copy or explanation of your personal data. Include your profile phone number and complete any ownership check we request.

Yes, ask support to correct an inaccurate phone number or account detail. We may verify ownership first, and we will explain if a record cannot be changed because retention is required.

On a mobile browser, cookies may keep your session or help identify a security event. Browser controls can remove them, but you may need to repeat login or verification steps.

Retention depends on the record type and the reason it was collected, including account administration or a lawful request. Ask support for the applicable category and retention explanation.