Reference

Open ultraruby Privacy Policy Clearly

ultraruby Privacy Policy shows how we handle your account details, phone verification and wallet records when you open access to Live Blackjack Elite or Cendrawasih Wild Slots.

Account dataWallet recordsCookie choicesPhone checks
ultraruby Open ultraruby Privacy Policy Clearly
PRIVACY SUPPORT

Check Privacy Help Before Contacting Us

A privacy question should have a direct route, so we connect account help with the support path shown after sign-in.

Account help form Open the support form from your signed-in account when your request concerns stored profile…
Wallet record query If a DANA, OVO, GoPay or QRIS reference appears incorrectly, describe the date, method…
Cookie request For cookie questions, tell us which device and browser you used, such as a…
DATA CONTROL

Switch Privacy Settings With Account Care

Privacy depends on practical handling, not a vague promise. We separate account details from payment references where our records allow, limit internal access to operational needs and use security events to investigate…

Account data handling

We use details such as your contact information, phone verification result and sign-in history to operate account access and respond to privacy requests. A request can be checked against the account record before we change or disclose anything connected with your profile.

Cookie choices

Cookies can remember a session and help us understand browser activity connected with account access. Our Privacy Policy explains their purpose and your choices; clearing them may sign you out or require another phone verification step on that device.

Wallet references

DANA, OVO, GoPay and QRIS may generate transaction references that we retain to match account activity with a payment request. These references are not a substitute for your wallet password, which we do not need for a privacy enquiry.

Device security

We may record browser, device and sign-in signals when you use a phone or desktop. These signals help us identify unusual access around account changes, while your payment PIN and one-time code should remain private and outside every support message.

Retention timing

The policy explains why certain account, payment and security records remain available after an action and when they can be removed. Retention can differ by record type, so your request should name the data category you want us to assess.

Change requests

You can ask us to correct inaccurate profile data, explain a stored record or assess deletion through the support form. We may request account verification first, then respond using the contact detail already attached to your ultraruby account.

Ask About Privacy Policy And Access

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They cover the data connected with login, phone checks, mobile browsing and local payment references, while keeping the route back to account support clear. If your situation is unusual, send the details through the support form rather than sharing sensitive wallet credentials.

It covers account details, phone verification, browser and device signals, cookies, payment references and security records connected with your access. It also explains purposes, retention, correction and deletion requests, including records created when you use DANA, OVO, GoPay or QRIS.

We use the result to confirm an account access step and help protect changes to your profile. The Privacy Policy explains how that record is handled; if the phone number is wrong, contact account help after signing in and request a correction.

Yes. The Privacy Policy covers the transaction references needed to match DANA, QRIS, OVO, GoPay, bank transfer or virtual account activity with your account. It does not ask you to share a wallet PIN or one-time code with support.

You can use the signed-in support form to request access to, or correction of, account data. State the record you mean, such as a phone detail or wallet reference. We may verify account control before releasing or changing personal data.

Cookies can maintain a browser session and support account access on a phone. The Privacy Policy describes their purpose and your available choices. Clearing browser data may end the session, so you may need to sign in and complete phone verification again.

Retention depends on the type of record and the reason it was created, including account, payment matching and security records. The Privacy Policy explains these purposes. You can ask support to assess a specific category instead of making a general request.

Start with the support form linked from your signed-in account help area. Describe whether you need access, correction, deletion or an explanation, and include only the account detail needed to locate you. Access depends on local law and where local law permits.