Rujukan Laman

Your Privacy Policy at adinda55

Your account data, cookie choices and payment records are explained here in plain terms, so you can see what we collect, why we use it and how to…

Plain languageAccount dataCookie choicesLocal law
adinda55 Your Privacy Policy at adinda55
CONTACT PATHS

Privacy Help for Your Account

Privacy questions about your account have a direct route: use account chat or the contact form shown in our support area.

Privacy questions Use account chat for a question about collection, cookies or a message you received…
Data access requests Ask for a copy of personal data linked to your account through the contact…
Security concerns If you suspect an unrecognised sign-in or change to account details, contact support promptly…
DATA PRACTICE

How adinda55 Handles Personal Data

Our privacy work follows the same account path you use: collection at sign-in or payment, purpose checks before access is granted, security controls around stored records, and deletion or restriction when the…

Data collected

We collect details you provide, such as contact data and account preferences, plus device, connection and sign-in signals created when you access the service. We use these records for account operation, security, support and legal duties.

Payment records

Touch 'n Go, GrabPay, Boost dan FPX can return a reference, status or timing record for a transaction. We use that data to match your request, resolve a failed transfer and verify withdrawal instructions.

Cookies and choices

Cookies and similar storage help retain your session, language choice and security state. We explain necessary and optional uses in the policy, and you can manage available choices through your browser or the controls shown on the account page.

Account security

Sign-in events, device signals and verification steps help us detect unusual account access. When a withdrawal or account change needs checking, we compare request details with the account record and limit disclosure to authorised handling.

Retention periods

We keep each category only while it supports the stated purpose, an open account, a dispute, a security need or a legal duty. When the period ends, records are deleted, anonymised or restricted according to applicable law.

Requests and contact

You can ask for access, correction, deletion, restriction or a copy of your data through account chat or our contact form. Include details to locate the account; we verify identity, explain any limit and respond within the period required by local law.

Privacy Questions Before You Join

These answers cover the questions we hear before an account is opened or while records are being handled. They do not replace the full policy: if a conflict arises, the applicable policy wording and local law control. Access and eligibility remain dependent on local law and are available where local law permits. You can use the contact paths above for a request about your own data, cookie choice or account security event.

We collect details you submit for an account, records created by sign-in and device use, cookie choices, support messages, transaction references and verification documents where needed. The policy links each category to a defined purpose rather than unrelated use.

Transaction records help match deposits and withdrawals, investigate failed transfers, answer disputes and meet legal duties. Access is limited to the handling needed for those purposes, and retention ends when the applicable purpose or required period ends.

Yes, use account chat or the contact form and describe the account connected to your request. We verify ownership before release, provide the available data in a practical format, and explain any restriction required by local law.

Send the correction through support, stating which detail is wrong and what it should say. We may request a verification step, update the relevant record when confirmed, and tell you if another party must make the change.

Closing an account does not erase every record immediately. We remove or anonymise data when the stated need ends, while records tied to disputes, security events or legal duties may remain restricted for the period local law requires.

Necessary cookies can keep your session and security controls working, while optional cookies may remember preferences or help us understand account-page use. Check the cookie controls in your browser or account area to adjust choices where available.

Start with account chat or the contact form shown by support; your request is routed to the team handling privacy matters. Include a safe contact route and account reference, but do not send passwords or one-time security codes.