Reference

Privacy Policy for Your ora788 Account

ora788 Privacy Policy explains how we collect, use and protect details connected with your account, wallet status and access to our casino and sports pages.

ACCOUNT CLARITYWALLET DATAMOBILE ACCESS
ora788 Privacy Policy for Your ora788 Account
CONTACT ROUTES

Where to Ask About Privacy Policy

A clear contact path helps when you need an account record explained or corrected. Send your request through our available account support route and include the phone number or account detail that lets us locate the right record without sending a wallet password. We can clarify a DANA or QRIS reference, explain a login event from your phone, and tell you what extra checks are needed before changing protected account details. Keep your request focused on Privacy Policy so our team can direct it correctly.

Team online

ACCOUNT REQUEST

Ask us to check the personal details attached to your account after phone verification. Include your registered contact detail and the specific field you want explained or changed; never send your password, wallet PIN or one-time access code.

WALLET RECORD

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, give us the date, amount reference and wallet name shown in your receipt. We use that context to locate the record while keeping your wallet credentials private.

ACCESS HELP

When a mobile login or account page stalls, contact the same support route and describe your device path, such as browser sign-in followed by the lobby page. We may ask for a receipt or verification detail before discussing protected data.

DATA PRACTICES

Inside ora788 Privacy Policy Controls

We handle policy requests around the account journey rather than treating every visit as a separate profile.

DATA USE

We use account details to create access, confirm phone ownership, respond to support and connect a payment status with the correct account. We do not describe DANA, OVO, GoPay or QRIS data as a reason to use unrelated personal details.

COOKIE CHOICES

Cookies can keep a session active or remember a page setting on your browser. You can manage browser cookie controls, but removing required cookies may interrupt sign-in and require you to verify the account again.

ACCOUNT SECURITY

Phone verification is part of account access, and sign-in events can help us spot unusual behaviour. Do not share your password, wallet PIN or one-time code; we may ask for account details before discussing a protected record.

RETENTION

We keep personal and payment-reference records for the period needed to provide account support, investigate status questions, protect access or meet a lawful requirement. When a record is no longer needed for those purposes, we review its removal.

YOUR REQUESTS

You can ask what personal details we hold, request a correction, or ask whether eligible deletion or restriction is available. We may verify that you control the account before acting, so another person cannot change your records.

POLICY CONTACT

Use our account support route for Privacy Policy questions and name the request clearly: access, correction, deletion, cookie choice or wallet-record clarification. Eligibility for a request depends on local law and the relevant account record.

Privacy Policy Questions About ora788

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. We explain what data is connected to phone verification, how cookies and mobile sign-in work, and how to contact us without exposing private credentials. If your request concerns eligibility or access, the outcome depends on local law and applies where local law permits.

The ora788 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It explains why we use those records for access, security, status checks and support, including references connected with DANA, OVO, GoPay and QRIS.

We may store a payment reference, date, status and account connection so we can investigate a transaction question. We do not need your wallet PIN or one-time code for that purpose. Your DANA or QRIS provider remains separate from our account records.

Yes, send an account support request that clearly asks for data access and include the registered contact detail. We may verify phone ownership before responding. The records we can provide, and any limits on the response, depend on local law.

Contact us through the account support route and identify the detail that needs correction, such as a contact number or account name. Do not include your password or wallet credentials. We may ask for phone verification before changing protected information.

Yes. Privacy Policy explains that cookies may support a browser session or remember a page setting when you move from mobile sign-in to the lobby. You can change browser cookie controls, although required cookies may be needed for account access.

We retain payment references, login events and related account records only while they support account service, security checks, status investigations or a lawful need. We periodically assess whether storage is still required. The applicable retention outcome depends on local law and the record type.

You can submit a deletion request through account support and state which record you want reviewed. We first verify account control, then assess whether the record must remain for security, support or a lawful requirement. The result depends on local law.