Reference

Privacy Policy for erek erek 19

erek erek 19 Privacy Policy explains what we collect when you open an account, sign in from a phone, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice securityData requests
erek erek 19 Privacy Policy for erek erek 19
CONTACT PATHS

Get privacy help beside your account

Privacy questions should be easy to route, especially when a wallet reference or phone check is involved.

Account support Use the support route inside your account for a Privacy Policy request. Tell us whether you need access, correction or deletion, and include the phone number linked to your erek erek 19 account so we can match the request safely.
Wallet record help If your request concerns DANA, OVO, GoPay or QRIS, share the transaction reference shown in your account rather than a wallet password or PIN. We use the reference to locate the status record without asking for private wallet credentials.
Login and device query A sign-in concern can be raised through the same account support path. Describe the phone or browser involved and the time of the event; we can then check session signals while keeping your account details away from an unverified contact.
HANDLING DETAILS

What our Privacy Policy covers

We keep this policy practical by connecting each data use to a clear account action. A phone check supports access control, device signals help us spot an unfamiliar session, and payment references…

Account records

When you open an account, we store the details needed to identify your profile and complete phone verification. We use that record for sign-in assistance and account security, not as a reason to request unrelated personal details.

Cookie choices

Cookies or similar browser storage can keep a session active and remember a practical setting. You can clear them through your browser controls, although doing so may sign you out and require the account step again.

Device signals

A phone or browser can provide session signals such as device type, browser details and access time. We use these clues to compare a familiar sign-in with an unusual one and to help investigate an account access question.

Payment references

DANA, OVO, GoPay and QRIS may provide a reference or status connected with your account action. We use that reference to trace the record; we do not need your wallet PIN, password or private wallet login.

Retention approach

We keep account, security and transaction references for the period needed to protect access, resolve a dispute or meet a legal requirement. When a record is no longer needed for those purposes, our handling process can remove it.

Change requests

To request a copy, correction or removal, contact us through the signed-in support path and describe the exact data involved. We may verify your phone or account details before acting, which protects your profile from an unauthorised request.

Privacy Policy answers for your account

These Privacy Policy answers focus on the questions that arise before and after an account is opened. They explain account access, wallet references, cookies, device signals and requests for data changes in plain language. If your situation is not covered, use the support path connected to your signed-in account and describe the record or action you want us to check.

It covers data connected with your account, phone verification, sign-in sessions, browser storage, device signals, selected pages and payment references. We use those details for access security, payment-status matching, support replies and legal duties, with access depending on local law.

Phone verification helps connect an account request to the person seeking access and helps us respond safely to account changes. If you ask about stored data or a wallet record, we may repeat an account check before disclosing details.

Yes. The Privacy Policy covers payment references and status details linked to your account action through DANA, OVO, GoPay or QRIS. We use those references to trace a record, while your wallet PIN and wallet password remain outside our support request.

Sign in and use the account support path, then request access to your personal data in clear terms. Include the phone or email linked to your profile. We may verify those details before responding so another person cannot obtain your account record.

You can ask us to correct inaccurate account details or remove data that no longer needs to be held, where local law permits. Send the request through signed-in support and identify the record. Some security or transaction records may need to remain.

Cookies and browser storage can keep a session active and remember selected settings. You can clear them in your phone or desktop browser, but that may sign you out. After clearing them, use your usual account step to access the lobby again.

Use the signed-in support path and describe the device type, browser and approximate access time. We can check the session signals and help protect the account. Do not send a wallet PIN, password or full private payment credentials in your message.