Reference

Privacy Policy for Your larisbet303 Account

Our Privacy Policy explains what we collect when you open a larisbet303 account, use the mobile lobby, or request a wallet check through DANA and QRIS.

Clear data useCookie choicesAccount requestsLocal access
larisbet303 Privacy Policy for Your larisbet303 Account
PRIVACY HELP

Where To Ask About Your Data

A clear support path helps when you want to ask what we hold, why a record was used, or how to correct an account detail.

Account request Ask us to confirm the personal data connected with your larisbet303 account.
Wallet record For a DANA, OVO, GoPay or QRIS reference, send the transaction date and receipt…
Correction path If your phone number, name or contact detail needs changing, tell us which field…
DATA PRACTICES

What We Do With Account Records

Privacy depends on practical controls at each point where your account touches the lobby, wallet or support route.

Account data

We collect details you provide during account opening, including your phone number and contact information. The account path uses these details to create your profile, send verification prompts and connect later requests to the right record.

Device signals

When you sign in from a mobile browser or desktop, we may note browser type, device characteristics and security signals. These records help us identify unusual access without requiring the same device each time you enter the lobby.

Cookie controls

Cookies can keep a session active, remember selected settings and support account security. Your browser lets you clear or block them, although removing essential cookies may require another sign-in or interrupt a saved account path.

Payment matching

A payment reference can be used to match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity with your profile. We do not ask you to send a wallet password, card PIN or one-time security code.

Retention periods

We keep account, support and transaction records for as long as needed for the stated purpose, account security, legal duties or disputes. When a record is no longer needed, our handling process removes it or separates it from active account use.

Change requests

You can ask us to correct account data or explain its use through the support route. We check your identity first, record the request, and reply using the contact path connected with your larisbet303 account.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions we expect before you continue from Indonesia. They cover what we collect, why a payment reference may appear in an account record, how browser cookies affect access, and which steps help us respond to a data request. Where a request depends on identity or local requirements, we explain the next account step clearly.

The larisbet303 Privacy Policy covers account registration, phone verification, sign-in security, cookies, support messages and payment references. It explains why we use each category, who may need access for a stated purpose, how retention works and how you can request a correction.

We may collect your registered phone number, contact details, account activity, browser or device signals, support messages and transaction references. We use these records for account access, security, payment matching and support handling, rather than asking for a wallet password or security code.

DANA and QRIS references help us match a payment status with the correct account and resolve a receipt question. The wallet provider or bank may keep its own record under separate terms. Send only the date and reference needed for our support check.

Yes. Use the support route connected with your larisbet303 account and state whether you want access to a record or correction of a field. We first verify account ownership, then review the request and reply through the associated contact path.

Cookies may support sign-in sessions, saved settings and security checks. Your browser can clear or block them, but essential cookies may be needed for the account path to work. The Privacy Policy explains their purpose, while your browser controls local cookie removal.

We retain account, support and transaction records only while they serve the stated purpose, account security, legal duties or dispute handling. Retention can differ by record type. When the purpose ends, the record is removed or separated from active account use.

It applies to our pages and account handling where local law permits. Access and certain requests depend on local law, and external payment providers or banks may apply their own privacy terms. Contact support if you need the policy applied to a specific record.