Reference

Your Privacy Policy For Clearer Account Control

Your parislot Privacy Policy sets out what we collect, why we use it and how you can ask us to change or remove account details.

Account dataWallet recordsCookie choicesContact requests
parislot Your Privacy Policy For Clearer Account Control
CONTACT PATHS

Get Help With A Privacy Request

A clear contact path helps when a privacy question concerns your login, wallet reference or account record.

Account request Use the support contact path from your signed-in account when you want to ask what personal data we hold. Sending the request from the matching account helps us connect your question with the correct phone verification record without asking you to disclose a wallet password.
Wallet record For a privacy question about DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, name the rail and approximate transaction date. We use those details to locate the relevant record while keeping the request separate from your wallet PIN or banking credentials.
Sign-in concern If you think another device has reached your account, contact support through the account help path and change your password before sending extra details. We can review the sign-in context, protect the account and explain which privacy records may be affected.
HANDLING DETAILS

See How We Handle Your Data

We keep this policy practical: your account data supports sign-in, phone verification, payment matching and support replies, while device cookies help remember selected settings.

Account collection

When you open an account, we collect the details needed for access and phone verification. Sign-in activity and account changes may be linked to that record so we can investigate an unfamiliar device and answer a data request accurately.

Payment references

DANA, OVO, GoPay and QRIS can create payment references that help match an account action. Bank transfer and virtual account records may also be stored for reconciliation. We use these references for account support, not as a request for your private banking password.

Cookies on devices

Cookies can keep a selected language, session setting or security preference on your phone or computer. Clearing them may sign you out or remove saved choices. You can manage browser cookie controls, although some account functions may then require another sign-in.

Account security

Phone verification before account access helps us connect a sign-in with the correct account. We may examine device and session signals when access looks unusual. Never include a password, wallet PIN or one-time code in a support message.

Retention period

We retain account, support and payment-reference records only for the period needed for the stated purpose, account safety and applicable legal duties. When a record is no longer needed, our handling may include deletion, anonymisation or restricted storage.

Changes and contact

To request access, correction or deletion, send a signed-in support request describing the exact record. We may ask follow-up questions before acting. We will explain any limit that applies, including cases where a record must remain stored under local requirements.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the questions you may have before opening an account or sending a data request. We keep each answer tied to the actual account steps, device behaviour and payment references used on parislot. If your situation is not covered, contact support with the smallest amount of personal detail needed to identify your account.

The parislot Privacy Policy covers account details, phone verification, sign-in activity, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains your options for requesting access, correction, deletion or clarification.

We collect the details needed to create and secure your account, including contact details, phone verification results and relevant sign-in activity. If you use a wallet or bank route, we may retain a payment reference for matching and support, but you should not send us a PIN or banking password.

Phone verification helps connect account access with the correct person and reduces confusion when a new device signs in. It may also help us investigate an unusual session or answer a correction request. We use the verification record for account security and related support handling.

We may store transaction references, status details and account links needed to match activity through DANA, OVO, GoPay or QRIS. These records help resolve a wallet question without requesting your wallet PIN. Bank transfer and virtual account references may be handled in the same way.

Yes. Send a request through the support path connected with your account and state whether you want access or correction. We may ask you to complete an identity check before sharing or changing records, so another person cannot obtain your account details.

Use the signed-in support path and clearly ask for deletion under the Privacy Policy. We will check the request, explain which records can be removed and tell you if an account, payment or legal record must remain stored for a stated reason.

Some cookies can remain on your phone or computer until they expire or you clear them through the browser settings. Removing them may end your session or reset saved choices. The Privacy Policy explains their purpose, while your browser provides the device-level controls.