Reference

Privacy Policy for prada118 Accounts

The prada118 Privacy Policy explains what we collect when you open an account, use the lobby, contact support or move funds through DANA, OVO, GoPay and QRIS.

Clear data purposesWallet activity contextAccount request routeMobile and desktop access
prada118 Privacy Policy for prada118 Accounts
CONTACT DATA CARE

Where To Ask About Your Privacy Policy

A clear contact path helps you control the data connected with your account. When a login, wallet reference or verification question needs attention, contact us through the support route shown after account access and describe the specific record or activity you mean. We use the details you provide to locate the request, confirm account ownership and reply with the next step. Please avoid sending wallet passwords or one-time codes in a support message.

Team online

Account contact route

Use the support contact inside your account when you want to ask about profile data, a login event or a correction. We may request an account step before discussing records, so a request is matched to the right person.

Wallet reference help

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, include the transaction reference and date, not your wallet password. We use that limited detail to trace the status while keeping unrelated account data out of the request.

Privacy request follow-up

Tell us whether you want to ask for access, correction or removal of eligible data. We will confirm the request path and may verify your account before sharing or changing records connected with prada118.

DATA HANDLING DETAILS

What We Keep And Why It Matters

We separate ordinary account activity from the details needed to resolve a specific payment or access request.

Account records

We use your registration details and phone verification status to connect an account request with the correct account. Clear account steps reduce mistaken changes when you ask about login history, profile details or access to stored records.

Payment references

A DANA, OVO, GoPay or QRIS reference can help us match a deposit or status question. Bank transfer and virtual account records are handled for the same account purpose, without asking you to share a wallet password.

Device signals

On a phone, tablet or desktop browser, we may retain basic device and session signals linked to account protection. These signals help us notice a new login path and investigate access concerns without reading unrelated files on your device.

Cookies

Cookies can keep a session available and show whether you opened this Privacy Policy. They may also support basic page operation. Your browser controls cookie storage, while account functions may need certain session cookies to work.

Retention timing

We retain records for the account, security or payment purpose that requires them, then assess whether they are still needed. A request about deletion or correction is checked against account status and applicable local requirements.

Security contact

If you suspect unauthorised access, contact us through the account support route and change your password from the account settings path. Do not send one-time codes; we use ownership checks before discussing sensitive records.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the account, device and wallet questions you may search before opening access. We keep each response tied to an action you can take, including checking a payment reference, asking for a record or securing a mobile session. If your question is not covered, use the contact route shown in your account and mention the exact data concern.

The prada118 Privacy Policy covers data connected with account creation, phone verification, login sessions, device signals, cookies, support messages and payment references. It explains why we use those details, how retention is assessed and how you can ask about access, correction or removal where local law permits.

We do not ask you to send a DANA, OVO, GoPay or QRIS wallet password through support. We may use a payment reference, date and account details to check status. If a request needs ownership confirmation, we use an account step rather than asking for a private wallet credential.

Use the support contact route inside your account and state that you are making a Privacy Policy data request. Identify the record or activity you mean, such as a phone verification event or login session. We may verify account ownership before explaining what can be provided.

Yes, ask us to correct an eligible account detail through the account contact route. Include the current record and the correct replacement, but do not include a password or one-time code. We check ownership first, then confirm whether the change can be made under the applicable local requirements.

A phone, tablet or desktop browser can provide basic session signals such as browser type and login timing. We use them to help identify unusual account access and support an investigation. We do not need access to unrelated files on your device for this account-security purpose.

Retention depends on why a record is needed, including account operation, payment matching, security checks or an unresolved support request. We assess whether it remains necessary after that purpose ends. You can ask about a particular record through support, and we will explain the available path.

Yes. Account access and eligibility depend on local law, including the rules that apply to your location in Indonesia. Our Privacy Policy still explains how data is handled when you contact us, browse the policy or use an available account path where local law permits.