Reference

Privacy Policy For Your jet4d Account

Our Privacy Policy explains what we collect when you open a jet4d account, use DANA or QRIS, and contact account support.

Account dataWallet recordsCookie choicesSecurity requests
jet4d Privacy Policy For Your jet4d Account
CONTACT OUR TEAM

Privacy Policy Help When You Need It

A clear contact path helps you ask about the Privacy Policy without sharing more data than necessary.

Account access If phone verification or login access is the reason for your Privacy Policy question…
Wallet records For a DANA, OVO, GoPay or QRIS record, share the payment reference and date…
Data requests To request a copy, correction or removal of personal data, state the action clearly…
DATA HANDLING

Six Privacy Policy Details To Check

We keep the Privacy Policy practical by connecting each data use to an account action you can recognise.

Account creation

When you open an account, we collect the details needed to create and maintain that account. Phone verification may be required before access. We use the submitted information to match your sign-in request and keep the account path distinct from another person’s.

Payment matching

A DANA, OVO, GoPay or QRIS action can create a reference, amount and status record. Bank transfer and virtual account records may include a bank reference. We use these details to match the requested transaction and investigate a receipt or status question.

Cookie controls

Our site may use cookies or similar browser storage for session continuity, preferences and security checks. You can manage cookies through your browser settings. Blocking some cookies may affect login continuity, but it does not turn a blocked payment into an account authorisation.

Account security

We treat passwords, phone verification codes and wallet PINs as confidential account credentials. Do not place them in support messages. If you suspect a session is exposed, change the relevant credential through the account path and contact support with the time and device involved.

Retention choices

We retain account, security and payment records only for the period needed for the stated account purpose, support handling, dispute checks or legal duties. A removal request may not erase records that must remain for a transaction or legal obligation.

Request handling

You can ask how your data is used, request a copy, correct inaccurate details or ask whether removal is available. We may confirm your identity before responding. Include a clear request and contact detail, while keeping passwords and wallet credentials out of the message.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the account, device and wallet questions you may have before opening an account. They also explain what to include when contacting us and why some records may remain after a removal request. Where access or eligibility is discussed, it depends on local law.

The jet4d Privacy Policy covers account details, phone verification, browser and session data, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It explains why we use each category and how you can ask about access, correction or removal.

Phone verification helps us confirm that the person requesting account access controls the registered contact route. We may use that check when you sign in or ask about personal data. Never send a verification code to support; tell us only that the access check is failing.

Yes. The Privacy Policy covers payment references and status details created when you use DANA or QRIS, along with comparable records for OVO, GoPay, bank transfer and virtual account actions. We use them to match a request, answer receipt questions and investigate an account status.

You can contact us with a clear request for the personal data connected to your account. We may verify ownership before providing a response. To protect your account, include an account identifier but exclude your password, wallet PIN and phone verification code.

Send a correction request through the available account support route and identify the inaccurate field. We may ask for an ownership check before changing it. If the detail is tied to a payment reference or security record, we will explain any handling restriction.

You can ask whether removal is available for a particular data category. We assess the request under the purpose and legal duties connected to that record. Account, security or payment information may need to remain for support handling, disputes or required transaction records.

Cookies can support session continuity, preferences and security checks when you use the site from a mobile browser or desktop. Your browser settings let you manage them. If you block required cookies, login or account navigation may not work as intended, while your Privacy Policy rights remain available.