Reference

Open yatogel Privacy Policy Before Account Access

Clear control over your account data starts with our Privacy Policy. We explain what we collect during phone verification, how wallet records from DANA, OVO, GoPay and QRIS…

Account data clarityWallet record controlsMobile cookie choicesPhone check details
yatogel Open yatogel Privacy Policy Before Account Access
CONTACT PATH

Reach Us About Privacy Policy Requests

A direct support route helps when you need to ask about a privacy record, correct an account detail, or understand a wallet reference.

Account privacy request Use the support contact shown after login to ask what account data we hold…
Wallet record question If a DANA, OVO, GoPay, or QRIS receipt appears unclear, send the relevant reference…
Access concern When a mobile or desktop sign-in looks unfamiliar, contact us through the available support…
ACCOUNT CONTROLS

Switch On Clear Privacy Controls In yatogel

We keep this policy practical by connecting each privacy choice to an account action you can recognise.

Data collection

We collect account details you submit, phone verification results, sign-in events, device signals, support messages, and payment references needed to connect DANA, QRIS, or bank activity with your own account.

Cookie choices

Cookies can keep your session available between pages and remember selected settings. You can manage browser cookie controls on your mobile or desktop device, although some account functions may then need another sign-in.

Account security

Phone verification and sign-in records help us identify account access. Keep your password and wallet credentials private, and contact support if a device, login time, or account action does not look familiar.

Record retention

We keep account, support, security, and transaction records only as needed for the purposes described in this Privacy Policy, including resolving disputes, checking status, and meeting duties where local law permits.

Requesting changes

You can ask us to correct account data or explain its use through the support contact available after login. We may verify your account before changing records so another person cannot act for you.

Who receives data

Access is limited to people and service partners who need data for account operation, security, support, or payment reference handling. We do not ask for your DANA, OVO, GoPay, or QRIS password.

Browse Privacy Policy Answers For Your Account

These Privacy Policy answers address the account questions we expect before sign-in or phone verification. They cover data use, cookies, wallet references, correction requests, and access limits. If your situation is not covered, contact us through the support path shown in your account and describe the specific record you want us to check.

It covers account details, phone verification, sign-in events, device signals, cookies, support messages, and payment references used for DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

Phone verification helps connect account access to the correct person and supports security checks. We use the result for account handling and access decisions, with eligibility depending on local law.

We use payment references and status details to match an account transaction, investigate a receipt question, and prevent account confusion. We do not need your DANA or QRIS password for that process.

Yes. Contact us through the support route available after login and identify the record that needs correction. We may verify account ownership before making a change to protect your data.

Cookies can maintain your sign-in session and remember selected settings on mobile or desktop. Browser controls let you manage them, but disabling cookies may require another login or affect account pages.

Retention depends on the purpose of the record, including account operation, security checks, support handling, dispute resolution, and legal duties. We keep data only for the period those needs require.

Use the account support contact shown after login and describe your request clearly. For an unfamiliar access event, include the device and approximate time so we can locate the relevant account record.