Rujukan Laman

Privacy Policy for Your Malaysia Account

Before you open an account on kissed918, this page explains what we collect, why we use it, and how you can ask us to change it.

Personal dataCookiesLocal lawAccess requests
kissed918 Privacy Policy for Your Malaysia Account
HELP PATHS

Where to send privacy requests

If you want a copy of the details tied to your account, need a correction, or want us to explain a retention point, reach out through the channel that matches your login.

Live chat Open chat from your account area and tell us which detail you want checked. We use it for access, correction and deletion requests, then confirm the account match before we touch anything sensitive.
Email Use your registered email when you want a copy of stored fields, a note on sharing, or a question about retention. We may ask for a short verification step before we respond.
Privacy form Submit the form if you need cookie changes, a contact update or a complaint about how a record was used. If a local rule keeps a record in place, we will say so clearly.
HANDLING PRACTICES

How we protect your details

Our handling stays narrow: we collect account fields, device marks and payment traces only when they help with login, service delivery or dispute handling.

Collection limit

We ask only for the details needed to create, verify and maintain your account. Anything extra stays out unless a legal duty, a support case or a payment match makes it necessary.

Cookie use

Cookies remember your session, language choice and simple site settings. We also use them to spot repeated logins from unusual devices, which helps us keep account access under control.

Login safety

Your password stays private with you. We never ask for it by chat or email, and we use verification checks before any sensitive change is accepted on the account.

Retention

Some records stay longer when local law, dispute handling or account auditing requires it. Once the purpose ends, we remove or de-identify what we no longer need from our active systems.

Change requests

You can ask to correct a field, ask for a copy, or request deletion where the law allows it. We will tell you what can move and what must stay.

Contact trail

For every request, we keep a short trail of the channel used, the checks completed and the result sent back. That record helps us answer follow-up questions without exposing more than needed.

Privacy policy questions answered

These questions cover the parts you ask us about most: what we collect, how long we keep it, when we share it, and how you can ask for changes. If local law gives you a right, we follow that right and explain any limit that applies. When your account sits in Malaysia, the same policy language applies unless a legal rule needs a different treatment.

We collect the details needed to set up the login, verify contact fields, handle security checks and record any transaction trace tied to your account. We avoid asking for extra details unless a legal or support need appears.

Yes. Cookies keep your session open, remember simple settings and help us notice unusual access patterns. You can clear them in your browser, though some features may not remember your last choices after that.

Yes, you can ask for a copy through the contact route linked to your account. We will verify that the request comes from you, then return the details we are allowed to share.

You can ask us to correct a field or remove certain details where local law allows it. If we must keep a record for auditing, dispute handling or a legal duty, we will say so.

Only staff, processors and service partners that need them for account handling, security or payment matching can see the relevant parts. They are asked to use the data only for the task we set.

We keep records for as long as needed for service, dispute handling and any local legal duty. After that, we delete, de-identify or archive them according to the purpose they served.

Use chat, email or the in-account form from the details tied to your login. We will confirm the account link first, then answer the request on the same route or another allowed channel.