Reference

karim123 Privacy Policy For Your Account

The karim123 Privacy Policy explains what we collect when you open an account, use the mobile lobby, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesSecurity requests
karim123 karim123 Privacy Policy For Your Account
HELP WITH PRIVACY

Get Clear Answers About Your Records

A direct support route helps you understand the Privacy Policy without guessing which account step applies.

Account support path Use the support option inside your account for Privacy Policy questions.
Wallet record help If your question concerns DANA, OVO, GoPay or QRIS, add the payment reference and…
Privacy request route For a copy, correction or deletion request, state the action clearly and use the…
DATA CARE DETAILS

What The Privacy Policy Covers

The Privacy Policy gives you a practical view of the information used around your account rather than a broad description of the lobby.

Account collection

When you open an account, we may collect your contact details, phone verification result and sign-in history. These records help us connect your requests to the correct profile and investigate an access question without relying on a display name alone.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account request can create a reference, amount status and time record. We use this information to reconcile the account action, while wallet credentials remain outside the support request.

Cookie controls

Cookies and similar device storage can remember a session choice or help us understand whether a page loads correctly. Your browser settings provide a way to restrict them, although some account functions may then need another sign-in.

Security signals

We may examine device type, browser details, login time and failed access attempts when protecting an account. These signals can prompt phone verification or a support check; they are used to assess account activity, not to request your wallet PIN.

Retention choices

We keep records only for the period needed for the stated account, payment, security or support purpose, subject to legal requirements. A retention question can be sent through the privacy route, and we will explain what can be changed or removed.

Change requests

You can ask us to correct inaccurate contact details or clarify how a record is used. We may verify the phone connected to your account before making a change, and requests involving access depend on local law.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the account and wallet questions we expect you to ask before using karim123. They cover what we collect, why payment references appear, how cookies work, how to request a copy or correction, and what happens when access depends on local law. For a case-specific answer, use the support path connected to your account.

The Privacy Policy covers account details, phone verification, login events, device signals, cookie use, support messages and payment references. It explains why we use each category, how long records may remain, how security checks work and how you can request access, correction or another policy-related action.

Phone verification helps us connect an account request to the right person and respond safely to account questions. It can also support an access check after unusual login activity. We do not ask you to place a wallet PIN or password in a Privacy Policy support message.

Yes. The Privacy Policy explains that DANA, OVO, GoPay and QRIS activity may create payment references, status details and timestamps connected with your account request. These records help reconciliation and support, while your private wallet credential is not needed for our account support path.

Use the privacy contact path shown after account access and state that you want a copy of your personal data. Add your verified phone number and the records you mean, such as login or payment references. We may verify ownership before responding, and timing depends on local law.

You can request a correction when contact or account details are inaccurate. Tell us which field is wrong and what it should say through the account support path. We may ask for phone verification, and some changes can require an account check before they are applied.

On a mobile browser, cookies or device storage may keep a session choice or help diagnose a page issue. You can restrict them through browser controls. If you clear or block them, the lobby may ask for another sign-in, while account records remain governed by the Privacy Policy.

Yes. Send a retention or deletion question through the privacy route and identify the relevant account record without sharing your password. We assess the request against account, payment, security and legal needs. Whether a record can be removed depends on local law and its stated purpose.