Reference

Open paris500 Privacy Policy Clearly

paris500 Privacy Policy explains how we collect, use and protect the account details connected with your lobby access, including phone verification and wallet activity.

Account dataWallet activityCookie choicesRequest changes
paris500 Open paris500 Privacy Policy Clearly
CONTACT PATHS

Ask Support About Privacy Policy

A direct support request helps you resolve a Privacy Policy question without guessing which account screen to use.

Account privacy request Ask us to explain the data linked to your account, including phone verification records and login details. We may ask you to confirm account ownership before discussing personal data.
Wallet reference check For DANA, OVO, GoPay or QRIS queries, send the transaction reference and approximate time through the account support route. We use the smallest useful set of details to trace status.
Policy clarification If a paragraph is unclear, quote the relevant wording and tell us what you need to know. Our support team can explain the request path without asking for your wallet PIN.
DATA PRACTICES

Browse How We Handle Your Data

Privacy Policy choices matter most when they connect to real account actions, so we describe our handling in operational terms.

Data collection

We collect details you provide for account access, including your phone number, plus records created when you sign in, verify the account or contact support about a wallet status.

Device and browser use

A mobile browser may provide device, browser and connection details so we can keep a login session working and identify unusual access. These records are tied to the relevant account event.

Cookie controls

Cookies can remember session settings and help us understand which account page was requested. Your browser controls can manage cookies, although switching them off may affect login continuity.

Account protection

Phone verification is part of the account path before access. Never share a one-time code or wallet PIN; if a login looks unfamiliar, contact support from the account route as soon as possible.

Retention choices

We retain account, transaction and support records for the period needed for account operation, dispute checks and applicable legal duties. The full policy explains how retention is assessed for each record.

Change or deletion request

You can ask us to correct details, obtain a copy or request deletion where available. We may verify ownership first and may keep records when an operational or legal reason requires retention.

Check Paris500 Privacy Policy Answers

These Privacy Policy answers address the searches we hear most often before account creation. They explain what we collect, how wallet references are used, what happens on a phone and how to contact us. If your situation is different, use the support path above and avoid sending passwords or verification codes.

It covers account details, phone verification, login events, device and browser data, cookies, wallet references, retention and contact requests. It also explains when data may be shared for account operation or legal duties and how to ask for correction or deletion.

We may collect your phone number, account details, verification records, login activity, device and browser signals, support messages and transaction references. The exact set depends on the account action you take, such as signing in or checking a DANA receipt.

We may retain a payment reference, amount context and status details needed to match a DANA or QRIS transaction with your account. We do not need your wallet PIN or one-time code for a support request.

Yes, you can contact support through the account route and ask for a copy or correction where that request is available. We first confirm account ownership, then explain what can be supplied, changed or retained under the Privacy Policy.

Retention depends on the type of record and the reason it was created. Account, transaction and support records may remain available for account operation, dispute checks or legal duties. The Privacy Policy sets out the factors used when retention ends.

Yes. The policy applies when you sign in through a mobile browser, including device, browser and cookie processing connected with that session. Review your browser cookie controls, and contact us if a shared device creates an account-access concern.

Use the support route shown after sign-in and include the policy question, registered phone number and only the necessary reference. Account eligibility depends on local law, so we can explain the applicable access position without requesting your wallet credentials.