Reference

ina138 Privacy Policy For Your Account

The ina138 Privacy Policy shows how we handle your account details while you move from phone verification to Live Casino, erek4 or local wallet access.

Clear data choicesPhone verificationIndonesia account access
ina138 ina138 Privacy Policy For Your Account
HELP WITH DATA REQUESTS

Get Privacy Policy Help Near Login

A clear contact path matters when your Privacy Policy question concerns a locked sign-in, an unfamiliar device record or a wallet reference. Start from account help and describe the request in plain English, including the email or phone detail attached to your account. We use that account step to locate the right record without asking you to send a wallet password. If you are in Makassar, the same digital support route applies where local law permits.

Team online

Account data request

Ask us to explain, correct or remove a detail connected with your ina138 account. Include the account contact used at registration so we can verify the request before discussing personal data.

Wallet reference check

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the transaction reference through account help. We compare the cashier record with your account activity and reply with the next privacy step.

Sign-in device concern

Tell us when a new phone or browser appears in your account history. We can review the access record, help secure the sign-in and explain which device data the Privacy Policy covers.

DATA HANDLING DETAILS

What Privacy Controls You Can Use

Privacy Policy choices are easier to use when each control has a clear purpose. We keep account access tied to the details you provide, separate payment references from wallet credentials, and use…

Account details

We handle the contact and verification details you provide during account creation so we can identify your account, support sign-in and connect your requests to the correct record. Please keep those details current.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be used to match a cashier event with your account. We do not ask for your wallet password as part of that check.

Cookies and sessions

Cookies may remember a sign-in session, device preference or page setting. You can manage browser cookie controls, but limiting them may require you to repeat an account step when returning to the lobby.

Account security

Phone verification helps connect account access to the contact detail you submitted. If a sign-in comes from an unfamiliar device, we may use device and connection signals to review the event and protect the account.

Retention approach

We retain account, request and transaction references only as needed for the stated account, security and service purposes, or for a period required where local law permits. Ask support to explain the record involved.

Change requests

To request access, correction, deletion or clarification, use account help and identify the contact detail on your account. We may ask for a verification step before changing or disclosing personal data.

Answers About ina138 Privacy Policy

These Privacy Policy answers focus on the searches we hear before an account is opened. You can use them to understand account records, local wallet references, cookies, device checks and contact steps without sending sensitive wallet credentials. Where a request affects access or eligibility, the outcome depends on local law.

The ina138 Privacy Policy covers account details, phone verification, device and connection signals, cookies, support requests and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It explains why we use each category and how to ask about your record.

We collect the details you submit during account creation and phone verification, along with technical records needed for sign-in continuity and security. We may record device or connection events when you access the account, but the Privacy Policy does not require your wallet password.

The Privacy Policy allows us to use payment references from DANA, OVO, GoPay and QRIS to match a cashier event with the correct account and resolve a status question. These references help with reconciliation; they are not a request for your wallet password or private wallet login.

Yes. Use the account help path and state whether you want access, correction, deletion or clarification. Include the contact detail used for registration, then complete any verification step we request. We handle the request under the Privacy Policy and where local law permits.

Cookies can keep a session active and remember a page setting, while device and connection details can help identify unusual sign-ins. The Privacy Policy describes these uses. If you restrict cookies in your browser, you may need to repeat login or verification steps.

We keep account, support and payment-reference records for the account, security and service purposes described in the Privacy Policy, or for a period required where local law permits. Ask account help about a particular record, and we can explain the relevant retention reason.

Contact our support desk through account help and mention the record type, such as a new device event or an unexpected QRIS reference. Do not send a wallet password. We first verify your account contact, then explain the Privacy Policy step that applies.