Reference

Privacy Policy for ultraruby Accounts

ultraruby Privacy Policy explains how we collect, use and protect the account details needed for your Indonesia access.

Clear data purposesWallet record controlsPhone verification contextCookie choices
Browse Our Lobby Read FAQ
ultraruby Privacy Policy for ultraruby Accounts
HELP WITH REQUESTS

Get Privacy Policy Help From Your Account

A clear support path helps when a privacy request and an account issue arrive together. Start from the support route available after login and state whether you need a copy, correction, deletion…

Account request Use the signed-in support path to ask about your Privacy Policy rights, stored account details or a correction. We check the phone verification attached to your account before discussing personal records, so your request is connected to the right ultraruby profile.
Wallet record If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, mention the date, amount reference and wallet route shown in your account. We use those details to locate the matching record without asking you to reveal a wallet PIN or password.
Access concern When login activity or a device path looks unusual, contact support through the account route before changing payment details. We may ask for phone verification and recent account context, then record the request as part of our security handling.
DATA HANDLING

What We Keep And Why

We keep personal data only for defined account, security, payment-record and legal purposes described in this Privacy Policy.

Account details

We handle the details entered during account creation, including contact data and phone verification status. These records let us provide account access where local law permits and help us identify which profile should receive a privacy request or security response.

Payment references

Wallet and bank records are kept as references rather than wallet passwords. A DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI reference can help us check a receipt, identify a mismatch and answer a record request.

Cookies

Cookies can preserve a signed-in session, remember a device preference and show whether the Privacy Policy page works correctly. You can manage cookies through your browser settings, although switching them off may affect account access or saved preferences.

Device security

We may use device and login signals to detect unusual access, such as a new browser or repeated failed attempts. This helps us pause a sensitive account change and request phone verification before personal or wallet details are discussed.

Retention choices

We retain records for the period needed for the purpose described in this Privacy Policy, including account security, payment reconciliation and applicable legal duties. When a record no longer has a valid purpose, our handling follows the deletion or disposal process available to us.

Your request

You can ask for access, correction or a deletion assessment through the signed-in support path. Tell us which account detail or record you mean, and we may confirm your identity through the phone verification already linked to your profile.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the questions we expect before you open an account or connect a local wallet. They explain which details may be collected, how device activity and cookies fit into account security, and what route to use when you want to inspect or change a record. If your request concerns access in Medan, Semarang or another Indonesian location, eligibility still depends on local law.

The ultraruby Privacy Policy covers account details, phone verification, device and login signals, cookies, payment references and support requests. It explains why we use each category, how security checks work and which request path you can use to ask about access, correction or deletion.

We use your phone number to create and secure the account, send or confirm an account step and connect a privacy request to the correct profile. Phone verification may be required before we discuss personal records or change details, and access depends on local law.

Yes. The Privacy Policy covers references linked to DANA, OVO, GoPay and QRIS, including status or receipt details needed to match an account activity. We may also retain bank transfer or virtual account references, but we do not need your wallet PIN.

Device data helps us recognise unusual login behaviour and protect account changes. A new browser, repeated failed attempts or a different device path may lead to a phone verification step. We use these signals for security handling, not as a replacement for your account details.

You can request a correction through the signed-in support path. Identify the account field or payment reference that needs attention and provide the current detail. We may confirm your identity through the phone verification attached to the account before making a change.

You can ask us to assess deletion through the account support route. We review the request against account security, payment reconciliation and applicable legal duties. If a record must remain for a stated purpose, we explain that limitation and follow the retention period that applies.

Use the support path shown after you log in and describe the Privacy Policy issue clearly. Include your account phone number or a relevant DANA, OVO, GoPay, QRIS or bank reference, but never include a password, PIN or complete payment credentials.

Related Pages

ultraruby Indonesia Live Blackjack Salon Cashback Weekly Guide ultraruby Casino About Us