Reference

erek erek 79 Privacy Policy Explained

Your account data at erek erek 79 is handled through a clear Privacy Policy covering registration, wallet records and account security.

Clear collection rulesWallet record contextAccount change requests
erek erek 79 erek erek 79 Privacy Policy Explained
CONTACT ROUTES

Where To Ask About Your Data

A direct account route gives you a practical way to ask about this Privacy Policy without posting personal details in a lobby message.

Account contact Open the support contact inside your account and describe the Privacy Policy request you…
Wallet record query For a DANA, OVO, GoPay or QRIS question, send the reference shown in your…
Login data request If a sign-in or phone verification record looks incorrect, tell us through the signed-in…
HANDLING DETAILS

How We Apply The Policy

We apply this Privacy Policy to the account journey rather than treating each screen as a separate record.

Account data

We collect details you provide during account creation and phone verification, along with records needed to keep the account usable. This may include contact details, sign-in events and messages you send through the account support route.

Cookies and devices

Cookies and device signals help keep a mobile browser session connected to the right account and help us detect unusual sign-in behaviour. You can manage browser cookie settings, although changing them may affect account access or saved preferences.

Wallet checks

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be retained to match account activity and resolve status questions. We do not need you to send a wallet password, card secret or one-time security code.

Account security

Phone verification and sign-in records help us identify account actions and investigate an unfamiliar session. Keep your phone access and account credentials private; our support route will not require you to publish them in a lobby or chat message.

Retention periods

We retain records only for the operational, dispute, security or legal purpose described by the applicable policy need. A deletion request may not remove every record immediately when a transaction or legal duty requires continued retention.

Policy changes

When this Privacy Policy changes, we place the revised wording on the policy page and identify the updated scope where appropriate. You can ask through your account contact path which section changed and how it affects your existing records.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the searches we hear before an account is opened or a data request is sent. They cover the account step, local wallet references, mobile access, cookies, retention and the route for correcting information. If your situation is not covered, use the account contact path and describe the specific record or action you want us to check.

It covers details connected with your account, including registration data, phone verification, sign-in events, device signals, support messages and payment references. It also explains how we use, protect, retain and change those records when you access the service where local law permits.

A DANA or QRIS reference lets us match a wallet event with the correct account and investigate a status question. The same approach can apply to OVO, GoPay, bank transfer or virtual account records. Send references only through the protected account contact route.

Yes, you can ask for an account data copy through the signed-in support contact shown in your account. Include enough detail for us to locate the record, such as the linked phone number or an account reference, but do not send passwords or security codes.

Use the account contact path and explain which phone verification detail appears wrong. We may ask for reasonable confirmation before making a change, because correcting the wrong account could expose personal data. Availability of a correction depends on local law and the record involved.

Yes. The Privacy Policy includes cookies and device signals used to maintain a mobile browser session, remember limited preferences and identify unusual sign-in behaviour. Your browser settings can restrict cookies, but that may interrupt account access or require you to verify the session again.

Retention depends on why a record is needed for account security, a status query, a dispute or a legal obligation. DANA, QRIS and bank transfer references may therefore remain after an account action ends. Ask through support for the applicable retention explanation for your record.

You can submit a deletion request through the account contact route. We will assess which details can be removed and explain any records that must remain for security, transaction handling or legal reasons. The result depends on local law and the specific account history involved.