Reference

Privacy Policy for erek erek 4d

Your account details, wallet choices and device signals stay connected to clear access decisions.

Account clarityWallet data contextCookie choicesPhone verification
erek erek 4d Privacy Policy for erek erek 4d
CONTACT ROUTES

Get Privacy Help From Your Account

A clear contact route helps you ask what data we hold or report a mistaken account detail.

Account request Use the support path inside your account to ask for a copy, correction or explanation of personal data. Include your linked phone number so we can match the request to the right profile before discussing account records.
Wallet reference For a privacy question involving DANA, OVO, GoPay or QRIS, share the transaction reference visible in your account receipt. We can check the record while keeping your wallet PIN, password and authentication code out of the conversation.
Access concern If an unfamiliar device or sign-in appears, tell us through the account support route and change your password from the security area. We may ask for phone verification before changing access details linked to your profile.
DATA PRACTICES

What We Do With Your Account Data

We keep this policy practical by linking each data use to an account action you recognise. Phone verification supports account recovery, device details help us investigate sign-in problems, and payment references help…

Collection

We may receive your phone number, account details, sign-in records, device information and payment references when you open an account or use its account areas. We collect only what helps deliver access, verify activity, answer requests or meet a valid legal need.

Phone checks

Phone verification confirms that an account access request is connected to the number you provided. If you ask us to change that number, we may request another account check so a stranger cannot redirect recovery details.

Cookie choices

Cookies can keep your session available and help us see whether a policy page loads correctly on your device. Your browser settings can remove or restrict cookies, although changing them may affect sign-in continuity.

Account security

We use sign-in records, device signals and verification steps to investigate unusual access. We do not ask you to disclose a password, wallet PIN or one-time code when you report a security concern through support.

Retention

We retain account and transaction records for as long as needed for the stated service purpose, security checks, dispute handling or an applicable legal requirement. When a record is no longer needed, our process removes or de-identifies it where appropriate.

Change requests

You can ask us to correct inaccurate personal details, explain how a record is used or provide an applicable copy through account support. We may verify your identity first, then respond according to the request and local legal requirements.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account actions you are most likely to take before opening an account or while checking a wallet record. We explain the practical route for access, correction, cookies, phone verification and deletion requests. If your question concerns eligibility or a regional restriction, access depends on local law, and the account support path can clarify which rule applies.

It covers account details, phone verification, sign-in and device records, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains security, retention and how to request a change.

We use the phone number to create and protect your account, complete a phone verification step and help confirm recovery or access changes. If the number is inaccurate, contact support through your account so we can verify the request before editing it.

Yes. The Privacy Policy covers payment references and wallet status connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use those references to match an account transaction, not to request your wallet PIN.

Sign in where possible and use the account support path. State whether you want a data copy, a correction or an explanation of use, then provide the phone number linked to your profile. We may verify identity before handling the request.

Cookies may keep a session active and help us check whether pages load properly on your device. You can restrict or remove them through your browser settings. If sign-in continuity changes afterward, review the browser setting before contacting account support.

We keep records for the operational purpose described in the Privacy Policy, including security checks, transaction questions, dispute handling or a legal requirement. When the purpose ends, our process removes or de-identifies the record where appropriate.

Use the account support route as soon as you notice it, change your password from the security area and complete any requested phone verification. Do not send a password, wallet PIN or one-time code in a support message.