Reference

Open the Privacy Policy for erek erek 14

erek erek 14 Privacy Policy sets out what we collect when you create an account, verify your phone, enter the lobby and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesSecurity requests
erek erek 14 Open the Privacy Policy for erek erek 14
CONTACT PATHS

Browse Privacy Help From Your Account

A clear contact path helps when you want to ask about the Privacy Policy, check a stored account detail or question a wallet record. We route privacy requests through the same account support area used for login and cashier status questions, so you can include the relevant phone number, transaction reference or device detail without sending a wallet password. If you are in Bandung, the same online route applies; access depends on local law.

Team online

Account support

Use the support path inside your account when you need to ask what data is linked to your phone verification, request a correction or clarify why a login record appears. Include your account phone number and we can match the request without asking for your wallet PIN.

Wallet records

For a DANA, OVO, GoPay or QRIS query, send the payment reference and visible status from your account cashier path. We use those details to locate the relevant record, explain its purpose and avoid requesting full wallet credentials or a wallet password.

Policy questions

When your question concerns this Privacy Policy itself, contact our support desk through the account contact route and state whether you seek access, correction, deletion or a retention explanation. We will identify the request before discussing account-linked data with you.

DATA PRACTICES

Switch Through Our Privacy Safeguards

Our privacy process follows the account actions you take, rather than collecting unrelated details.

Phone verification

Before account access is completed, we use the phone verification result to connect the correct account holder with the login…

Device signals

A browser or mobile session may create technical records such as device type, operating system, browser version and login time.

Cookie controls

Essential cookies can keep your session and policy choices working, while limited measurement cookies may show which page sections are…

Wallet references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain the payment rail, reference and status needed…

Account security

We use phone verification, session checks and account details to reduce the chance of another person entering your account.

Requests and retention

You can ask for access, correction, deletion or an explanation of retention through our support path.

Get Answers About Privacy Policy

These Privacy Policy answers focus on the account and wallet questions you are most likely to raise before opening access. We keep the route practical: identify your account, describe the request and use the support path connected to your login. Where access or eligibility is discussed, it depends on local law.

It covers account details, phone verification, device and session records, cookies, payment references and support requests connected with your access. It also explains retention, security checks and how to ask for access, correction or deletion where local law permits.

We may collect the details you enter, your phone verification result, account settings, login events and technical device data. If you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may store the related reference and payment status.

Device type, browser details and session timing help us identify unusual access and protect the account path. We do not need to read private files on your phone. You can contact support if a device or login record looks unfamiliar.

Use the account support route and state that your request concerns the Privacy Policy. Include your account phone number, the record you want checked and the correction needed. We may verify account ownership before discussing or changing account-linked data.

You can send a deletion request through the support path connected with your account. Some records may need to remain for security, payment reconciliation or dispute handling. We will explain the reason for any retained record and apply the request where local law permits.

We use the payment rail, reference, amount and status to match a cashier event with your account. The record helps us answer a receipt or status question, but we do not require your DANA or QRIS password or private wallet credentials.

Contact our support desk through the account contact route and label the message as a Privacy Policy request. Tell us whether you need access, correction, deletion or a retention explanation, then include your account phone number without sharing a password or one-time code.