Reference

totogp Privacy Policy For Your Account

The totogp Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesContact requests
totogp totogp Privacy Policy For Your Account
HELP WITH PRIVACY

Contact Us About Your Privacy Policy

A privacy question should not leave you searching through payment screens. From your account, use the support route near the cashier area and describe the exact request, such as correcting a phone number, asking about a QRIS receipt or checking why a verification record is retained. We will use the account details you provide to locate the relevant case and keep the response focused.

Team online

Account request

Send a correction, deletion or access request from the account linked to your totogp profile. Including the affected phone number helps us locate the right record without asking for unrelated wallet details.

Wallet question

For DANA, OVO, GoPay or QRIS privacy questions, include the transaction reference rather than a wallet password. We can then check the record category and explain why that reference appears in your account history.

Device concern

If a shared phone, browser cookie or unfamiliar login raises a privacy concern, tell us the device path used, such as mobile browser or desktop. We can direct the account-security steps that fit your case.

DATA HANDLING DETAILS

Six Practical Privacy Controls

Privacy is handled through account steps rather than broad promises. We separate identity checks, wallet references, device signals and support messages so each record has a clear purpose.

Account creation

We collect the details needed to create and verify your account, including a phone number where required. Clear phone verification helps connect your request to the correct profile before we discuss private account records.

Wallet references

DANA, OVO, GoPay and QRIS references help us reconcile a payment event with your account. We use the reference and status data for processing, support checks and record accuracy, not as a general profile.

Cookies

Cookies can remember session settings and help us identify unusual sign-in behaviour. Your browser controls can remove stored cookies, although clearing them may require you to complete account verification again.

Mobile security

On a mobile browser, we may record device and connection signals linked to sign-in activity. These signals help us investigate account access from an unfamiliar phone without reading unrelated files on your device.

Retention periods

We retain account, support and transaction records for different periods because each serves a different purpose. A deletion request is assessed against open cases, security needs and legal duties before we confirm the result.

Change requests

You may ask us to access, correct or delete eligible personal data through account support. We may request account verification first, protecting your records from a change submitted by someone else.

Privacy Policy Questions From Indonesia

These answers address the privacy searches we hear most often before an account is opened. They explain how our records connect to account verification, local wallets, cookies, device access and support requests. If your situation involves a specific transaction or phone, use the account contact path so we can check the relevant record rather than give a general reply.

The totogp Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and wallet references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create or verify the account, connect privacy requests to the correct profile and reduce mistaken disclosures. We do not treat phone verification as permission for unrelated data use.

Yes. The Privacy Policy covers QRIS, DANA, OVO and GoPay references linked to your account, including status and reconciliation details. A reference helps us investigate a payment record without requesting your wallet password.

You can request a correction through account support, preferably while signed in to the affected profile. Tell us which detail is wrong, such as a phone number, and we may verify ownership before changing it.

Cookies may keep a session active, remember settings and help identify unusual sign-in behaviour. You can remove them through your browser, but doing so may sign you out or trigger phone verification on your next visit.

Retention varies by record type. Account, transaction, security and support records may follow different periods because they serve different purposes. We assess deletion requests against open cases, security needs and legal duties.

You may send a deletion request through account support, and we will assess which records are eligible. Some data may need to remain for security, dispute handling or legal duties where local law permits.