Reference

Open tokohoki Privacy Policy with Account Clarity

The tokohoki Privacy Policy explains what we collect when you create an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice choicesCookie controls
tokohoki Open tokohoki Privacy Policy with Account Clarity
ACCOUNT HELP ROUTE

Ask About Privacy Beside Your Wallet Path

A clear contact route matters when you want to understand a receipt, device record or account detail. Our support path keeps privacy questions close to the account-help and cashier areas, so you can identify the relevant sign-in step before sending a request. Include your account identifier and the subject of your request, but never send a password or wallet PIN.

Team online

Account access questions

Use the account-help path when you need to know which phone verification detail is linked to your tokohoki access or why a security check appears on a new mobile device.

Wallet record questions

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, identify the transaction status and date so we can locate the correct payment reference without requesting your wallet PIN.

Privacy change requests

Ask us to correct, access or delete eligible personal details through the privacy contact route. We may verify account ownership before changing records or disclosing data.

DATA HANDLING DETAIL

Explore How tokohoki Handles Your Details

Privacy choices work best when you can see the operational reason behind each record. We separate account identity, payment references and device signals, then apply access checks before discussing account-specific details.

Account data use

We use the contact and verification details you submit to create access, confirm account ownership and respond to account-help requests. We do not need your wallet PIN to discuss a payment reference.

Payment references

A DANA, OVO, GoPay or QRIS record can include a reference, amount status and time. Bank transfer and virtual account records help us match a receipt without exposing unrelated account activity.

Mobile device signals

When you move from login to a lobby on mobile, security signals may record device and session details. These checks help identify unusual access and may appear again after a device change.

Cookies and choices

Cookies can remember a session setting and help us understand account navigation. Your browser controls can limit cookies, although changing them may affect sign-in continuity or saved preferences.

Retention approach

We keep personal records only for the periods needed for account operation, payment matching, security checks and applicable legal duties. The Privacy Policy explains the factors used for each retention period.

Correction requests

If your contact detail or account record is inaccurate, send a correction request through the privacy contact route. We check ownership first, then update eligible data and explain any limitation.

Browse tokohoki Privacy Policy Answers

These questions address the privacy searches we hear most often before account access. Each answer points to a concrete record, device action or contact step, so you can decide what to ask before using the account path where local law permits.

It covers account details, phone verification, sign-in and device records, cookies, payment references and support requests. It also explains retention, sharing for service operation, and available requests for access or correction.

Yes. The Privacy Policy explains that wallet activity may create a payment reference, status and time record. It also covers bank transfer and virtual account references used to match an account transaction.

We may record session and device signals alongside your account identifier to protect access. These details help us notice an unusual login or a device change when you move from login to the lobby.

Send an access request through the privacy contact route and include your account identifier plus the records you want located. We verify ownership before discussing account, device or payment-related details.

Yes, where local law permits. Tell us which contact or account detail is inaccurate through the privacy contact route. After an ownership check, we update eligible records or explain why a limit applies.

Cookies can keep a sign-in session and remember selected settings while you move between account pages. Browser controls can restrict them, but this may interrupt access continuity or remove saved preferences.

Retention depends on the record and the reason it exists, such as account operation, payment matching, security or legal duties. The Privacy Policy explains those factors and the available contact route.