Reference

demo pg Privacy Policy For Your Account

The demo pg Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and contact our support team.

Account dataWallet recordsCookie choicesSecurity checks

Explore Our Lobby Read FAQ

See How Privacy Policy Applies

demo pg Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy sets out how we receive, use, store and disclose data connected with your demo pg account. This can include your contact details, phone verification result, sign-in device, approximate connection details, wallet selection and transaction reference. DANA, OVO, GoPay and QRIS may create payment

1
records needed to match a deposit or withdrawal request, while a bank transfer or virtual account can add a bank reference. We use these details to operate account access, detect unusual activity, answer support requests and meet applicable legal duties. You can ask us to correct
2
eligible data, explain a processing purpose or close an account request through the support path. Some access or retention choices depend on local law, and service access is available where local law permits. The policy applies alongside any specific consent prompt shown during account creation.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH REQUESTS

Get Privacy Policy Help From Your Account

A clear support route matters when you want to ask about your Privacy Policy rights or a stored account detail.

Account support form Use the support form inside your account to ask about data access, correction, deletion or a Privacy Policy purpose. We may request phone verification before discussing account-linked details.

Wallet record question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the date, amount and receipt reference through support. Keep your wallet PIN and one-time code private.

Sign-in access request For a locked sign-in or device change, tell us which account step stopped. We can explain the required identity check without asking you to share a password.

CONTROL YOUR DETAILS

Keep Privacy Policy Choices Clear

We handle this policy area through defined account steps rather than broad promises. Your request is tied to the profile you identify, the relevant device or wallet record, and the purpose you…

Data we receive

We may receive your name or contact detail, phone verification result, sign-in device data, connection details and account activity needed to provide access where local law permits.

Cookie controls

Cookies and similar storage can remember sign-in preferences and help us understand page errors. Your browser settings can clear or restrict them, although some account steps may then need repeating.

Account protection

Phone verification helps connect an account request to you. We also use sign-in and transaction signals to investigate unusual activity; never send us your password, wallet PIN or one-time code.

Retention timing

We retain account, support and payment references for as long as needed for the stated purpose, account administration or legal duties. Exact timing can depend on the record and local law.

Correction request

Ask us to correct an inaccurate eligible detail through the account support form. Include the field you want changed and the reason, so we can verify the request before editing it.

Policy contact

For a Privacy Policy question, contact us through support while signed in when possible. We will use the account step and request details to direct the matter to the right team.

Privacy Policy Answers For demo pg

These Privacy Policy answers focus on the questions you may have before opening an account or linking an Indonesian wallet. We keep each response tied to a real account action, from phone verification and QRIS receipts to cookie settings and requests made through support. Access and eligibility depend on local law.

It covers data linked to your account, sign-in device, phone verification, cookies, support messages and payment references such as DANA, OVO, GoPay and QRIS. It also explains purposes, retention and request paths.

Phone verification helps us connect an account request with the correct profile and investigate access problems. It can also support checks around unusual wallet activity without exposing your password or wallet PIN.

Yes. The Privacy Policy includes payment references needed to match activity, including QRIS receipts, DANA records and bank transfer or virtual account references. We do not ask for your private wallet PIN.

Sign in and use the account support form, naming the data request clearly. We may ask for a verification step before sharing account-linked details, and the response can depend on local law.

Yes. Send the field, the corrected value and a short reason through support. We compare the request with your verified account details before making an eligible change to the record.

Use your browser controls to clear or restrict cookies and similar storage. You may need to sign in again or repeat an account step, because some preferences will no longer be remembered.

We keep each record for the time needed for its stated purpose, account administration or legal duties. Payment references, support messages and account data can have different retention periods under local law.

demo pg Privacy Policy For Your Account

Get Privacy Policy Help From Your Account

Keep Privacy Policy Choices Clear

Data we receive

Cookie controls

Account protection

Retention timing

Correction request

Policy contact

Privacy Policy Answers For demo pg

01 What does the demo pg Privacy Policy cover?

02 Why does demo pg need phone verification?

03 Does the Privacy Policy include QRIS and bank transfer data?

04 How can I request a copy of my account data?

05 Can I ask demo pg to correct my details?

06 How do I change cookie choices for demo pg?

07 How long does the Privacy Policy keep my data?

Related Pages