Reference

edicitoto Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an edicitoto account, verify your phone, use the lobby, or check DANA and QRIS status.

Account dataWallet referencesCookie choicesSecurity checks

Explore Our Lobby Read FAQ

How Wallet Data Is Used Here

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

Our Privacy Policy separates payment status from the personal details needed to maintain your account. When you choose DANA, OVO, GoPay, or QRIS, we may receive payment references, status signals, and the account identifier needed to match an activity to your cashier history. Bank transfer and

1
virtual account records can also be used to confirm whether a transaction belongs to your account. We use phone verification before account access and may connect device or browser signals with security checks when unusual activity appears. The policy also explains why we keep records, when
2
cookies operate, and how you can ask us to correct or remove eligible data. We only describe access where local law permits; eligibility depends on local law. Read the full policy before opening an account, and contact us through the account support route if a privacy
3
question relates to a wallet status or receipt.

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

PRIVACY HELP ROUTES

Get Clear Answers About Your Data

A privacy question should not leave you guessing about the next step. We keep help close to the account and cashier paths, so you can ask about a phone check, a wallet…

Account support Send a privacy request from the support path connected to your account. Include your account identifier and the specific record you want us to check, such as a phone verification event.

Cashier context For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, keep the payment reference and receipt ready. We can use those details to locate the relevant status entry.

Access questions If a privacy concern affects account access, tell us what happened and which device or browser was used. We will direct the request through the available support channel.

DATA HANDLING PRACTICE

What Our Privacy Process Covers

We explain the practical parts of this Privacy Policy in terms you can use: what enters our records, why a security signal appears, and how to request a change.

Account details

We handle the details needed to create and maintain your account, including contact data supplied during the account path and the phone verification step required before access.

Device signals

Browser and device signals can help us connect a session to your account and identify unusual access. The policy explains their purpose rather than treating every signal as a personal profile.

Cookie choices

Cookies can support sign-in continuity, preferences, and security checks. Our Privacy Policy explains their role and the route available when you want to ask about cookie handling.

Account security

Phone verification and account checks help us investigate access concerns. Never send a wallet PIN or private login credential in a support message about your data.

Record retention

We retain account, security, and transaction-related records for the periods described in the policy. Retention can depend on the purpose of the record and applicable legal duties.

Change requests

You can ask us to access, correct, or remove eligible personal data through the support route. We may need account details to confirm that the request is yours.

Privacy Policy Answers Before Account Opening

These Privacy Policy answers focus on the questions you may have before opening an account in Indonesia. We cover wallet records, cookies, phone verification, device access, retention, and requests for changes. If your situation is not listed, use the support path connected to your account and describe the exact record or access event.

It covers account details, phone verification, device and browser signals, cookies, lobby activity, payment references, security checks, retention periods, and the steps for asking about or changing eligible personal data.

Yes. The Privacy Policy explains that DANA and QRIS activity may produce payment references and status details used to match a transaction with the correct account and cashier record.

Phone verification is part of the account access process. It helps connect a request or session to the correct account and gives us a clearer route when you ask about personal data.

The policy explains which OVO and GoPay payment references or status details may be handled for account and transaction records. It also describes the purpose and retention approach for those records.

You can send a correction request through the account support route. Include the account identifier, the data you believe is wrong, and the replacement detail so we can assess the request.

Cookies may support sign-in continuity, preferences, and security checks on your device. The Privacy Policy sets out their role and how to raise a question about cookie handling.

Yes. Account access and eligibility depend on local law. Where local law permits, you can read the Privacy Policy from the account area and contact us about your personal data.

edicitoto Privacy Policy for Your Account

Get Clear Answers About Your Data

What Our Privacy Process Covers

Account details

Device signals

Cookie choices

Account security

Record retention

Change requests

Privacy Policy Answers Before Account Opening

01 What does the edicitoto Privacy Policy cover?

02 Does the Privacy Policy mention DANA and QRIS data?

03 Why does edicitoto need phone verification?

04 Are OVO and GoPay details stored under this policy?

05 Can I ask to correct my personal data?

06 How do cookies affect my account access?

07 Does access to edicitoto depend on local law?

Related Pages