Reference

prada 188 Privacy Policy for Your Account

prada 188 Privacy Policy explains how we collect, use and protect the details connected with your account, including login data, wallet records and device signals.

Account dataWallet recordsCookie choicesPolicy requests
prada 188 prada 188 Privacy Policy for Your Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact route helps you act on the Privacy Policy without searching through unrelated account pages. Start from the account help path when you need to ask what data is held, why a phone check appeared or how a wallet record is matched. Include your account identifier and the date of the relevant event, but do not send a password or full wallet credentials. We use the details you provide only to locate the request and respond through the available account channel.

Team online

Account help path

Use the signed-in account help path for a Privacy Policy question about login records, phone verification or device activity. Add the approximate date and your account identifier so we can locate the relevant entry without asking you to send a password.

Cashier status request

If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account data, mention the payment reference and status shown beside the cashier record. We can explain the matching step while keeping your wallet PIN and complete credentials out of the request.

Policy change request

Ask us to correct, access or remove eligible personal details through the same support route. State the exact change you want, such as an old phone number or inaccurate contact detail, and we may request account verification before processing it.

DATA PRACTICE

How prada 188 Handles Personal Data

We apply the Privacy Policy to the account journey rather than treating every signal as the same.

Account security

We use phone verification before account access where that check is required, and we may compare sign-in, device and session signals when activity looks unusual. These checks support account protection without requiring us to see your phone passcode or wallet PIN.

Cookies and devices

Cookies can keep a sign-in session and selected settings working across a mobile browser or desktop browser. You can adjust cookie permissions in your browser settings, though turning them off may affect account access and may require another sign-in.

Payment references

For DANA, OVO, GoPay and QRIS, we use transaction references and displayed status to connect a wallet event with your account. Bank transfer and virtual account records serve the same matching purpose; we do not need your wallet password.

Retention period

We keep personal data only while it supports the purpose described in this Privacy Policy, account assistance or an applicable record requirement. When a record no longer serves one of those purposes, we assess deletion or removal of direct identifiers.

Access requests

You may ask what personal data is connected with your account, subject to identity checks and applicable limits. Include your account identifier, requested date range and preferred reply route so we can separate your records from another account.

Corrections and removal

If a phone number, contact detail or account entry is inaccurate, tell us the exact correction needed. You may also ask about removal where local law permits; we will explain any record that must remain for a stated obligation.

Privacy Policy Questions About prada 188

These Privacy Policy answers address the account, device and payment questions you may have before opening access or while checking a wallet record. We keep the wording tied to actual steps: phone verification, browser cookies, cashier references and the account help path. If your situation is not covered, contact us with the smallest useful set of details and we will direct the request.

It covers personal details connected with your account, including contact data, phone verification, device and session signals, support messages, cookie activity and payment references. The policy also explains how we use those details for access, account assistance, unusual activity checks and applicable record duties.

Yes. The Privacy Policy includes references and status information linked to DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account records. We use those references to match a cashier event to your account, not to collect your wallet password or PIN.

Use the signed-in account help path and ask for a personal data access request. Provide your account identifier, the relevant date range and a reply route. We may verify account ownership first, then explain which records can be supplied under applicable law.

You can request a correction through account support by naming the inaccurate field and the replacement detail. We may ask for a phone verification step before changing access data. This keeps an old number from being attached to the wrong account.

Cookies can preserve a sign-in session and selected settings when you use a mobile browser. Your browser controls can block or remove them, but account access may then require another sign-in. The Privacy Policy explains why these small files support the account path.

We retain information while it serves the purpose explained in the Privacy Policy, supports an open account request or meets an applicable record duty. We then assess deletion or removal of direct identifiers. The precise period can depend on the record type and local requirements.

Yes, access and eligibility depends on local law. Where local law permits, you can ask about account data, payment references, cookies, correction or removal through the stated support path. We may limit a request when a specific record must be retained for an applicable duty.