Reference

Open the rezeki hub Privacy Policy

rezeki hub Privacy Policy explains how we handle your account details, wallet references and device access while you browse Live Roulette Prestige or Live Dealer Highlights.

Account dataWallet referencesCookie choicesAccess requests
rezeki hub Open the rezeki hub Privacy Policy
CONTACT PATHS

Open a privacy request through support

A clear contact route helps you ask what data we hold or report a concern about account access. Send your request through the support route linked beside account assistance, using the email address connected to your account where possible. We may ask for an account step or verification detail before discussing private records. That check protects you when a request involves wallet references, device activity or a change to your registered contact details.

Team online

Data access request

Ask us to confirm whether we hold account records connected with your email or phone details. Include the account contact you used so we can locate the correct record without exposing it to another person.

Correction request

If your name, phone detail or account record needs correction, tell our support team which field is wrong and what should replace it. We may verify the account before making a change to protect its ownership.

Privacy concern

Report an unexpected message, unfamiliar device session or concern about a DANA, OVO, GoPay or QRIS reference through the same support path. Keep payment receipts private and never send a wallet PIN.

DATA PRACTICES

Explore the privacy steps behind your account

Privacy is managed through practical account controls rather than broad promises. We separate account details from payment references where our records allow, limit access to staff who need it for support or…

Account collection

When you create an account, we collect the details needed to identify the account and contact you. A clear phone verification step can be required before account access, helping us connect requests with the correct account holder.

Wallet references

A deposit record may contain a method label such as DANA, OVO, GoPay, QRIS, virtual account or bank transfer. We use transaction references for account support and status checks, not to ask for your wallet password or PIN.

Device signals

Browser type, operating system, language and sign-in timing can be recorded when you use a phone or desktop. These signals help us investigate an unfamiliar session and are considered alongside your account details during support checks.

Cookies

Cookies may keep a session active, remember selected settings or help us understand which privacy page version was shown. You can clear or restrict cookies in your browser, although some account steps may then need to be repeated.

Retention decisions

We retain records only while they support account administration, security review, dispute handling or a legal requirement. When a deletion request is accepted, some limited records may remain where keeping them is required for one of those purposes.

Policy changes

If our collection or use of personal data changes, we revise this Privacy Policy and show the new version through the privacy link. Check the page before an account step if you want to see the current wording.

Browse answers about Privacy Policy

These Privacy Policy answers address the searches we hear most often before account creation or a support request. We explain the practical route for access, correction, cookie control and account protection without asking you to share sensitive wallet credentials. If your situation is not covered, use the support path and include only the account details needed to locate your record.

It covers account details, phone verification records, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, virtual account or bank transfer activity. It also explains retention, correction, deletion requests and how we protect account access.

Yes. Send a data access request through our support route and use the email or phone detail connected to your account. We may ask for an account verification step before releasing records, so another person cannot obtain your private account or wallet references.

Tell support which account field is inaccurate and provide the replacement detail through the privacy contact route. We check ownership before changing phone, email or verification records. This process applies whether you access the account from a mobile browser or desktop device.

Yes. The policy covers transaction references showing a DANA, OVO, GoPay or QRIS method, as well as virtual account and bank transfer references. We do not ask for wallet PINs or passwords. Receipts should be shared only through the designated support path.

Cookies can preserve a session, remember a setting and support page operation. You can remove or restrict them through your browser controls. If cookies are blocked, you may need to repeat login or phone verification steps when returning to the account.

Retention depends on the purpose of the record, including account support, security checks, dispute handling and legal requirements. When those purposes no longer apply, we assess removal. Some limited records may remain after a request where keeping them is required by law.

You can submit a deletion request through support with the contact detail linked to your account. We review the request against account, security and legal obligations. Access to the account may depend on local law, and we explain any records that cannot be removed.