Reference

Privacy Policy for Your kerahoki Account

Our Privacy Policy explains what we collect when you open a kerahoki account, verify your phone and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesData requests
Explore Our Lobby Read FAQ
kerahoki Privacy Policy for Your kerahoki Account
CONTACT ROUTES

Get Help With Privacy Requests

A clear support route helps you ask about the Privacy Policy without repeating your account story. Open the support path beside the cashier area and include the phone number linked to your account, the subject of your request and any relevant receipt reference. We use those details to locate the correct record, while you should never send a password, wallet PIN or full banking credential.

Team online

Policy questions

Ask how we collect, use or retain account information through the support path. Include your registered phone number and the Privacy Policy topic you want clarified, and we will use the account record to keep the response relevant.

Wallet record checks

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the transaction date, amount reference and wallet name through support. We can compare the payment record with your account without asking for your wallet PIN.

Change requests

To request correction, access or removal of personal data, use the same support route and state the action clearly. We may ask for phone verification before changing account-linked details, so another person cannot alter your record.

HANDLING DETAILS

Six Practical Privacy Commitments

We keep the Privacy Policy practical by linking each data purpose to an account action you can recognise.

Account collection

We collect details needed for an account, including your contact information and phone verification result. We do not ask you to place a wallet PIN or banking password in a support message, and we use the account step to match records.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create references such as status, time and amount. We use these details to match a cashier action or receipt, not to request your private wallet credential.

Cookies and sessions

Cookies and session storage can keep sign-in choices, language settings and security signals on your browser. Clearing them may require phone verification again, especially when you switch from a mobile browser to desktop before opening the lobby.

Account security

We use sign-in events, device signals and phone verification to spot account access that does not match your normal path. If a security check pauses access, support can help after confirming details linked to your account.

Retention periods

We keep account, payment and support records for the period needed for account operation, security checks or applicable legal duties. When a record no longer serves one of those purposes, we remove it or separate it from direct account identifiers.

Your requests

You can ask what personal data we hold, request a correction, ask about deletion or question a processing purpose through support. We may need phone verification, and access or action depends on local law and the record involved.

Privacy Policy Answers for kerahoki

These Privacy Policy answers address the searches we hear most often before account access. They explain the records connected with wallets, mobile sessions, phone verification and support. If your situation is not covered, send a specific request through the account support path, and avoid including passwords, wallet PINs or full bank credentials.

The kerahoki Privacy Policy covers account details, phone verification, login and device signals, cookie choices, support messages and payment references. DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may be linked to your account when you use those payment paths.

Phone verification helps us connect an account request to the person controlling the registered number and helps protect changes to personal data. We may request it again after a new device, cleared cookies or an account security event.

Yes. When you access the lobby through a mobile browser, we may process browser, device and session signals needed for sign-in continuity and security. These signals are handled as account-access records, not as permission to inspect unrelated content on your phone.

We use payment references such as status, time and amount to match a cashier action or receipt with your account. We do not need your DANA or QRIS PIN in support messages. Send only the reference needed for a record check.

You can ask for access to personal data linked to your account or request a correction through support. Include your registered phone number and the precise record involved. We may verify account control first, and the available action depends on local law.

We retain account, payment and support records while they serve account operation, security checks or applicable legal duties. After that period, we remove them or separate them from direct identifiers where practical. Support can explain the category and purpose of a record.

Use the support route beside the cashier area and write the Privacy Policy subject you need clarified. For a wallet issue, include the payment name and reference, but never send a password, wallet PIN or full banking credential.

Related Pages

kerahoki Indonesia Pekanbaru Lucky Slots FAQ Lightning Roulette Room MotoGP Race Bet