Reference

cph2269 Privacy Policy Explained

Your account details, wallet records and device access are covered by the cph2269 Privacy Policy in one clear place.

Account dataWallet recordsCookie choicesAccess requests
cph2269 cph2269 Privacy Policy Explained
CONTACT THE POLICY TEAM

Three Ways To Ask About Your Privacy

A direct request helps us locate the right account record without exposing details to the wrong person.

Signed-in account route Open support from your account so we can connect the Privacy Policy request to the correct profile. Include the phone number used during verification and say whether you need access, correction or deletion.
Wallet record question If your request concerns a DANA, OVO, GoPay or QRIS reference, share the date and reference shown in your account rather than a wallet password. We use those details to trace the relevant transaction record.
Access without login If login is unavailable, state that clearly and provide the contact detail attached to your account. We will use an account check before discussing personal data, so a request cannot be answered to an unverified contact.
SIX DATA CONTROLS

What Our Privacy Process Covers

Privacy work is part of the account flow, not a separate promise hidden from the cashier or lobby.

Account collection

We use contact details and phone verification results to create the right account record. Details from an account step are kept separate from the wallet password, and we do not need that password to check a DANA or QRIS reference.

Device signals

When you sign in from a phone or desktop browser, we may record device and login signals linked to security checks. These signals help us spot unusual access while the mobile path moves from login toward the lobby.

Cookie choices

Cookies can remember a session and support account security. Your browser settings can restrict them, although changing those settings may require another login or affect how the Privacy Policy request path loads.

Wallet references

Payment records can contain a method, amount reference and status for DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use these operational details to match activity and resolve a status question.

Retention timing

We keep account and security records only for the period needed for account protection, service records or legal duties. When a record is no longer needed, we remove it or restrict access under our internal process.

Change requests

You can ask us to access, correct or delete personal data through support. Include your account contact and the requested action; we may verify ownership before making a change to protect your profile.

Privacy Policy Answers For Your Account

These answers focus on the questions you may have before opening an account or asking us to change an existing record. They describe the cph2269 Privacy Policy in practical terms, including wallet references, mobile access, cookies, retention and the checks we use before releasing account data. If your situation is not covered, use the support route above.

The cph2269 Privacy Policy covers account details, phone verification, login and device signals, cookie use, wallet references, support messages and retention. It also explains how to request access, correction or deletion, subject to local requirements and an account ownership check.

Phone verification helps connect the account to the contact detail you provided and reduces mistaken access. We may use the verification result when you sign in, request personal data or ask us to change records linked to DANA, OVO, GoPay or QRIS activity.

Yes. The Privacy Policy covers transaction references and status details connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use those references to match an account action, not to request your wallet password.

Use the signed-in account support route and ask for a data access request. Include the phone or email attached to your profile and describe the records you need. If you cannot sign in, say so; we will complete an ownership check first.

You can request a correction or deletion through support and identify the specific account detail involved. We may retain limited records when needed for account security, service records or legal duties. Access and eligibility depends on local law.

On a mobile browser, cookies may keep a session active and support security checks as you move from login to the lobby. You can restrict cookies in browser settings, but that may end your session or require another account sign-in.

State the action you want, such as access, correction, deletion or a cookie question. Add the account phone or email, relevant dates and any wallet reference shown in your account. Never include a wallet password; we do not need it for a request.