Rujukan Laman

Open your privacy choices clearly

Your Privacy Policy explains how dfbocai handles account data, wallet checks, cookies, device records, and support chats before you open an account.

Account dataCookie choicesWallet checksSupport records
dfbocai Open your privacy choices clearly
CONTACT PATHS

Start a privacy request with us

If you want to ask about access, correction, deletion, cookies, or account records, contact us through the same support routes used for your account. We may ask you to confirm control of your email, phone number, or wallet record before we act on a privacy request.

Team online

Live chat privacy queue

Use live chat when you are signed in and ask for the privacy queue. We can locate your account faster, confirm recent wallet activity, and tell you what records are needed before any data change.

Email privacy request

Send your request from the email linked to your account and include the topic you want checked. Avoid sending full card, bank, or identity images until our team asks through a secure channel.

Wallet record help

For Touch 'n Go, GrabPay, Boost dan FPX questions, share the transaction time, reference code, and amount. We use those details to match payment logs without exposing extra account records.

DATA CARE

Browse the safeguards behind privacy

Our Privacy Policy is written around the records we actually handle: account registration data, login activity, payment references, cookie signals, support chats, and verification files.

Account records

When you open an account, we collect details such as your name, contact number, email, login history, and account status. These records help us keep access consistent and respond when you ask for changes.

Payment references

Touch 'n Go, GrabPay, Boost dan FPX activity creates payment references, time stamps, and status results. We use those records to match deposits, verify withdrawals, handle reversals, and answer wallet privacy questions.

Cookie controls

Cookies help remember language, session state, device type, and security signals. You can manage browser cookie settings, but some account functions may need session cookies so we can keep your login active.

Security checks

We monitor login patterns, password resets, device changes, and failed access attempts. These checks help us detect account misuse, and the related records are kept only as long as required for security or legal reasons.

Retention periods

We keep records for different periods depending on their purpose. Support chats may be shorter, while payment, verification, and dispute records may be retained longer to meet audit, banking, or legal requirements.

Correction requests

If your contact details, name spelling, or wallet record looks wrong, ask us to check it. We may require proof before making changes, especially where payment history or identity checks are involved.

Check common privacy questions

These answers explain the main Privacy Policy points in plain terms, including what data we collect, how wallet records are used, how cookies work, and how you can contact us. For account-specific requests, we will still need to confirm that the account belongs to you.

We collect data you provide during account setup, support contact, wallet activity, and verification checks. This may include your name, contact details, login records, payment references, device signals, and documents you send when requested.

Wallet records help us match deposits, verify withdrawals, trace failed transfers, and answer payment questions. Touch 'n Go, GrabPay, Boost dan FPX references are handled as account records, not as public profile details.

We share data only where needed for account operation, payment processing, fraud checks, hosting, support, legal requests, or dispute handling. Partners receive the limited records required for their role and must handle them properly.

Contact us through signed-in live chat or the email linked to your account. We may ask for extra checks before releasing records, especially if the request involves wallet history, identity files, or security logs.

Yes, you can ask us to correct inaccurate contact details or profile records. Where the change touches payment history, withdrawal checks, or identity records, we may request supporting proof before updating the account.

Cookies help keep your session active, remember display choices, and detect unusual access patterns. If you block certain cookies, some account functions may not load correctly or may require repeated login checks.

Retention depends on the record type and legal need. Support chats may be kept for a shorter period, while payment, verification, dispute, and security records may remain longer for audit and compliance reasons.