Rujukan Laman

Privacy Policy for Your i1kiss918 Account

This page explains how we collect, use, store and share account data for your i1kiss918 access, including device logs, cookies and contact details you send us.

Account dataCookiesRetentionLocal law
i1kiss918 Privacy Policy for Your i1kiss918 Account
CONTACT PATHS OPEN

How to Reach Us About Privacy

For privacy matters, use the contact paths listed here and send the exact request you want us to handle.

Email request Send your request from the email linked to your account, and tell us which…
In-account form Use the in-account form when you want one thread that stays attached to your…
Document check If we need extra proof before changing sensitive details, we may ask for a…
DATA HANDLING STEPS

How We Handle Data and Access

We keep privacy handling narrow: collect only what helps with account access, support, safety checks and legal duties; use cookies for sign-in and preference memory; and limit staff access to the people…

Collection scope

We collect the details you enter, the messages you send, login times, device data and cookie IDs. That set helps us recognise your account, answer support requests and keep a clear record of changes you ask for.

Cookie use

Cookies remember your sign-in state, language choice and page settings. They also help us spot repeated login attempts and keep a session open while you move between pages, so you do not need to start over each time.

Access control

Only staff who need the record for support, safety checks or legal handling can see it. We keep logs of access, and we limit internal permissions so a broad team cannot open private account files.

Retention periods

We keep account records only as long as we need them for your active profile, dispute handling, audit checks and lawful requests. After that, we remove them or strip the parts that identify you.

Change requests

If you want a correction, a copy of your data, or removal where local law permits, send the request through the contact route on this page. We confirm identity first so the right record is changed.

Payment records

When a payment reference appears in your file, we keep only the details needed to match the transaction, settle a query and meet record-keeping duties. We do not store more than the purpose requires.

Privacy Policy Questions You May Ask

These answers cover the policy points people ask about most: what we collect, how cookies work, how long we keep records, and how you can ask for a correction or copy. If your request depends on a local rule, we follow the rule that applies and explain the next step before any change is made. You can use the contact route on this page or the in-account form after login, whichever is easier for you.

We keep the details you enter, plus login and device signals that help us manage access, support and security checks. If you add payment references, we store only what is needed to match the record.

Yes. Cookies remember sign-in state, language choice and session settings, and they help us detect repeated logins from the same device. You can clear them in your browser, though some pages may ask you to sign in again.

Yes. Send the request through the contact path linked to your account, and we will confirm your identity before sending anything. We may redact parts that must stay private or stay on file for legal reasons.

Yes. Tell us which field is wrong and what the correct version should be, and we will update it after our checks. If a record must stay unchanged for verification or legal handling, we will say why.

We keep records only while they are needed for account service, dispute handling, audits or lawful requests. After that period, we remove them or strip identifying parts, so older files do not remain longer than needed.

Only the staff handling privacy, support or legal requests can see the case file. We keep the route narrow, and we use the contact details attached to your account so replies go to the right place.

Yes, it applies to your account where local law permits. If the rule in your area changes what we can collect or show, we follow the stricter rule for that request and tell you the outcome.