Reference

kikislot Privacy Policy for Your Account

kikislot Privacy Policy shows how we handle the account, wallet and device details connected with your use of our lobby.

Account recordsWallet activityDevice choicesCookie controls
kikislot kikislot Privacy Policy for Your Account
CONTACT ROUTES

Check Privacy Policy Questions Through Support

A clear contact path matters when your account record or wallet reference does not look familiar. We keep privacy questions close to the account support route, so you can ask what data is linked to your login, why a verification step appeared, or how a receipt was matched. Include the account identifier shown in your profile, but never send a password or full wallet credentials.

Team online

Account privacy request

Open the support path from your account and state that your request concerns the Privacy Policy. We use the account identifier to locate the relevant record before discussing access or changes.

Wallet data question

If a DANA, OVO, GoPay or QRIS reference seems incorrect, send the visible transaction reference and date through support. We can check the status without asking you to reveal a wallet password.

Login record concern

When a device or login event looks unfamiliar, contact support from the account path and describe the device behaviour. We may ask for an account verification step before changing access details.

DATA PRACTICES

Browse How kikislot Handles Privacy Details

The privacy process is designed around specific records rather than broad collection. We separate account details from payment references where the operating process allows, use security checks to protect access, and keep…

Data we receive

We may receive account contact details, verification outcomes, login timestamps, device signals and support messages. Payment rails provide references and status data, such as a QRIS receipt, rather than a request for your wallet password.

Cookie choices

Cookies and similar device storage can remember sign-in preferences and help us detect unusual access. Your browser settings provide a control point, although changing them may affect account recognition or policy display.

Account security

Clear phone verification before account access helps connect the right person to the right account. We may compare login and device signals when activity changes, then request another account step before making sensitive changes.

Retention timing

We retain records only for as long as needed for account operation, payment matching, dispute handling, security checks or legal duties. The Privacy Policy explains the purpose behind each retention category rather than using one blanket period.

Correction requests

If your contact detail or account record is wrong, ask support to review the specific field. We may confirm ownership through the account path before correcting it, so another person cannot alter your profile.

Who receives a request

Privacy questions start with our account support route. We may direct a request to the team handling security, wallet reconciliation or records, while keeping the request connected to your verified account.

Find Answers About Privacy Policy Access

These Privacy Policy answers address the account and wallet questions you may have before opening an account. We keep the wording practical: what we collect, how you can ask for a change, what happens to device records, and how local access rules affect the process. If your situation is not covered, use the support route linked to your account.

It covers account details, phone verification, login and device records, cookie choices, support messages, payment references and retention. It also explains how to contact us about access, correction or deletion where local law permits.

Phone verification helps us connect account access to the correct person and reduce mistaken or suspicious logins. We may use the result for account security, while the Privacy Policy explains its handling and retention.

Yes. It covers the transaction reference, status and timing linked to DANA, QRIS, OVO, GoPay, bank transfer or a virtual account. We use those details to match account activity without requesting your wallet password.

Use the support route inside your account and identify the exact record you want corrected or removed. We may ask for an ownership check before acting, and the available outcome depends on local law.

We may store device type, browser signals, login time and related security events to recognise unusual access. These records help protect your account and are handled according to the retention wording in the Privacy Policy.

Retention depends on the purpose, such as account operation, payment matching, security, dispute handling or legal duties. The Privacy Policy describes those purposes, and support can clarify a record connected to your account.

Yes. State that you want the handler or status of a Privacy Policy request when contacting support. We first verify the account context, then explain which team is reviewing the account, wallet or security record.