Reference

Privacy Policy For Your tokkewin Account

tokkewin keeps its Privacy Policy close to the account steps you actually use, from phone verification through wallet status and lobby access.

Account dataWallet recordsCookie choicesAccess requests
tokkewin Privacy Policy For Your tokkewin Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

A privacy request should be easy to connect with the right account record. We ask you to use the support path linked to your tokkewin account and describe the request clearly, such as a correction to phone details, a question about QRIS receipt data, or a request about cookies on your mobile browser. We may need account verification before discussing personal details, so another person cannot obtain your records.

Team online

Account privacy request

Tell our support team whether you need access, correction, deletion, or a clarification about your Privacy Policy rights. Include the account step or record involved, but do not send a password or wallet PIN.

Wallet record question

For DANA, OVO, GoPay or QRIS questions, share the relevant date and receipt reference through the account support path. We use those details to locate the payment record without asking you to disclose unnecessary personal data.

Device access concern

If a mobile browser shows an unfamiliar session or a cookie prompt behaves unexpectedly, contact us through account help. We can first verify the account and then explain which access record or cookie setting relates to your concern.

DATA HANDLING DETAILS

What We Keep And Why It Matters

We write this Privacy Policy around the information needed to operate an account and answer a real support question.

Account creation

During account creation, we collect the details needed to create your profile and complete phone verification before account access. Our Privacy Policy explains the purpose of each required field, while optional details should not be requested without a stated reason.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, status and receipt trail. We use that trail to match a payment question to your account, investigate a mismatch and prevent another person from changing the record.

Cookies and sessions

Cookies may keep a login session working, remember a choice or help us identify a browser error. You can manage browser cookie settings, but restricting them may affect account access or require you to repeat a verification step.

Mobile device signals

When you move from login to the lobby on a phone, limited device and connection signals can help us detect unusual access and diagnose loading problems. They are handled as account security data, not as a reason to collect unrelated device content.

Retention decisions

We consider the account relationship, payment reconciliation, security checks and an active dispute when deciding how long a record stays available. A deletion request may be limited where keeping a specific record is required by local law or needed to protect account integrity.

Changes and contact

You can ask about a personal detail, request a correction, or question a Privacy Policy use through the support route connected with your account. We verify the requester first, explain any limit, and record the outcome so the same issue does not need to be repeated.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and payment questions we expect you to have before opening access. They cover the records created by phone verification, DANA, OVO, GoPay and QRIS, plus cookies, mobile sessions and requests made through support. Where a legal or eligibility condition applies, access depends on local law.

The tokkewin Privacy Policy covers account details, phone verification, payment references, device signals, cookies, security events, retention and requests about your data. It applies to the information created when you access the account, check wallet status or contact support about a record.

We use phone verification to connect the account to the person completing the access step and to reduce mistaken or unauthorised account changes. The Privacy Policy describes this use and the related security record; account access depends on local law and the checks shown during registration.

Yes. Privacy Policy treatment includes the reference, status and receipt details created when you use DANA, OVO, GoPay or QRIS. We use those records to reconcile an account question, investigate a missing status and support a payment check without requesting your wallet PIN.

Cookies can keep a session active, remember a browser choice and help us diagnose an access problem. You can change cookie controls in your browser, although blocking required cookies may send you back to login or repeat a verification step before the account opens.

You can contact support through the account-linked route and request access, correction or removal of eligible personal data. We verify your identity before discussing the record. Some payment, security or legal records may need to remain available where local law permits.

The Privacy Policy does not promise one fixed period for every record. We consider why the data was created, including phone verification, wallet reconciliation, security review or an open dispute, then retain it only while an operational or legal need applies.

Yes. Use the support path connected to your account and state whether your concern involves account data, a DANA or QRIS receipt, a cookie, a mobile session or another Privacy Policy point. Include only the details needed to locate the record, never your password or wallet PIN.