Reference

Privacy Policy For Your primer4d Account

Our Privacy Policy explains how primer4d handles the details you provide when you create an account, enter the lobby and use DANA, OVO, GoPay or QRIS.

Account detailsWallet recordsCookie choicesContact requests
primer4d Privacy Policy For Your primer4d Account
CONTACT YOUR WAY

Get Privacy Policy Help Before Access

A clear contact route lets you ask about the Privacy Policy before you open an account or while you check a wallet record.

Account contact Ask us about the Privacy Policy, the data attached to your account, or a phone verification record through the account support path. Include your registered contact detail so we can distinguish your request from another account without asking for your password.
Wallet question If DANA, OVO, GoPay or QRIS shows a status you do not recognise, contact us with the transaction reference and approximate date. We can check the account-side record while you keep your wallet PIN and full payment credentials private.
Data request For a copy, correction or deletion question under this Privacy Policy, state the action you want and the account contact used at registration. We may ask for an account step to confirm that the request comes from you.
DATA HANDLING

See How primer4d Handles Your Details

The Privacy Policy gives you a practical view of the records created around your account, rather than treating every visit as the same.

Account creation

When you open an account, we collect the details needed to create your profile and send the phone verification step. The Privacy Policy explains why those fields are needed and how they connect to your account access.

Device sessions

Your mobile browser and desktop browser can produce different login session details. We use those signals to protect the account and investigate an access question, not to request your device password or wallet PIN.

Payment references

DANA, OVO, GoPay and QRIS can return a reference or status after you start a wallet action. We associate the account-side reference with your profile so a receipt question can be checked without storing your private wallet credential.

Cookies

Cookies can keep a session working, remember a selected setting and help us understand whether a page request belongs to the same visit. Your browser controls cookie removal, while the Privacy Policy explains their role in account access.

Retention

We retain account, payment and support records for the period needed for the purpose explained in this policy, required record keeping, or a question that has not yet been resolved. You can ask which retention reason applies to your record.

Policy changes

If we change how account data, cookies or wallet references are handled, we update the Privacy Policy on this page. Check the policy before a new account step, especially when access depends on local law.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account and wallet questions you are most likely to ask before using primer4d. They explain the practical route for checking, correcting or limiting the use of your details, while keeping access wording tied to local requirements. If your question concerns a specific record, use the account contact path and provide only the reference needed to locate it.

It covers account creation, phone verification, login sessions, cookies, support messages and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security checks, policy changes and how to contact us about your data.

We use your phone detail for the account verification step and to help connect a login request with the correct profile. The Privacy Policy explains this account purpose. Do not send us your wallet PIN, one-time code or full payment password through support.

Yes. It covers the account-side references and status details created when you use QRIS, DANA, OVO or GoPay. We use those records to check a receipt or status question. The wallet provider remains responsible for credentials held inside its own service.

Use the account support path and state whether you want a copy, correction or deletion request. Include the registered email or phone detail and the specific record concerned. We may ask an account verification question before changing or disclosing personal data.

Cookies can maintain a login session, remember a setting and connect related page requests. Your browser lets you remove or restrict them, although some account steps may then need to be repeated. The Privacy Policy describes cookies in relation to your access.

We keep account, payment-reference and support records for the period needed for their stated purpose, required record keeping or an unresolved request. The exact period can depend on the record type. Ask support which retention reason applies to your account detail.

Contact us through the account support path with the page subject, your registered contact detail and any relevant reference number. Access or eligibility depends on local law, so we can explain the policy route without promising access in a location where it is not permitted.