Reference

kaya raya slot Privacy Policy for Your Account

kaya raya slot Privacy Policy explains how we collect, use and protect the details connected to your account, from phone verification to DANA or QRIS status.

Clear data purposesWallet records explainedCookie choicesAccount access requests
kaya raya slot kaya raya slot Privacy Policy for Your Account
CONTACT ROUTES

Get Privacy Help Near Your Account

A clear contact path helps you ask about personal data without repeating your account story. Use the support route available from your account area and include the email or phone detail linked to your profile, not a wallet PIN. Our team can trace a QRIS receipt reference, explain an OVO status record, or route a privacy request for a second check. If you are in Surabaya, the same account-based path applies on mobile and desktop.

Team online

Account privacy request

Ask us to find, correct or remove personal details linked to your account. We first compare your request with the verified phone or email on file, then explain what can be changed and any legal reason a record must remain.

Wallet record question

If a DANA, GoPay or QRIS reference appears unfamiliar, send the receipt number through the account help route. We use that reference to locate the related record without asking for your wallet password, PIN or one-time security code.

Sign-in privacy support

A sign-in issue can be handled without exposing your full account history. Tell us the device type, approximate time and account contact detail; we may ask for phone verification before discussing access or changing security details.

DATA CONTROLS

Six Privacy Controls We Apply

Privacy is handled through account steps rather than broad promises. We separate identity checks from wallet references, limit internal access to records needed for support or security, and…

Account data

We use your submitted contact details to create the account, send account notices and complete phone verification.

Payment references

We retain the reference needed to match a DANA, QRIS, bank transfer or virtual account event with your account.

Cookies

Cookies can remember a sign-in step, preserve language or region settings and help us see whether a page loads correctly.

Security checks

We may compare a new sign-in with account signals such as device type, session timing and phone verification status.

Retention

We keep records for as long as needed for account operation, support tracing, security checks or applicable legal duties.

Policy changes

If we change how personal data is handled, we place the revised Privacy Policy in the policy area and show…

Privacy Policy Questions Before Account Access

These Privacy Policy answers focus on the questions you may have before opening an account with kaya raya slot. We cover the records connected to mobile browsing, wallet references, cookies, phone verification and requests for access or correction. If your situation is not covered, use the account help route and send only the details needed to identify your request.

We may collect account contact details, phone verification results, sign-in and device signals, cookie activity, support messages and payment references. A DANA or QRIS reference helps us trace status, while your wallet PIN, bank password and one-time security code should never be sent to support.

Phone verification helps us confirm that an account request comes from the person connected with the account. We may use it before discussing sensitive access, correcting contact details or changing security settings, including when you move from a mobile browser to desktop.

We use the payment reference and status needed to match an account event, answer a receipt question and investigate a delayed wallet update. We do not need your wallet password or PIN. Bank transfer and virtual account references can be handled through the same account support path.

Yes. Send an access or correction request through the account help route using the verified phone or email on your profile. We may ask for an additional identity check, then tell you which records can be supplied or amended and why.

Cookies can keep a sign-in step active, remember language or region settings and help us diagnose page loading. You can adjust browser controls, but blocking necessary cookies may make you sign in again or repeat phone verification on a later visit.

Retention depends on the reason for holding a record, such as account operation, security, payment tracing, support or legal duties. We remove or separate records when they are no longer needed for those purposes, subject to applicable requirements and local law.

Use the support route inside your account and state whether you need access, correction, deletion or an explanation of a wallet reference. Include your account contact detail and receipt number when relevant, but never include a PIN, password or one-time code.