Rujukan Laman

Privacy Policy For Your Account

This Privacy Policy explains what sking666 collects, why we use it, how we protect it and how you can ask about your personal data.

Clear data purposesAccount security controlsMalaysia payment context

Explore the Lobby Read FAQ

How We Handle Account Data

sking666 Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

We collect details you submit when opening or using an account, such as your name, contact details, login credentials and records of requests sent to support. We may also receive device type, browser data, approximate location, session activity and technical logs needed to keep access secure.

1
Payment records can include the selected method, transaction reference, amount, status and timestamps, while sensitive payment credentials remain with the relevant payment service. We use this material to provide account access, confirm transactions, detect unusual activity, answer requests, maintain service records and meet duties that apply
2
under local law. We do not sell personal data for third-party advertising. Access and eligibility depend on local law and are available where local law permits. The exact data held can vary according to the account actions you take and the payment method selected.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

PRIVACY CONTACTS

Reach Us About Your Privacy

Our support paths are available for questions about this Privacy Policy, account records, cookie choices or a request to correct personal data. Include the email or account identifier linked to your profile so we can locate the right record without asking you to send passwords or full payment credentials. We may ask for reasonable proof of identity before discussing private account details.

Team online

Privacy email

Send a request through the privacy contact address shown in your account area. Tell us which record you want checked, corrected or removed, and we will reply using the contact details attached to your profile.

Account chat

Use the support chat when your question concerns a session, cookie setting or account-access record. Our team may ask security questions before sharing details, so another person cannot obtain private data through a chat request.

Security concern

Tell us promptly if you suspect unauthorised account access or a privacy issue. Do not send your password, one-time code or complete payment credentials; describe the event and the device involved instead.

DATA PRACTICES

Six Ways We Protect Privacy

Privacy work continues after an account is created. We separate login controls from payment references, restrict internal access according to work needs and record key account events so unusual activity can be…

Data collection

We request account details needed for registration, access, support and transaction handling. Technical records help identify failed sessions, unusual sign-ins and device faults without requiring us to read private content outside the stated purpose.

Cookie choices

Essential cookies keep sign-in and security checks working. Optional cookies may measure page performance or remember preferences. You can adjust browser controls, but blocking essential cookies can prevent parts of your account from opening correctly.

Account security

Login credentials are protected through access controls, session checks and technical safeguards. We may challenge unfamiliar devices or activity patterns. Keep your password and one-time codes private because our team will not ask for them.

Payment records

For Touch 'n Go, GrabPay, Boost dan FPX, we retain method names, references, status and timing needed to match deposits or withdrawals. Full wallet or banking credentials are handled by the relevant payment service.

Retention periods

We keep records only as long as needed for the stated purpose, account support, security checks or duties under local law. When a record is no longer needed, it is deleted, anonymised or securely restricted.

Requests and changes

You can ask what personal data we hold, request a correction, question its use or ask about deletion where local law allows. We may retain limited records when a legal or security reason requires it.

Privacy Questions We Answer

The answers below summarise the practical points most relevant to your sking666 account. They explain what may be collected, how requests are checked, why payment references remain available and where local law affects access, retention or deletion. Contact support when your situation needs a record-specific response.

We may collect your account name, contact details, login records, support messages, device signals, approximate location, session logs and payment references. The amount collected depends on which account functions and payment options you use.

Device type, browser version, IP-related signals and session events help us keep accounts secure, identify failed access and investigate unusual activity. These records also help technical support reproduce faults without requesting unnecessary personal details.

For Touch 'n Go, GrabPay, Boost dan FPX, we may retain the method, transaction reference, amount, status and timestamp. Full wallet or banking credentials are not required for our records and remain with the payment service.

Yes. Contact the privacy path linked to your account and state whether you want access to a record or correction of an error. We may verify your identity first, and local law can affect the response.

Send a deletion request through support with your account identifier and the records concerned. We assess the request under local law because some security, transaction or account-history records may need to remain for a stated period.

We compare the request with contact details and account signals already held, then may ask additional questions. Never send a password, one-time code or complete payment credential when asking about your personal data.

Yes, it covers personal data connected with supported Malaysia access, including local payment references. Access and eligibility depend on local law and are available where local law permits, so certain rights or retention rules may vary.

Privacy Policy For Your Account

Reach Us About Your Privacy

Privacy email

Account chat

Security concern

Six Ways We Protect Privacy

Data collection

Cookie choices

Account security

Payment records

Retention periods

Requests and changes

Privacy Questions We Answer

01 What personal data does sking666 collect?

02 Why do you need device and session details?

03 What payment details are retained?

04 Can I request a copy or correction?

05 How can I ask for data deletion?

06 How are privacy requests verified?

07 Does this policy apply to Malaysian access?

Related Pages