Reference

Open paris99 Privacy Policy Before Account Access

paris99 Privacy Policy shows how we handle your account details, device signals and wallet records before you open an account or enter the lobby.

Account dataWallet recordsDevice controlsPolicy requests
paris99 Open paris99 Privacy Policy Before Account Access
REQUEST ROUTES

Check Your Privacy Support Path

A clear request path helps when you want to ask about a Privacy Policy matter rather than a game or cashier question. Start from the account support route and include the phone number linked to your paris99 account, the request you want handled and any relevant payment reference. We use those details to locate the right record while avoiding unnecessary copies of identity documents. Requests about access, correction or removal are assessed under local law.

Team online

Account access request

Tell us which account detail you want to see and include your verified phone number. We compare the request with the account record before sharing any response, so another person cannot use a public payment reference to obtain your private details.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the transaction reference and approximate time. We use the cashier status to locate the event, then explain which payment record is held and why it remains connected to your account.

Policy change request

If a phone number, profile detail or privacy preference needs correction, describe the requested change through our support path. We may ask for an account step or phone verification before acting, because changes must stay attached to the correct paris99 account.

DATA PRACTICE

Browse How paris99 Handles Data

The Privacy Policy is practical: it explains what we collect, why we use it and what happens when you stop using an account.

Account data

When you open an account, we use the details you submit and the phone verification result to create a sign-in path. Login events can be linked to that account so we can identify unusual access and respond to a request about your own records.

Cookie controls

Cookies can keep your session, language choice and page state available while you move between the account area and policy page. You can restrict cookies in your browser, although some sign-in or saved preference steps may then need to be repeated.

Device signals

A phone or desktop browser may send device and connection signals used for session security, fraud checks and troubleshooting. We use these signals for account protection rather than presenting them as public profile details, and we explain the related purpose when a request is made.

Payment references

A DANA, OVO, GoPay or QRIS reference helps match a cashier result with the correct account. Bank transfer and virtual account records can serve the same purpose, while wallet credentials remain with the payment service rather than being displayed in the account area.

Retention period

We keep records for the period needed to operate the account, resolve a payment question, protect access or meet a legal requirement. A deletion request may therefore remove some profile details while a transaction reference must remain for a defined purpose.

Your contact path

Send privacy questions through the account support route with your verified phone number and a precise request. We may ask for an additional account step before discussing personal data, and we use the contact details only to identify and answer the request.

Browse Privacy Policy Answers

These Privacy Policy answers cover the searches we hear most often before an account is opened. Each response points to the account, device or payment step involved, so you can decide what to send through support and what to expect when access depends on local law.

The paris99 Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains why we use each category, how long records may remain and how you can request access, correction or deletion where local law permits.

We handle the details you submit, the phone verification result and account activity needed for sign-in. We can also receive device signals and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account steps. We do not display wallet credentials in your account.

The Privacy Policy treats DANA and QRIS references as transaction records used to match a cashier result with your account. We may retain the reference, amount status and timing for support or legal purposes, while the wallet service remains responsible for its own credential handling.

Yes, you can send an account data request through the support path with the phone number linked to your account and a precise description. We verify that the request comes from the account holder before explaining or providing records, subject to limits that depend on local law.

Describe the incorrect detail and the change you want through account support. We may ask you to complete phone verification or another account step before editing it. This protects your profile from changes made through an unverified request and keeps the correction attached to the right account.

Retention depends on the purpose. We keep device signals while they support session security or access checks, and payment references while they help resolve a cashier issue or meet a legal requirement. A request can ask for the applicable period, although deletion may have lawful limits.

Yes, the Privacy Policy applies to your use of the account and related records from Indonesia. Account access and eligibility depends on local law. If you need a regional explanation, include your account phone number and location context in the support request so we can assess it properly.