Reference

demitoto Privacy Policy For Your Account

Our Privacy Policy explains what account details we collect, why phone verification is needed, and how we handle wallet records linked to DANA, OVO, GoPay and QRIS.

Account data explainedWallet records coveredCookie choices availablePhone checks described
demitoto demitoto Privacy Policy For Your Account
HELP WITH DATA

Get A Clear Privacy Support Path

Questions about your Privacy Policy choices should start with the support route inside your signed-in account.

Account contact route Use the signed-in support path for a Privacy Policy request about your name, phone…
Wallet record query If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the receipt reference…
Access assistance A sign-in problem does not remove your right to ask about stored data.
HANDLING YOUR DATA

Know What Our Privacy Controls Do

Our Privacy Policy is supported by everyday account controls rather than vague promises. We separate sign-in details from wallet references where practical, record security events to spot unusual access, and limit internal…

Collected account details

We may hold your account name, contact number, verification result, sign-in events and device signals. These details help us connect the right person to the right account without requesting unrelated personal material.

Wallet and payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create references linked to your account. We use those references to check status and resolve payment questions, not to request your wallet password.

Cookies on your device

Cookies can remember a device setting or help us understand a sign-in session. You can manage cookie permissions through your browser settings, although turning them off may affect account access steps.

Account security checks

Phone verification and login-event checks help us identify unusual account access. Keep your phone and sign-in details private, and contact us through the account path if a verification step does not match.

Retention approach

We retain each record for the period needed for its stated account, support, security or legal purpose. When that purpose ends, deletion or further restriction follows our internal handling process and local requirements.

Requests and corrections

You can ask what personal data we hold, request a correction, question a processing purpose or seek deletion where applicable. Include your account contact and request type so we can verify ownership before responding.

Find Answers Before Opening An Account

These Privacy Policy answers cover the searches we hear most often before account creation. They explain phone checks, payment references, device cookies, data access and contact steps in plain English. If your situation is different, sign in where possible and send a focused request through support so we can check the relevant account record.

The demitoto Privacy Policy covers account details, phone verification, login events, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect account access to the correct contact number and supports security checks. We record the verification result and related event, not more personal material than the account process requires.

Yes. The Privacy Policy covers references created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account routes. We use them to check payment status and answer account questions.

Sign in and use the account support route to ask for a copy of eligible personal data. State the account contact and request type; we verify ownership before sharing records tied to your account.

You can request a correction when an account detail is inaccurate or incomplete. Send the affected field through support, explain the change, and provide only the evidence needed for us to check ownership.

Cookies may remember device settings or support a sign-in session on your phone. Your browser controls cookie permissions, but restricting them can interrupt phone verification or other account access steps.

Use the contact path inside your signed-in account and label the request as a Privacy Policy matter. If you cannot sign in, use the public account contact route and avoid sending wallet passwords or full payment credentials.