Rujukan Laman

Open ez918kiss Privacy Policy

This page explains what account details we keep, why we use cookies, and how payment records move through Touch 'n Go, GrabPay, Boost dan FPX when you open…

Account detailsCookie choicesPayment recordsLocal-law access
Explore Lobby Read FAQ
ez918kiss Open ez918kiss Privacy Policy
CONTACT PATHS

Switch to our privacy contacts

If you want to ask about this policy, use the contact path linked to your account so we can check ownership before we discuss stored details.

Account inbox Send the request from the email or inbox linked to your account after sign-in. We use that path to confirm ownership before we change, copy, or remove any stored detail.
Live chat Use live chat for quick privacy questions about cookies, device records, or payment trails. We may ask for account checks before we continue, so keep your registered details ready.
Email reply If you prefer email, reply to our support thread with the same subject line and the exact request. That helps us trace your case and answer within the right account history.
KEEPING IT TIGHT

Browse our data and cookie care

We handle this policy area with a simple rule: collect the minimum needed, store it only for the time needed, and limit access to staff who need it for account work.

Collection limits

We collect account details, device signals, and payment records only when they are needed for registration, access, fraud checks, or support. Anything extra is left out of the record set.

Cookie control

Cookies help the site remember your session and settings. You can clear them in your browser, and some features may ask you to sign in again after that reset.

Account security

We protect accounts with sign-in checks, session time-outs, and alerts for unusual activity. If you suspect someone else has access, contact us from your linked channel at once.

Retention windows

We keep logs and transaction trails only as long as needed for the task, dispute handling, and legal duties. After that period, the records are removed or archived with limited access.

Change requests

You can ask us to correct a wrong detail, update your contact path, or delete a record where local law allows. We will check the request against the account before acting.

Shared access

If another service needs a record for verification or settlement, we share only the minimum field set, and only when a legal basis allows that transfer in Malaysia or the relevant place.

Open common privacy questions

These answers cover the points we hear most often: what we collect, why cookies appear, how to ask for a change, and when we may keep a record under legal duty. If your account uses Touch 'n Go, GrabPay, Boost dan FPX, the same policy rules apply to the payment trail and the support thread tied to that action. That keeps each request tied to the right file.

We collect the details needed to create the account, check logins, and connect wallet actions to the right file. That usually includes contact details, device signals, and payment records tied to your session.

Cookies keep your session active, save language or page settings, and help us spot unusual behaviour. You can clear them in your browser, but some parts may ask you to sign in again.

Yes. Send the request from the channel linked to your account and tell us which field is wrong. We will check ownership first, then update or explain any limit under local law.

We keep each record only for the period needed to run the account, handle disputes, meet audit duties, or meet legal duties. After that, we remove or archive it with limited access.

Only staff who need the details for account work, support, security checks, or legal handling can access them. When a service partner is involved, we share the smallest field set needed.

Use the account inbox, live chat, or email reply path linked to your profile. Add the page path, date, and action you want us to check so we can trace the request.

Related Pages

ez918kiss Malaysia ez918kiss Login ez918kiss Casino ez918kiss App Golden Colosseum