Reference

imba slot login Privacy Policy

The imba slot login Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and contact our support path.

Clear data purposesWallet record contextAccount contact pathCookie choices

Explore Our Lobby Read FAQ

What Our Privacy Policy Covers

imba slot login Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers the details you provide during account creation, such as your contact information and verification response, together with technical signals from the phone or browser used to sign in. It also explains how we match payment references from DANA, OVO, GoPay, QRIS, bank

1
transfer or virtual account activity to the correct account record. We use these details to keep account access orderly, check a payment status and respond to a privacy request. We do not describe access as available everywhere: it depends on local law or is offered where
2
local law permits. Please read this notice before opening an account, and contact us through the account contact path if a section is unclear.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Privacy Help Beside Your Account

A clear contact path helps when you want to ask about personal data, a cookie setting or an account record linked to a wallet reference. We direct privacy questions through the contact entry shown after login and alongside the cashier path, so you do not need to explain your account from the beginning. Include the account identifier, the relevant date and the type of request. We use those details to locate the correct record while keeping the request focused.

Team online

Account contact entry

Open the contact entry after signing in and identify your request as a Privacy Policy question. Add the account identifier and the email or phone detail connected with your account so we can route the request to the relevant record.

Payment record question

If your request concerns DANA, OVO, GoPay or QRIS, include the payment reference and date rather than sending a full wallet screenshot. This helps us check the stored transaction reference while reducing unnecessary personal details in your message.

Correction request

For a change to your account details, tell us which field is inaccurate and confirm the account step you completed before sign-in. We may ask for an account check so a correction is applied to the right profile.

DATA PRACTICES

How We Handle Your Account Data

We handle account data around identifiable actions: creating a profile, confirming a phone detail, signing in from a device and matching a payment reference.

Account details

We may hold the contact details you submit during account creation and the phone verification result used before account access. These records help connect your sign-in request with the correct profile and help us respond to a data question.

Device signals

A phone or desktop browser can send technical details such as device type, browser version, session time and security events. We use these signals to recognise an active sign-in path and investigate unusual account access.

Cookie controls

Cookies can keep a session active and remember selected settings. Our Privacy Policy explains their purpose, and you can adjust browser cookie controls. Removing them may require you to repeat the login step when returning to the account.

Wallet references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may retain a reference, amount status and timestamp needed to connect the payment event with your account record. We do not need a full wallet password for that matching step.

Account security

Phone verification before account access is one part of our account security process. We may also record sign-in events and session changes so we can review a disputed login and help you regain control through the account contact path.

Storage and changes

We keep records only for the period needed for the stated account, payment or support purpose, subject to applicable requirements. You can ask what we hold, request a correction or ask how a record is being used through the contact entry.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account steps you are most likely to check before opening an account from Indonesia. We cover sign-in records, local wallet references, cookies, device signals and contact requests in plain language. If your question is not listed, use the account contact entry and include only the details needed to identify your request.

The Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, payment references and support requests. It explains why we handle each category and how you can ask about access, correction or use of a record connected with your account.

Yes. The Privacy Policy includes references connected with DANA and QRIS, along with OVO, GoPay, bank transfer and virtual account activity. We may use a reference, status and timestamp to match a payment event with your account without requesting a wallet password.

We collect limited device and browser signals to support the sign-in session, identify unusual access and investigate an account question. Examples include device type, browser version, session time and security events. The Privacy Policy explains how these signals fit the account process.

Use the contact entry shown after login and state which account field is inaccurate. Include the account identifier and explain the requested correction. We may ask you to complete an account check before changing the record, so the update reaches the correct profile.

You can ask what account, device, cookie, payment-reference or support data is connected with your profile. Send the request through the account contact path with the relevant date or reference. We will use the details supplied to locate the appropriate record.

Cookies can retain a session state and selected settings in your browser. If you remove or block them, you may need to repeat phone verification or sign in again. The Privacy Policy describes cookie purposes, while your browser provides the setting used to change them.

No statement on this page changes local eligibility. Account access depends on local law and is available where local law permits. If you are unsure about your location or account position, check the applicable local requirements and contact us through the account path.

imba slot login Privacy Policy

Privacy Help Beside Your Account

Account contact entry

Payment record question

Correction request

How We Handle Your Account Data

Account details

Device signals

Cookie controls

Wallet references

Account security

Storage and changes

Privacy Policy Questions From Indonesia

01 What does the imba slot login Privacy Policy cover?

02 Does the Privacy Policy include DANA and QRIS data?

03 Why does imba slot login collect device information?

04 How can I request a correction to my account data?

05 Can I ask what data the Privacy Policy says you retain?

06 How do cookies affect my imba slot login session?

07 Is access covered by the Privacy Policy available everywhere?

Related Pages