Reference

Privacy Policy for Your Account Data

Our Privacy Policy explains what yes123 collects when you open an account, sign in from mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Account detailsWallet recordsDevice signalsCookie choices
yes123 Privacy Policy for Your Account Data
PRIVACY HELP DESK

Where To Ask About Your Records

A clear contact route helps when you want to understand, correct or remove personal details held under this Privacy Policy.

Account access If your phone verification stalls, contact us through the account support path and describe the sign-in step. We use the details already attached to your account to locate the request without asking you to send a full wallet history.
Wallet records For a DANA, OVO, GoPay or QRIS receipt question, provide the transaction reference and account contact detail through support. We use that pairing to check status while limiting exposure of unrelated account activity.
Privacy requests To ask for a copy, correction or deletion of personal data, name the request clearly and use the privacy contact route. We may verify account ownership first, then explain what can be changed or retained under local requirements.
DATA CONTROL POINTS

What Our Privacy Process Covers

We keep this policy practical by tying each data category to an account action you recognise. Phone verification supports access checks, device signals help us spot unusual sign-ins, and payment references help…

Account collection

When you create an account, we collect the contact and verification details needed to establish your access path. We do not treat a phone number as a general browsing profile; it is connected to the account step where you provide it.

Device signals

A mobile or desktop sign-in can produce device, browser and session signals. We use these markers to identify unusual access and protect the account; they help us assess a login event rather than describe your personal interests.

Cookie settings

Cookies may retain a session, language choice or security preference so the account area behaves consistently. You can manage cookie settings in your browser, although blocking some cookies may affect sign-in or policy-page access.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can appear in account records. We compare the reference, amount and account identifier supplied during a transaction to resolve status questions and prevent misapplied entries.

Security controls

We use phone verification, session checks and account activity records to reduce unauthorised access. Keep your sign-in details private and contact us if a session or wallet entry looks unfamiliar, so we can follow the account security process.

Retention requests

We retain some account, security and payment records for as long as needed for the purpose described in this policy or where local law permits. Ask us about a specific record, and we will explain whether correction, access or deletion is available.

Privacy Policy Answers For yes123

These Privacy Policy answers focus on the account and wallet questions you are most likely to have before opening access. We explain what is collected, how a request is checked and which details help us trace a DANA, OVO, GoPay or QRIS event. If your question involves eligibility, the answer depends on local law.

The yes123 Privacy Policy covers account details, phone verification, device and session signals, cookies, support conversations, and payment references. It explains why we use each category, how we protect account access, how retention works, and how you can ask about or change eligible records.

We collect the contact and verification details you submit for an account, together with login, device and security-event records created during access. If you use DANA, OVO, GoPay or QRIS, related references may be connected to your account to confirm status.

Yes. The Privacy Policy covers payment references from DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity connected with your account. We use those references to match a receipt or status question, not to expose unrelated account information.

Use the privacy contact route shown on this page and describe whether you want access to a record or a correction. Include your account contact detail and the relevant category, such as phone verification or QRIS reference. We may verify ownership before responding.

Cookies can keep a session, language choice or security setting available, while device and browser signals help us assess a sign-in. You can manage cookies in your browser. Blocking them may affect account access, but it does not erase records already retained under the policy.

We keep records for the purpose explained in the Privacy Policy, including account security, support and payment reconciliation, and for any period where local law permits or requires retention. Ask about a specific category and we will explain the applicable handling.

Start with the signed-in account support path when your concern involves access, phone verification or a wallet receipt. For a data request, use the privacy contact route on this page. Provide only the details needed to locate your account, and we may verify ownership.