Rujukan Laman

Open Your ac69 Privacy Choices

Our Privacy Policy explains what ac69 collects when you create or use an account, why we need each category, and how you can ask about it.

Clear data purposesCookie choicesAccount security
ac69 Open Your ac69 Privacy Choices
PRIVACY HELP DESK

Browse Privacy Help Channels

Questions about your personal data should have a clear route to a real response. Contact us through the account support channel or the privacy email route shown on ac69, and include enough account detail for us to locate the right record without sending passwords or full payment credentials. We may ask for reasonable identity checks before changing or disclosing account data.

Team online

Privacy email

Send a request about access, correction, deletion, consent, or processing purposes through the privacy contact shown on ac69. We will use your account details only to locate and answer the request.

Account support

Use the signed-in support channel when your question concerns a specific account record, cookie setting, security event, or message history. Avoid placing passwords, one-time codes, or complete payment details in your message.

Security contact

Report suspected account misuse or an unexpected data request through the security route shown on ac69. Include dates, device details, and safe contact details so we can check the event promptly.

HOW DATA IS HANDLED

Switch On Account Data Controls

Privacy choices work best when the handling behind them is visible. We separate account identity data from routine activity records where practical, restrict internal access by need, and use security checks when…

Collection purpose

We collect details that help create an account, provide account access, answer requests, prevent misuse, and meet applicable duties. Optional details are treated according to the choice presented when they are requested.

Cookie handling

Cookies can remember a session, retain a preference, measure page use, or help detect suspicious activity. You can manage browser permissions, although removing required cookies may affect sign-in and account security checks.

Account security

Sign-in events, device signals, and verification steps may be assessed together when access looks unusual. We may pause a request or ask for confirmation to reduce the chance of account data reaching the wrong person.

Payment records

Transaction references from Touch 'n Go, GrabPay, Boost dan FPX help us match a wallet event to your account. Payment providers may retain their own records, and their privacy terms apply to their handling.

Retention periods

We keep records only as long as needed for the stated purpose, account administration, dispute handling, security checks, or duties that apply to us. When a record is no longer needed, it is removed or protected from routine use.

Change requests

You can ask us to correct inaccurate details, explain processing, provide eligible copies, or consider deletion or restriction where applicable. We assess each request under the law relevant to your location and reply through a suitable channel.

Check Common Privacy Questions

The answers below cover the questions we expect when you are deciding whether to open an account or when you need help with an existing one. They summarise the policy in plain language, but the full Privacy Policy and applicable local law determine how a particular request is handled.

We may collect registration details, contact data, device and connection signals, account activity, support messages, payment references, and security verification records. The exact categories depend on the action you take and the purpose explained at collection.

Account details let us create and maintain your profile, while device and connection signals help protect sign-in sessions, identify unusual access, and troubleshoot requests. We use these categories for stated purposes rather than unrelated personal profiling.

Touch 'n Go, GrabPay, Boost dan FPX may send a transaction reference, status, amount, and time. We use matching details to identify an account event, resolve discrepancies, and maintain required records; each provider controls its own processing.

Yes. Contact the privacy route shown on ac69 with your request to access eligible data or correct an inaccurate record. We may verify your identity first, then assess the request against applicable law and retained records.

Send a deletion request through the privacy contact route. We will assess which records can be removed and which must remain for security, dispute handling, account administration, or legal duties. Access depends on local law and is available where local law permits.

Retention varies by record type and purpose. We consider account activity, security needs, unresolved questions, disputes, and applicable duties before removing or restricting routine use of data. The policy explains the factors used when a fixed period cannot be stated.

Contact the security route shown on ac69 as soon as possible, without sharing passwords or one-time codes. Tell us what happened, when you noticed it, and how we can reach you so we can check account access and respond.