Reference

Privacy Policy for Your togelup Account

togelup Privacy Policy explains what we collect when you open an account, sign in from a phone, or connect DANA, OVO, GoPay or QRIS.

Account clarityWallet recordsDevice controlsPolicy access
togelup Privacy Policy for Your togelup Account
HELP WITH PRIVACY

Get Privacy Answers Through Support

Questions about the Privacy Policy should reach the same support path used for account and wallet assistance, so we can locate the correct record without asking you to repeat the whole account story. Use live chat for a quick question about stored details or a payment reference, or send a support message when your request needs identity checking. We ask you to contact us from the email or phone connected to your account whenever possible.

Team online

Live chat

Use live chat when you need to ask where account details, device records or wallet references appear in our Privacy Policy. We may request a limited account identifier before discussing personal data, so another person cannot obtain details through a general chat.

Account message

Send an account message when you want to correct a phone detail, question a verification record or ask why a DANA, OVO, GoPay or QRIS reference is connected to your account. We check the request against the signed-in account before making changes.

Receipt check

If a payment receipt appears incorrectly, include its date, rail and reference rather than sending unrelated personal documents. Our support team can compare the receipt with the account ledger and explain what the Privacy Policy permits us to retain for reconciliation.

CONTROL YOUR RECORD

What You Can Ask Us To Change

We keep privacy requests practical: tell us which account detail, cookie setting, device record or payment reference you are asking about, and we will assess the request against…

Data collection

We collect account details when you create or verify access, plus device and browser signals when you sign in.

Cookie choices

Cookies and similar storage can keep a session active, remember basic page settings and help us see whether a login…

Account security

We use phone verification before account access and may compare device signals when a sign-in looks unusual.

Retention period

We retain account, payment and support records for as long as needed for service operation, dispute handling, security checks or…

Correction request

You can ask us to correct inaccurate contact or verification details by naming the field that needs changing.

Privacy contact

For a copy, deletion question or explanation of stored data, contact support through the signed-in account path and state that…

Privacy Policy Answers Before Account Access

These Privacy Policy answers address the practical questions we hear before an Indonesian account is opened or a wallet is connected. We explain what happens during phone verification, why a device may be recognised, how payment references are used and where to send a correction or deletion request. If your situation is unusual, contact us through live chat or the signed-in support path and mention the specific record involved.

It covers account details, phone verification, device and browser signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, correction requests, security checks and how to contact us about personal data.

Phone verification helps us confirm that the person opening or accessing an account controls the contact route provided. It supports account recovery and reduces mistaken changes to wallet status. We use the verification record for those account and security purposes, subject to the Privacy Policy.

Yes. The policy covers payment references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use these records to match account events, reconcile receipts and answer support questions, not to request unrelated personal details.

We may use device, browser and cookie signals to keep a signed-in session working, remember basic settings and identify unusual access. You can restrict cookies in your browser, but some account steps may require another login. The Privacy Policy explains these uses and their limits.

You can ask us to correct inaccurate account, contact or verification details through the signed-in support path. State the field that is wrong and provide only necessary context. We may verify account ownership before editing the record, then confirm what was changed or why it must remain.

You can submit a deletion request through support and identify the account concerned. We assess it against active account needs, payment reconciliation, dispute handling, security checks and legal retention duties. Where local law permits, we remove or anonymise eligible records and explain any information that must remain.

Use live chat for a short question or send an account message when you need a record checked. Contact us from the phone or email connected to your account where possible, mention Privacy Policy, and include the payment rail or device issue only when it helps locate the request.