Reference

Privacy Policy for 7c2711 Accounts

The 7c2711 Privacy Policy explains how we collect, use and protect details connected with your account, including phone verification and wallet activity.

Account dataWallet recordsCookie choicesContact requests
7c2711 Privacy Policy for 7c2711 Accounts
PRIVACY HELP

Where To Ask About Your Data

A clear contact path helps you question a record without losing the account context behind it.

Account request Ask us to correct contact details, explain a phone-verification record or clarify why an account detail appears in your profile. We use the account identifier you provide to locate the right record and may request an additional check before making a change.
Wallet reference For DANA, OVO, GoPay or QRIS questions, share the payment reference and date rather than a wallet password or private credential. We use that limited reference to trace a cashier status, match a receipt and explain which transaction details we retain.
Access concern If a new device, browser session or login alert concerns you, contact support with the account identifier and the approximate time. We can review the access record, explain the security step and help you understand what data was connected to that session.
DATA PRACTICE

How 7c2711 Handles Privacy

Privacy work is part of the account flow rather than a separate page you have to hunt for.

Account details

We collect the details needed for account creation, phone verification, sign-in protection and support. Your account path may include a phone number, device information and access timestamps, allowing us to distinguish a normal return from an unfamiliar session.

Payment records

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount, status and timing record. Bank transfer and virtual account activity may carry comparable references. These details help us match a cashier event without asking for your wallet password.

Cookies

Cookies can remember a session choice, preserve essential website functions and help us understand whether a page is working. You can manage cookie storage through your browser settings, although refusing required cookies may affect account access or policy preferences.

Device protection

We may use browser, device and login signals to identify unusual account access and request a further check. If you change from mobile to desktop, these signals help connect the session to your account without exposing wallet credentials to our support team.

Retention period

We keep personal and transaction records only while they support account operation, payment reconciliation, dispute handling, security checks or a legal duty. When a record is no longer needed for those purposes, our handling follows the deletion and retention rules that apply where you access the service.

Change request

You can contact us to ask for access, correction or clarification about personal data linked to your account. Include your account identifier and a focused request. We verify identity first, then explain the available action and any local-law reason a request may be limited.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account, device and payment records you are most likely to ask about before opening access. We keep the wording practical so you can decide what to share and where to send a request. If your situation is unusual, use the support path above and include only the details needed to locate your account.

It covers account details, phone verification, login and device signals, cookies, support messages and payment references. The policy also explains why we use these records, how long they may be retained and how you can ask for access or correction where local law permits.

Phone verification helps connect account access to the correct account and supports checks when a session comes from an unfamiliar device. We use the verification record for access protection and support, not as permission to request your DANA, OVO, GoPay or QRIS password.

Yes. It covers the transaction references needed to match DANA, OVO, GoPay and QRIS activity with your account. A reference may include status, timing and amount. Bank transfer and virtual account records can be handled in the same account-support process.

You can contact support with your account identifier and explain which detail is wrong, such as a phone number or contact record. We verify the request before changing anything, and the available action depends on local law and any record-retention duty.

Cookies can preserve essential session functions, remember selected settings and help us check page performance in a mobile browser. Your browser controls cookie storage. If you block required cookies, the login path or policy preferences may not work as intended.

We retain account, payment and access records while they are needed for account operation, reconciliation, security checks, disputes or legal duties. Retention is not unlimited by default. When a record no longer serves those purposes, handling follows the rules applicable where local law permits.

Use our available support channel and include the account identifier, the request type and any relevant payment reference. Do not send wallet passwords. We may ask for identity confirmation, then explain the response or any restriction required by local law.