Reference

Open primier4d Privacy Policy With Clarity

primier4d Privacy Policy explains which account, device and wallet details we collect, why we use them, and how you can ask about your records.

Account recordsWallet detailsCookie choicesContact requests
primier4d Open primier4d Privacy Policy With Clarity
CONTACT PATHS

Contact Us About Privacy Questions

A clear contact path helps you ask about your records without guessing which team to reach. Use the support route linked from your account area when a login, phone verification or wallet status creates a privacy question. Include the email or phone detail attached to your account, but never send a password or wallet PIN. We can then locate the right record and explain the next step.

Team online

Account privacy request

Ask which account details we hold and why they are used. Include your registered contact detail so we can identify the account before discussing records.

Wallet record question

For DANA, OVO, GoPay or QRIS references, send the transaction date and status shown in your account. Keep wallet passwords and PINs out of every message.

Access assistance

If phone verification blocks your policy request, use the account support route from the same device first. We may ask for an account detail to confirm your identity.

HANDLING DETAILS

Check How We Protect Your Records

We keep the Privacy Policy practical by linking each data use to an account action you recognise, from sign-in on mobile to a QRIS status check.

Account data

We use registration and phone verification details to create, secure and maintain your account record. We ask for enough detail to identify you, not for unrelated personal content.

Device signals

Your browser or mobile device can create session and security records when you sign in. These details help us detect unusual access and investigate a request tied to your account.

Cookie controls

Cookies can keep a sign-in session and remember selected settings. You can adjust cookie controls in your browser, although changing them may affect account access or policy-page preferences.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference records. We use status details to connect a payment event with the correct account.

Retention checks

We retain records for the period needed for account security, dispute handling and applicable local requirements. Ask through support if you want the reason for a particular retention period.

Change requests

You can ask us to correct account details, explain a data use or address a privacy concern. Where local law permits, we will assess the request after confirming account ownership.

Find Answers About Privacy Policy

These Privacy Policy answers cover the account steps Indonesian customers ask about most often. If your question involves a specific record, wallet reference or device session, contact us through the account support route so we can assess the details under applicable local requirements.

It covers account details, phone verification, device and session records, cookies, payment references and support requests. It also explains why we use those records and how to ask about them.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS. We use those records to match an event with your account, not to request wallet passwords.

Phone verification helps connect the account to the correct person and supports security checks before access. The related contact detail is handled under the Privacy Policy and can be queried through support.

You can contact us through the account support route and ask about records linked to your registered email or phone detail. Where local law permits, we assess the request after confirming account ownership.

Cookies may keep a session active and remember page settings. Your browser controls them, while changing cookie preferences can affect sign-in continuity. The Privacy Policy explains their role and related choices.

Retention depends on the record, security needs, dispute handling and applicable local requirements. Ask support about a specific account or payment reference, and we will explain the relevant retention reason.

Yes, you can ask us to correct an account detail or explain how it is used. Include the registered contact detail, avoid sending passwords, and remember that the outcome depends on local law.