Reference

Privacy Policy For Your imb123 Account

Our Privacy Policy explains what account details we collect, why we use them and how you can ask about them before opening an account.

Clear data purposesCookie choicesAccount contact path
imb123 Privacy Policy For Your imb123 Account
POLICY HELP ROUTES

Where To Ask About Privacy Policy

A clear contact route helps you understand the Privacy Policy without guessing which account screen to use.

Account access Use the support contact shown in your account area when you need help locating the Privacy Policy or checking which profile details are attached to your login. Include your account identifier and the email or phone detail already connected to it, but never send your password.
Data request Ask us to correct, explain or remove eligible personal data through the available support route. We may request an account check before acting, because the request must come from the person connected to the record. We will explain any limit that depends on local law.
Receipt context For a privacy question linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, provide the reference and date rather than a full wallet credential. This lets us find the relevant record while keeping sensitive payment details out of ordinary messages.
DATA HANDLING PRACTICE

What We Do With Account Details

We handle personal data around the account actions you choose, rather than treating every device signal as a permanent profile.

Collection purpose

We collect details needed for account creation, phone verification, login support and transaction matching. Contact information can help us send an account response, while device and session signals can help identify an unusual access attempt. We aim to use each detail for a stated operational reason.

Cookie controls

Cookies and similar session tools can remember an active sign-in path, preserve page settings or help us understand a failed account step. Your browser controls whether some cookies remain. Removing them may require you to verify your phone or sign in again before access continues.

Security checks

Phone verification and account activity checks help us distinguish your normal login from an unfamiliar device. If a check pauses access, contact support through the account route and describe the device path. Do not disclose a password, wallet PIN or complete bank credential.

Payment references

A DANA, OVO, GoPay or QRIS reference can be retained to reconcile a cashier status or investigate a receipt question. Bank transfer and virtual account records may contain a reference number and timing, but we do not ask you to place full banking credentials in support messages.

Retention approach

We keep account and request records only for the period needed for service operation, security review, dispute handling or a legal requirement. When a record is no longer needed for those purposes, we assess it for deletion or removal of identifying details, subject to local rules.

Change requests

You can ask us to correct inaccurate profile details or explain how a particular record is used. Send the request through the listed support path with enough information to locate your account. We may verify ownership first and will state when a requested change depends on local law.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account questions you may have before using imb123 from Indonesia. They explain the practical path for data access, corrections, cookies, verification and payment references without turning the page into a general lobby description. If your question concerns a specific record, include the account step, date and device context so our support team can locate the relevant event. Eligibility and access remain where local law permits.

The imb123 Privacy Policy covers details collected during account creation, phone verification, login activity, support requests and payment-status checks. It explains why we use contact details, device signals, cookies and references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Use the support contact displayed in your account area and ask for a copy or explanation of the personal data connected to your profile. Include your account identifier and reachable contact detail. We may verify ownership before responding, and the result depends on local law.

Yes, you can ask us to correct inaccurate contact or profile details through the available support path. Tell us which field is wrong and provide the replacement clearly. We may request phone verification or another account check before changing information linked to your login.

Our Privacy Policy treats DANA and QRIS references as operational payment records used to match a cashier status, receipt or support case. We do not need your wallet PIN for that process. Send a reference number and date when asking us to trace a payment-related record.

A browser session cookie may keep an account step active on your phone, while other cookies can support page settings or security checks. You can manage cookies through browser controls. Clearing them may end the session and require phone verification or a fresh login.

We use account activity signals and phone verification to review unusual access, especially when a new device or browser appears. If your login is paused, contact support through the account route and describe what happened. Never include your password, wallet PIN or full bank details.

You may request deletion of eligible personal data through the listed support route. We first check the account and assess whether records must remain for security, dispute handling or legal reasons. We will explain any restriction and whether the outcome depends on local law.