Reference

agentoto88 Privacy Policy For Your Account

Our Privacy Policy explains how agentoto88 handles the details you provide before account access, including your phone verification, wallet records and device sign-in history.

Clear data purposesWallet record contextAccount access controlsCookie choices
agentoto88 agentoto88 Privacy Policy For Your Account
CONTACT PATHS

Ask About Your Privacy Policy

You can raise a privacy question without explaining your whole account history in public. Start from the account support area, include the phone number linked to your profile, and describe whether your request concerns access, correction, deletion or a wallet receipt. We use the details in that request to locate the right record, and we may ask for an account step that confirms you are the person making the request.

Team online

Account privacy request

Send your question through the account support path and identify the specific data concern. We may request phone verification before discussing account records, wallet activity or sign-in details.

Wallet record query

For DANA, OVO, GoPay or QRIS questions, include the payment rail and receipt reference. This helps us separate a privacy request from a transaction-status question without exposing unrelated account data.

Access correction

If your name, phone detail or account access record is inaccurate, tell us what should change. We check the request against your account path before applying an eligible correction.

DATA HANDLING

What We Do With Account Details

Privacy choices matter most when they match the way an account actually works. We separate identity checks, wallet references, device signals and browsing preferences so a request can target the right record.

Account details

We use your phone number and verification result to connect sign-in activity with the correct account. This supports account recovery and helps prevent a private request being answered for the wrong person.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can show a payment reference, status and time. We use these details to trace receipts and resolve account-linked payment questions.

Device activity

When you move from mobile browser to desktop, technical sign-in details may differ. We use these signals for account protection and access checks, rather than treating every device as the same session.

Cookies

Cookies can remember settings and help us understand which policy or account page was opened. You can manage browser cookie controls, though some account functions may need essential session storage.

Retention

We retain records only for the stated account, payment, security or legal purpose, then assess whether they are still needed. A deletion request may not remove records that must be kept for those purposes.

Request changes

To request access, correction or deletion, contact us through the account support path with your linked phone detail. We verify ownership first and explain any limit that applies to the request.

Privacy Policy Questions For Indonesia

These Privacy Policy answers focus on the account situations you are most likely to encounter on agentoto88. They cover what we collect, how wallet records are used, what happens across devices and how to contact us when a request needs account verification. Where access or eligibility is discussed, depends on local law.

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

Phone verification helps connect your account access with the correct person. It can also protect privacy requests, so account details or wallet records are not disclosed to someone using another phone or session.

Yes. The Privacy Policy covers technical records from mobile browser and desktop sign-ins. A change of device can create different session details, which we may use for account protection and access checks.

We use payment references, status and timing to match a receipt with your account and investigate a stalled wallet step. We do not need unrelated account data to trace that specific request.

You can request access, correction or deletion through the account support path. We verify ownership first and explain if a record must remain for an account, payment, security or legal purpose.

Retention depends on the purpose for collecting the record. We assess whether account, payment, security or legal records are still needed, and a deletion request may not remove required records.

No. The policy explains data handling, not universal eligibility. Your access depends on local law, and you should check the account path and local requirements before providing personal details.