Reference

Privacy Policy for Your paris8888 Account

Our Privacy Policy explains how we collect, use and protect the data connected with your paris8888 account, including phone verification and wallet activity.

Clear data purposesWallet activity explainedRequest changes directly
paris8888 Privacy Policy for Your paris8888 Account
CONTACT PATHS

Privacy Help Beside Your Account

A clear contact route helps when you want to ask about the Privacy Policy, correct account data or understand a wallet record. Start from the account support path and include the phone number linked to your profile, without sending a password or full payment credential. We use the details you provide to locate the request and keep the reply focused on your privacy question.

Team online

Account data request

Ask us to confirm the data linked with your account or explain how phone verification is recorded. Include your registered contact detail so we can match the request without asking you to share a password.

Wallet status question

For a DANA, OVO, GoPay or QRIS record, send the transaction reference and selected rail through our support path. We use those details to trace status without requesting your wallet PIN.

Policy correction route

If a Privacy Policy explanation or account detail appears incorrect, contact us through the same account support route. We can clarify the purpose, check the record and tell you what change request steps apply.

DATA PRACTICES

Inside paris8888 Privacy Handling

We separate the data needed for account access from the data used to resolve a payment or support request.

Account records

When you open an account, we record the details needed to create your profile and complete phone verification. Those records connect your sign-in activity with the correct account so we can answer a data request accurately.

Device access

A mobile browser may send device and session signals when you move from login to the lobby. We use these signals for access checks and account protection, not as a substitute for your registered contact detail.

Cookies explained

Cookies can remember a session choice, support page function and show whether a policy page opened correctly. You can manage cookie settings in your browser, though changing them may affect sign-in or saved display preferences.

Account security

We may compare sign-in details, device behaviour and phone verification before allowing account access. If a pattern needs checking, we use the support path to ask for relevant proof and never request your password or wallet PIN.

Retention approach

We keep account, support and payment-reference data for the period needed for the stated purpose, account security and applicable records. When a retention purpose ends, handling follows the deletion or restriction process described in the Privacy Policy.

Your change request

You can ask what account data we hold, request a correction or raise a question about use. Send the request through account support with your registered contact detail; we may verify ownership before making a change.

Privacy Policy Questions for Indonesia

These Privacy Policy answers cover the account steps and local wallet references you are most likely to ask about before opening an account. If your situation is not listed, use the account support path and identify the relevant data category without sending private credentials.

It covers data connected with account creation, phone verification, sign-in, device access, cookies, support requests and wallet references such as DANA or QRIS. It also explains purposes, retention, security checks and how you can request access or correction.

We use your phone number to create and identify the account, complete the required verification step and direct support replies to the correct profile. It can also help us review unusual sign-in activity before account access is restored.

Yes. The policy covers wallet and payment-reference data received when you select DANA, OVO, GoPay or QRIS. We use those references to match a status or support request, while your wallet PIN remains outside our requested support details.

Yes. Send a correction request through account support using the contact detail registered to your profile. We may verify that you control the account, then explain whether the requested field can be amended and when the change will appear.

Cookies can keep a session choice, help a policy page load correctly and support basic account navigation. You can manage them through your browser settings. Blocking certain cookies may affect sign-in, saved preferences or the path from mobile login to the lobby.

Retention depends on the purpose: account operation, security checks, support handling or payment-reference records. We keep data for the period needed for that purpose and applicable records, then follow the removal or restriction process stated in the Privacy Policy.

Use the account support route and state whether your request concerns access, correction, cookies, phone verification or a wallet reference. Include your registered contact detail and a reference where relevant, but do not send your password, wallet PIN or full credential.