Reference

kantortoto Privacy Policy for Your Data

Our kantortoto Privacy Policy explains what we collect when you create an account, complete phone verification, open the lobby on mobile, or use DANA and QRIS.

Account clarityWallet recordsMobile privacyRequest access
kantortoto kantortoto Privacy Policy for Your Data
CONTACT ROUTES

Where To Ask About Privacy Policy

A clear contact route helps when you need to understand a record tied to your account. Start from the support contact shown in your account area and state that your request concerns the kantortoto Privacy Policy. Include the phone number or account identifier you can safely provide, plus the relevant wallet reference if your question concerns DANA, OVO, GoPay or QRIS. We use that context to locate the correct record without asking for a wallet passcode.

Team online

Account support path

Use the support contact inside your account area for access, correction or deletion questions. We may ask for a phone verification step before discussing account-linked data.

Wallet record path

For a DANA, OVO, GoPay or QRIS query, share the transaction reference and date through the account support route. Do not send wallet passcodes or private security codes.

Privacy request path

Label your message as a Privacy Policy request and describe the action you want, such as a copy, correction or restriction. We will respond through the contact route linked to your account.

HANDLING PRACTICES

Six Ways We Handle Your Records

We keep this policy practical by tying each data use to a visible account step. Phone verification supports account access, wallet references help reconcile a transaction, and device details help us recognise…

Account identity

We use your account details and phone verification result to connect the right person to the right account record before access. This reduces mistaken matches between similar wallet references.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create transaction references. We use those references to reconcile status with your account, not to request wallet passcodes.

Device signals

When you move from a mobile browser to desktop, basic device and session signals may help us identify unusual access. These signals support account security and are assessed under our retention rules.

Cookies

Cookies can keep a signed-in session consistent and remember necessary page settings. You can manage browser cookie controls, although restricting required cookies may affect access to account pages.

Retention

We keep account, transaction and support records only while they serve operational, security, dispute or legal purposes. After that period, we assess deletion, anonymisation or restricted storage.

Your requests

You can ask for a copy, correction, deletion or use restriction where available. Contact us through the account support route, describe the record, and complete any identity check needed to protect your account.

Privacy Policy Questions About kantortoto

These Privacy Policy answers cover the account and wallet questions you are most likely to have before opening an account. We focus on phone verification, mobile access, cookies, payment references and request steps so you can decide what to share. If your situation is different, use the support contact shown in your account area and mention the exact record or transaction involved.

It covers account details, phone verification, device and session signals, cookies, payment references, support records, retention and requests for access, correction, deletion or restriction where available.

No wallet passcode is needed for transaction matching. We may record the selected rail, reference, amount, status and timing for DANA, OVO, GoPay or QRIS activity linked to your account.

Phone verification helps connect account access to the correct account record. It also supports identity checks when you ask about private data or request a change to account-linked details.

Yes. The policy applies when you access the account and lobby through a mobile browser or desktop browser. Necessary cookies and session signals may support continuity between permitted sign-in steps.

Use the support contact displayed in your account area, label the message as a Privacy Policy request, describe the records sought, and provide safe account context for identity confirmation.

Yes, you can request correction of inaccurate account-linked data. Tell us which field is wrong and provide the updated detail through the account support route so we can assess the request.

We retain payment references and related account records while needed for operations, security checks, disputes or legal duties. We then assess deletion, anonymisation or restricted storage under this Privacy Policy.