Reference

indra303 Privacy Policy For Your Account

indra303 Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account recordsWallet detailsCookie choicesAccess requests
indra303 indra303 Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Help Through Your Account

A privacy question should reach the same account context as the record involved. We ask you to use the support route shown inside your account and include the sign-in email or phone…

Account request Use the support route available after sign-in to ask for access, correction or deletion of personal data. Include your account identifier, but never send your password, one-time code or complete wallet credentials in a privacy request.
Wallet record For DANA, OVO, GoPay or QRIS references, tell us the date, amount reference and account identifier shown in your receipt. We use those details to locate the relevant record while limiting the information shared in your message.
Security concern If you notice an unfamiliar sign-in or device session, mention the time and device path used, such as mobile browser or desktop browser. We can direct the account-security check without requiring your wallet PIN or sign-in password.
HANDLING DETAILS

How indra303 Manages Privacy Requests

Privacy work is tied to practical account events rather than broad collection. We separate identity details from payment references where our systems allow, restrict account records by access role and review unusual…

Data collection

We collect details you enter during account opening and phone verification, plus device and session signals created during sign-in. If you open Rice Terrace Reels or Lightning Roulette Room, related activity may be linked to your account record for security and account history.

Cookie controls

Cookies can keep your session and selected settings working between pages. On a mobile browser, you can clear site data through the browser privacy controls; blocking essential cookies may require you to sign in again before reaching account areas.

Account security

Phone verification helps connect account access to the contact detail you supplied. We do not ask for your password or one-time code in a support message, and unfamiliar device activity can be raised through the account security route.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can help us match a wallet status or receipt question. We use the reference for reconciliation and support, not as a request for your wallet PIN.

Retention period

We retain account, security and transaction-linked records for as long as needed for the purpose described here, account protection or legal duties. When retention is no longer needed, records are removed, aggregated or otherwise restricted where practical.

Change requests

Ask us to correct outdated contact details, explain a data use or request deletion where applicable through the signed-in support route. We may need to verify account control before changing information connected with phone verification or wallet records.

Privacy Policy Questions About indra303

These Privacy Policy answers address the account questions we expect before you open an account or send a data request. We keep the route practical: identify the account, describe the record and use the support path shown after sign-in. Eligibility and access remain subject to local law, including for Indonesian account holders.

The indra303 Privacy Policy covers contact details, phone verification records, account identifiers, device signals, session activity and support messages. It also explains why payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account may be retained for matching and security.

Use the support route shown after you sign in and ask for an account-data copy. Include the account email or phone number and describe the records you need. We may verify account control first, especially when the request concerns phone verification or wallet references.

Yes, you can request a correction through the account support route. State which detail is outdated and provide the updated value without sending a password or wallet PIN. We may check account control before changing contact details connected with sign-in or payment records.

DANA and QRIS references help us match a payment status or receipt question with the correct account. The same principle applies to OVO, GoPay, bank transfer and virtual account records. We do not need your wallet PIN to investigate a reference.

Cookies can retain a sign-in session and selected settings on your mobile browser. You can clear or block them through your browser privacy controls. Blocking essential cookies may sign you out, so you may need to complete the account access step again.

We keep records for the purpose that created them, account security and applicable legal duties. The period can differ between a support message, device signal and payment reference. When continued storage is not needed, we remove, aggregate or restrict the record where practical.

Use the account security support route and provide the approximate time plus the device path, such as mobile browser or desktop browser. Do not include your password or one-time code. We use the account context to assess the sign-in and direct the next step.