Reference

gadaitoto Privacy Policy Explained

Your gadaitoto Privacy Policy starts with clear control over account, wallet and device details, so you know what we collect and why we use it.

ACCOUNT RECORDSWALLET DETAILSDEVICE CHOICESLOCAL LAW
gadaitoto gadaitoto Privacy Policy Explained
CONTACT PATHS

Get Privacy Help From Your Account

A clear contact path matters when a Privacy Policy question concerns your own records. Start from the account help route while signed in, describe the specific record or request, and include the…

ACCOUNT HELP Use the help route attached to your signed-in account for access, correction or deletion questions. We can match your request to the account step and avoid unnecessary identity details.
WALLET STATUS For a privacy question tied to DANA, OVO, GoPay or QRIS, share the payment reference and status shown in your account so we can trace the correct record.
ACCESS QUESTIONS If local access affects your account request, tell us what you see on the sign-in path. We will explain the available route where local law permits.
DATA PRACTICES

Six Ways We Handle Your Data

We keep this policy practical by linking each data practice to an account action you can recognise.

COLLECTION

We collect account details you submit, phone verification results, sign-in events and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

PURPOSE

We use those records to open and secure your account, connect a payment status to your request, answer privacy questions and investigate unusual sign-in behaviour.

COOKIES

Cookies and similar device details can keep your session active, remember selected settings and help us detect repeated access problems. Your browser controls can manage cookie choices.

ACCOUNT SECURITY

Phone verification and sign-in checks help us distinguish your account access from unfamiliar activity. We may ask for account details before changing or releasing personal records.

RETENTION

We retain records only for the account, security, dispute or legal purpose that requires them. When that purpose ends, deletion or further restriction may be considered.

YOUR REQUEST

Ask for access, correction or a change through the account help route. Include the account step involved, and we will explain what can be changed where local law permits.

Privacy Policy Questions For gadaitoto

These Privacy Policy answers address the account and payment questions you may search before opening an account. We keep the wording tied to actual steps, including phone verification, wallet references, cookie settings and the account help route. If your situation is different, use the same contact path and describe the record you want us to check.

It covers account details, phone verification, sign-in activity, device and cookie data, plus payment references linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests.

Phone verification helps connect access with the correct account and supports security checks. We use the result for account handling and do not treat it as a reason to collect unrelated personal details.

We may retain the payment reference, requested amount status and related account link needed to trace your request. These records help us answer wallet questions and identify an unusual account event.

Yes. Use the signed-in account help route, describe the field or record that appears wrong, and provide the relevant account step. We will assess the request where local law permits.

Retention depends on why the record exists, including account security, payment disputes, service handling or legal duties. When the relevant purpose ends, we consider deletion or restricted handling.

Your browser settings can manage cookies and similar storage. Some choices may affect sign-in continuity or remembered preferences, but you can still contact account help about a privacy concern.

Start with the support contact shown in your signed-in account help area. State whether you need access, correction or deletion, and include only the account or payment reference needed to locate it.