Reference

Privacy Policy for erek erek 91

erek erek 91 Privacy Policy sets out what we collect when you open an account, verify your phone, use DANA or QRIS, and move through the casino or…

Clear collection rulesWallet record contextAccount request path
Explore Our Lobby Read FAQ
erek erek 91 Privacy Policy for erek erek 91
REQUEST HELP

Privacy Requests Near Your Account

A clear support route helps when your Privacy Policy request concerns a phone number, wallet reference or sign-in record. Start from the support path linked to your account and tell us which record you want checked, corrected or removed. Include the email or phone detail attached to your account, but never send a password or full wallet PIN. If you are in Bandung or elsewhere in Indonesia, the same request path applies; we may ask for an account check before discussing personal data.

Team online

Account data request

Use our account support path to ask what personal details are connected with your profile. We may confirm your phone verification first, then explain the available copy, correction or deletion step under the Privacy Policy and applicable local rules.

Wallet record check

For DANA, OVO, GoPay or QRIS records, identify the date, amount reference and wallet rail without sending secret credentials. We compare the request with our transaction record so the response concerns your account rather than another customer’s activity.

Policy contact route

Questions about cookies, retention or device signals can be sent through the same support area. Write Privacy Policy in your message subject and describe the exact change you want us to assess, so our team can route it correctly.

DATA PRACTICES

How We Handle Your Privacy

We keep the Privacy Policy practical by linking each data use to an account action. Phone verification helps us recognise the account owner; device signals help us spot unusual sign-in behaviour; wallet…

Account details

We use the name, phone number, email address and verification responses you provide to create and protect your account. If a detail changes, contact us through the account support path and we can explain the correction step available under this Privacy Policy.

Device signals

Your mobile or desktop browser may send device, session and network signals when you sign in. We use them to detect unusual access and protect the account, including when you switch from a mobile lobby path to a desktop browser.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference numbers, status entries and timestamps. We use those records to match your account request, while avoiding collection of wallet passwords or PINs.

Cookies and sessions

Cookies can remember a sign-in session, language choice and security state on your browser. You can clear them through browser settings, although removing session cookies may require you to complete phone verification again before account access.

Retention timing

We retain account, security and payment records only while they support account operation, dispute checks, security review or a legal requirement. When a valid reason ends, we assess deletion or de-identification rather than keeping the record without purpose.

Your requests

You can ask for access, correction, deletion or a use restriction where local law permits. Send the request through support with enough account detail for verification; we may keep a request record so we can show how it was handled.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions we hear most often from Indonesian customers. They cover what we collect, why a phone check may appear, how cookies work on mobile, and which route to use when you want a change. If your request involves access or eligibility, the outcome depends on local law.

It covers account details, phone verification, device and session signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security handling and the requests you can make where local law permits.

Phone verification helps us check that the person requesting account access or personal-data changes is connected with the account. It can also help us respond to a correction or deletion request without exposing account details to someone else.

We use payment references, status entries and timestamps to match account activity, but you should not send a wallet password, PIN or secret code to us. DANA and QRIS requests are handled through the relevant payment flow and your account support path.

Cookies can keep a session active, remember a language choice and support security checks while you move from login to the lobby. You can clear them in your browser settings, but doing so may end the session and prompt another phone verification.

Yes, you can ask what account details and related records we hold through the support path linked to your account. We may verify your phone or another account detail first, then explain the available response and any lawful limits.

Send support a clear request naming the detail that needs correction, such as a phone number or email address. Include the account identifier requested by our team, but not your password or wallet PIN. We will check ownership before changing the record.

You may request deletion through the account support route where local law permits. Some security, dispute or payment records may need to remain for a valid period, and we will explain that reason rather than removing records needed for those checks.

Related Pages

erek erek 91 Indonesia Access guide Dragon Tiger Live erek erek 91 Casino About Us