Reference

topanhoki/ Privacy Policy: Your Data, Wallets and Account

Our Privacy Policy explains how topanhoki/ handles your account details, wallet status and device data when you use the lobby in Indonesia.

Account dataWallet choicesCookie controlsContact route
topanhoki.click page image
PRIVACY HELP

Privacy Questions Near Your Account

A clear contact path matters when a privacy request meets a login or wallet question.

Account contact route Open the account support area and choose a Privacy Policy request. We use your registered phone number to locate the correct profile before discussing stored details.
Payment record check For DANA, OVO, GoPay or QRIS questions, provide the transaction reference and date. We compare that record with the account history without requesting your wallet password.
Access correction request If a phone, device or account detail is wrong, tell us which field needs correction. We may ask for an account step to confirm that the request is yours.
DATA HANDLING

Your Data Path Inside topanhoki/

We separate account service data from the details needed to investigate a payment or security event.

Account details

We use your phone number and submitted account fields to create access, confirm changes and respond to requests. Keeping these details current helps us send a privacy reply to the right account.

Device and session data

Browser, device and sign-in records help us recognise unusual access and investigate a locked session. The mobile lobby can use these records without reading unrelated files on your device.

Cookies

Cookies can preserve sign-in flow, remember selected settings and connect a support visit with the correct session. You can manage browser cookie controls, though some account steps may then need repeating.

Account security

Phone verification and recent account activity may be checked before we discuss private details or change account data. Never send us your wallet password, full card secret or one-time code.

Retention period

We keep records for as long as needed for account service, security checks, payment tracing, disputes or legal duties. When a record is no longer needed, our handling follows the applicable retention process.

Data change request

Ask us to correct, access or clarify your stored data through the account support route. State the requested action and registered phone number so we can verify ownership before replying.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the account steps people ask about before opening access or using local wallets. We keep the response practical: what data is collected, why a verification step appears, how cookies work and where to send a request. If eligibility or access applies, it depends on local law.

It covers account details, phone verification, device and session records, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us connect an account request to its owner before access, profile changes or private account details are discussed. It also supports checks when a sign-in pattern appears unusual.

No. For a DANA, OVO, GoPay or QRIS status check, we use the payment reference, date and result supplied through the rail. We do not ask for your wallet password.

Use the privacy contact route inside your account and request access to your stored data. Include your registered phone number and the categories you want checked so we can verify ownership.

Yes. Send a correction request through account support, identify the incorrect field and explain the requested change. We may complete a phone or recent-activity check before updating the record.

Cookies can keep your sign-in path, selected settings and support session connected. Browser controls can remove or restrict them, but some account steps may need to be completed again.

Open the account support area and select a Privacy Policy request. Share your registered phone number, request type and relevant reference, but never include a wallet password or one-time code.