Reference

98 toto Privacy Policy for Your Account

Our Privacy Policy explains how 98 toto handles the account data you provide before you enter the lobby, including phone verification and wallet records.

Clear data purposesWallet record contextAccount access requestsCookie choices
98 toto 98 toto Privacy Policy for Your Account
CONTACT ROUTES

Privacy Help Beside Your Account Path

A privacy question should not leave you guessing which account route to use. We keep the contact path close to sign-in and wallet status help, so you can ask about a phone number, device record, cookie setting or payment reference without sending sensitive credentials in an open message. Include your account contact and the subject of your request; never send a password or wallet PIN.

Team online

Account data request

Ask us to locate the account data linked to your verified phone path. We may request account details to confirm that the request comes from you before replying.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, share the date and masked reference only. We use that context to trace the relevant account record.

Cookie support

Tell us which device and browser showed the issue. We can explain session cookies, sign-in storage and the practical effect of clearing them before you return.

DATA PRACTICES

How We Handle Account Data and Cookies

We separate the data needed to operate your account from optional browser signals used to keep a session working.

Account data

We may hold your verified phone contact, account settings, session history and support messages. These records help us respond to account requests and connect activity to the correct profile.

Wallet references

Payment records identify a route such as DANA, OVO, GoPay, QRIS, bank transfer or virtual account. We use references and status details, not your wallet PIN.

Cookies

Session cookies can keep your sign-in path available while you move through the lobby. Browser controls let you clear them, although a fresh account sign-in may then be required.

Device security

Device and session signals help us examine an unexpected account entry or repeated sign-in failure. They support security checks without giving us access to your private device content.

Retention

We keep account, support and wallet references for operational, security or legal needs. When a record no longer serves one of those purposes, we remove it or reduce its link to you.

Policy changes

To ask about a correction, deletion or policy change, use the account contact route and describe the request clearly. We may verify your identity before changing records connected to your account.

Privacy Policy Answers for 98 toto

These Privacy Policy answers focus on the account actions you are most likely to take: opening access, checking a wallet reference, using a mobile browser and asking us to change or remove data. We keep each answer tied to the records we actually need for account security and support.

It covers account details, phone verification, device and session signals, cookies, support messages and payment references from routes such as DANA, OVO, GoPay and QRIS.

Phone verification helps connect you to the correct account and allows us to check that a data request or sign-in concern comes from the account holder.

Yes. It explains how we handle route names, masked references, status details and related account records for DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity.

Cookies can remember a browser session and help identify sign-in errors. If you clear them, you may need to complete the account sign-in path again on your mobile or desktop browser.

You can contact us through the account privacy route and request the data linked to your verified contact. We may ask for identity checks before releasing account-specific records.

Yes, describe the correction or removal request and include the relevant account contact. We assess it against operational, security and legal record needs, and access depends on local law.

Use the support contact path connected to your account and select the privacy subject. For wallet records, provide only the date and masked reference; never send a password or wallet PIN.