Reference

Privacy Policy for Your kiss918 Account

Your Privacy Policy gives you a clear account-data path before you open an account: what we collect, why DANA, OVO, GoPay and QRIS checks need certain details, and…

Account data scopeCookie choicesDANA and QRIS checksSupport privacy channel
kiss918 Privacy Policy for Your kiss918 Account
CONTACT ROUTES

Three Ways to Reach Privacy Support

Privacy questions should not sit in a normal game queue, so we give you direct paths for account-data requests. Live chat runs from 10:00 to 24:00 WIB for quick identity checks and status questions. Email works for longer requests, attachments, or legal data queries. The account form is the cleanest route when you are logged in, because we can match the request to your profile without asking for extra proof.

Team online

Live chat privacy triage

Use live chat from 10:00 to 24:00 WIB when you need a quick privacy status check. We may ask for your account ID and recent wallet reference, but never ask for your password.

Email privacy desk

Send detailed requests to [email protected] when you want a copy, correction, or removal check. Include your account ID, registered contact, and payment rail involved, such as OVO or GoPay.

Account privacy form

After login, go to Profile > Privacy Request and choose copy, correction, or removal. This route ties your request to the account session and reduces follow-up questions from our team.

SECURITY CONTROLS

Six Controls Behind Your Account Data

Six controls keep this policy practical rather than vague. We separate account details, wallet records, cookies, session logs, retention checks, and change requests so you can see which team handles each privacy…

Account details

We ask for the details needed to create and protect your account, such as account name, registered contact, login time, and security flags. Extra documents are requested only when an account-data request needs proof.

Payment records

DANA, OVO, GoPay and QRIS records help us match wallet activity to your account. We store reference codes, status, time, and amount so privacy requests do not break payment reconciliation.

Cookie choices

On Android Chrome, go to Settings > Site settings > Cookies. On iOS Safari, use Settings > Safari > Advanced > Website Data; changing cookies may log you out.

Game session logs

Session logs for Live Roulette, Rocket Crash, Bingo, and similar rooms record timestamps, round IDs, device signals, and error events. We use them for account security, dispute checks, and service fixes.

Retention checks

We keep privacy records for account operation, payment checks, security investigation, and legal request handling. When a record is no longer needed and where local law permits, we remove or mask it.

Change requests

Ask us to correct outdated contact details, check wallet-linked records, or remove eligible data. We verify your account before any change, then reply through the same channel you used.

Privacy Policy Questions You May Search

The questions below focus only on how our Privacy Policy works for your account. They cover account data, payment records, cookies, internal access, retention, and request steps. If your question includes a payment reference, include the DANA, OVO, GoPay, or QRIS receipt code when you contact us so we can locate the right record faster.

We collect your account name, contact details, login timestamps, device signals, and wallet receipt references. These fields let us protect access, reconcile DANA or QRIS activity, and answer privacy requests tied to your account.

No. We do not sell your personal data. We use it to run your account, verify wallet records, protect login access, answer privacy requests, and meet legal or payment-related record duties.

We store payment rail name, reference code, time, amount, account match, and transaction status. These records help us confirm wallet activity, resolve privacy questions, and avoid changing the wrong account record.

Yes. Send the request through Profile > Privacy Request, live chat, or [email protected]. We verify your account first, then correct eligible data or remove it where local law permits.

Cookies keep your session active, remember basic preferences, and help us spot unusual access. You can change them in Android Chrome under Settings > Site settings > Cookies, or in iOS Safari website data settings.

Only assigned teams can access account data for support, wallet checks, security, and privacy requests. Access is role-based, and sensitive requests require identity checks before we share or change records.

Retention depends on the record type. Account, payment, security, and legal request records may be kept while needed for operations or disputes, then removed or masked when no longer required.